ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov <avinogra...@gridgain.com>
Subject Grid behavior at key deserialization failure during rebalancing
Date Fri, 12 Feb 2016 15:11:24 GMT

At this moment key deserialization failure during rebalancing cause strange

Rebalancing from node sent supply message with broken key will be cancelled
at current topology.
All upcoming supply messages from this node will be be ignored, no new
demand messages to this node will be sent.

But when topology will be changed again, node with broken key will take
path at rebalancing again, untill key deserialization failure happen ...

Do we need to improve this situation, and if we have to how should be
handled case with key deserialization failure?

I see some ways:
1) We can inform user about data loss because of deserialization problems,
but keep current rebalancing strategy
2) We can continue rebalancing from this node, but ignore messages with
broken keys. And inform user about data loss.
3) We can pause rebalancing untill deserialization will be fixed somehow,
for example by shutdowning demanding or supplying node.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message