ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: ignite 1.4 status
Date Tue, 22 Sep 2015 02:50:53 GMT

I was debugging issues with discovery today, my findings are below:

   - Issue with assertion "topology version has not been updated" was
   caused by sending discard message for custom messages. Now since we
   re-arrange custom messages, discardId gets repositioned and messages that
   should have been discarded were not discarded.
   - Fixed the issue above by introducing separate pending queue for custom
   messages which gets discarded independently from other discovery messages.
   - Did not get to the bottom of "joining nodes" assertion. From the debug
   I see that coordinator always fires custom messages at the right moment,
   when joiningNodes is empty, however despite the fixed (above) issue with
   custom messages discard, custom processed custom messages get re-sent which
   leads to this assertion

I committed my pending debug code to ignite-1171-debug branch, if any of
you guys is up to debugging this issue while I'm asleep - great, if not -
I'll continue digging into it tomorrow.

2015-09-21 10:55 GMT-07:00 Yakov Zhdanov <yzhdanov@apache.org>:

> Igniters,
> We are not ready to release today.
> Alexey Goncharuk is still working on ignite-1171. Alex please provide
> updates by the end of the day.
> https://issues.apache.org/jira/browse/IGNITE-1516 - performance offheap
> query benchmark is not fully recovered. Semyon will be fixing it. Sergi,
> can you please assist?
> https://issues.apache.org/jira/browse/IGNITE-973 - Semyon has fixed race
> in
> cache logic, but issue is still reproducible due to possible issues in
> indexing logic. Sergi, this is on you. Can you please take a look?
> --Yakov

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