I'd like to add that first issue [1] has a follow-up fix [2]. It should
be backported along with the first fix.
[1] - https://issues.apache.org/jira/browse/IGNITE-8476
[2] - https://issues.apache.org/jira/browse/IGNITE-8682
Best Regards,
Ivan Rakov
On 05.06.2018 20:57, Ivan Rakov wrote:
I agree in general. First issue is severe usability issue, while
second one may fail crash recovery and cause data loss. This makes AI
2.5 not recommended for using.
Best Regards,
Ivan Rakov
On 05.06.2018 19:39, Alexey Goncharuk wrote:
Igniters,
Recently we've stumbled across the following two tickets [1], [2] which
seem to be very critical from the usability and stability points of
view.
The [1] results in clients not being able to update persistence-enabled
clusters unless the client configuration is identical to the server
configuration. The [2] may result in incorrect node state recovery and
either corrupted storage or lost updates.
I suggest we make an emergency release (to my knowledge, we already had
such a practice with Ignite 2.3) and include the fixes for both of the
issues to it.
Thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-8476
[2] https://issues.apache.org/jira/browse/IGNITE-8685
--AG
