[#KATTA-181] don't remove node-shard-mapping from client if proxy fails one time

Katta

don't remove node-shard-mapping from client if proxy fails one time

Created: 02/Feb/11 12:37 PM Updated: 02/Feb/11 06:30 PM

Component/s:

None

Affects Version/s:

0.6

Fix Version/s:

0.6.4

Description

« Hide

Right now a node is removed from shard-to-node mappings in the Client if an proxy-invocations fails.
The node-proxy itself, which gets removed as well, might be re-established if a new shard is added, but the removed shard-to-node mappings are never re-established for that client.

Now a failing proxy-invocation does not necessarily mean that the proxy is corrupt, see KATTA-180 as a example.

So following approach would look a bit safer:

remove a node-proxy only if x successive invocations are failed
re-establish the proxy immediatly
if the re-established proxy fails - remove the shard-to-node mapping

All

Comments

Change History

git Commits

Sort Order:

[ Permlink | « Hide ]

Johannes Zillmann added a comment - 02/Feb/11 06:30 PM

resolved in a way that a node-proxy + mapping will be removed:
a) if 3 successive proxy operations are failing
b) if 1 proxy operation is failing with an exception which indicates a connection problem