[OAK-3961] Cold Standby revisit timeout setup

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.16, 1.3.15, 1.4
• Component/s: tarmk-standby
• Assignee: Alex Deparvu
• Reporter: Alex Deparvu
• Created: 31/Jan/16 13:18
• Updated: 07/Jun/16 17:30
• Resolved: 01/Feb/16 15:07

Description

The timeout settings are too large and inefficient, making all the tests very slow. On top of this the current timeout if being enforced in 2 places, which turns out it doesn't play too well with the sync mechanism:

• one is via the ReadTimeoutHandler in the StandbyClient
• second is in the SegmentLoaderHandler
  as it turns out the first one is a global kill switch, and it will fail any transaction larger than the set value (all of the sync cycle), which is not what I meant to do with it, so I'll remove it and only leave the second one, which is a timeout per request (segment or binary).

Issue Links

• is duplicated by: OAK-3368 Speed up ExternalPrivateStoreIT and ExternalSharedStoreIT