ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasad Bhalerao <prasadbhalerao1...@gmail.com>
Subject Re: After upgrading 2.7 getting Unexpected error occurred during unmarshalling
Date Sat, 12 Jan 2019 05:47:14 GMT
No I am not using zookeeper discovery.
Using TcpDiscoveryVmIpFinder.

Can someone please explain on what event cacheMetrics in TcpDiscoveryNode
gets populated. It is not getting populated in standalone program.

If it gets populated then I might be able to reproduce this case.

On Fri 11 Jan, 2019, 8:28 PM Ilya Kasnacheev <ilya.kasnacheev@gmail.com
wrote:

> Hello!
>
> Have you tried enabling Zookeeper in your reproducer? I have a hunch that
> they are linked: this behavior is affected by zookeeper discovery.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 11 янв. 2019 г. в 17:44, Prasad Bhalerao <prasadbhalerao1983@gmail.com
> >:
>
>> I tried to reproduce this in standalone program. But the thing is cache
>> metrics map in TcpDiscoveryNode is empty even after setting
>> statisticEnabled to true on all caches.
>> So the flow does not enter into serializr/deserialize cacheMetrics block.
>>
>> Any idea how the cacheMetrics gets populated. On which event?
>>
>>
>> Thanks,
>> Prasad
>>
>> On Fri 11 Jan, 2019, 7:55 PM ilya.kasnacheev <ilya.kasnacheev@gmail.com
>> wrote:
>>
>>> Hello!
>>>
>>> I think the problem was introduced by
>>> https://issues.apache.org/jira/browse/IGNITE-6846 which does look very
>>> suspicious, however it is strange that it does not reproduce right away.
>>>
>>> I could try and devise a fix but I could not reproduce this behavior in
>>> any
>>> of tests. If you could do a reproducer project that would be awesome.
>>>
>>> Regards,
>>>
>>>
>>>
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>>
>>

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