Re: Grid behavior at key deserialization failure during rebalancing

Done https://issues.apache.org/jira/browse/IGNITE-2660 On Tue, Feb 16, 2016 at 12:58 PM, Dmitriy Setrakyan wrote: > Anton, > > If there is no deserialization for binary marshaller, then I would treat it > as a low priority issue. We should file a ticket and get to it when

[jira] [Created] (IGNITE-2660) Correct Grid behavior at key deserialization failure during rebalancing

Anton Vinogradov created IGNITE-2660: Summary: Correct Grid behavior at key deserialization failure during rebalancing Key: IGNITE-2660 URL: https://issues.apache.org/jira/browse/IGNITE-2660

Re: Grid behavior at key deserialization failure during rebalancing

Anton, If there is no deserialization for binary marshaller, then I would treat it as a low priority issue. We should file a ticket and get to it when it becomes more critical. D. On Tue, Feb 16, 2016 at 12:37 AM, Anton Vinogradov wrote: > Dmitry, > > I found such

Re: Grid behavior at key deserialization failure during rebalancing

Dmitry, I found such behavior at GridCacheRebalancingUnmarshallingFailedSelfTest. Seems we always unmarshalling keys at supply message handling in case of OptimizeMarshaller used. Also it happens when BinaryMarshaller used but key class implements Externalizable. On Mon, Feb 15, 2016 at 10:43

Re: Grid behavior at key deserialization failure during rebalancing

Anton, I am not sure why we would deserialize on the server side with Binary Marshaller. The data should remain in binary form. Do you know if we have a test for it? Thanks, D. On Mon, Feb 15, 2016 at 1:20 AM, Anton Vinogradov wrote: > Dmitriy, > > Key can be

Re: Grid behavior at key deserialization failure during rebalancing

Dmitriy, Key can be undeserializable during rebalancing because of many reasons. For example, 1) It was serialized with errors 2) Deserialization cause error 3) It based on classes unavailable at node trying to deserialize it Third is the most possible case. On Sat, Feb 13, 2016 at 3:44 AM,

Grid behavior at key deserialization failure during rebalancing

Igniters, At this moment key deserialization failure during rebalancing cause strange situation: 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

Re: Grid behavior at key deserialization failure during rebalancing

Anton, I am not sure I fully grok the use case. Can you please explain why a key can be broken? D. On Fri, Feb 12, 2016 at 7:11 AM, Anton Vinogradov wrote: > Igniters, > > At this moment key deserialization failure during rebalancing cause strange > situation: > >