CDV ❯ Make L2 to L2 comms default to using the reconnect stuff

• Type: New Feature
• Status: Closed
• Priority: 2 Major
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: hsingh
• Reporter: steve
• Created: May 19, 2008
• Votes: 0
• Watchers: 0
• Updated:

  February 12, 2013
• Resolved:

  May 18, 2010

Description

It will increase the failover time, but I guess we could at least with small reconnect window to protect against small network failures.

Steven Harris wrote: should we default to using the once and only once protocol between L2s? http://forums.terracotta.org/forums/posts/list/1039.page

Comments

Saravanan Subbiah 2008-06-10

Want to fix all known issues with OOO like poor performance, memory overhead, 2 different deadlocks that we know of, before enabling it for L2-L2 communication.

Saravanan Subbiah 2010-05-17

I think we are on track to make it the default in Esperance/Taraval timeframe.

Himadri Singh 2010-07-12

Defaults are

l2.nha.tcgroupcomm.reconnect.enabled = false
l2.nha.tcgroupcomm.reconnect.timeout = 2000

l2.l1reconnect.enabled = false
l2.l1reconnect.timeout.millis = 2000

OOO has been disabled by default in http://svn.terracotta.org/fisheye/changelog/Terracotta?cs=15347

Himadri Singh 2010-07-12

Verified in rev Terracotta Enterprise 3.3.0, as of 20100709-160710 (Revision 7827-15863 by cruise@su10mo5 from 3.3)