Re: [jbosscache-dev] Default JGroups configs

For 3.0, I agree. Can't ditch it for 2.x though. This came up analysing an intermittent failure in a state transfer test and I found that FLUSH wasn't present! On 24 Oct 2007, at 18:46, Brian Stansberry wrote: > Manik Surtani wrote: >> Any idea why the default configs still are: >> public String getDefaultClusterConfig() >> { >> return "UDP >> (mcast_addr=224.0.0.36;mcast_port=55566;ip_ttl=32;" + >> >> "mcast_send_buf_size=150000;mcast_recv_buf_size=80000):" + >> "PING(timeout=1000;num_initial_members=2):" + >> "MERGE2(min_interval=5000;max_interval=10000):" + >> "FD_SOCK:" + >> "VERIFY_SUSPECT(timeout=1500):" + >> "pbcast.NAKACK >> (gc_lag=50;retransmit_timeout=600,1200,2400,4800):" + >> "UNICAST(timeout=600,1200,2400,4800):" + >> "pbcast.STABLE(desired_avg_gossip=20000):" + >> "FRAG(frag_size=8192):" + >> "pbcast.GMS >> (join_timeout=5000;join_retry_timeout=2000;" + >> "shun=false;print_local_addr=true):" + >> "pbcast.STATE_TRANSFER"; >> } >> instead of using STREAMING_STATE_TRANSFER and FLUSH instead of >> STATE_TRANSFER? Any good reasons not to change it? > > Lots of other stuff missing vs. current best practice as well. No > FD. No FC. > > Although, IMHO in 3.0 we should get rid of this altogether and > force people to provide a config. > > -- > Brian Stansberry > Lead, AS Clustering > JBoss, a division of Red Hat > brian.stansberry(a)redhat.com -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev