[
https://issues.apache.org/jira/browse/IGNITE-9999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684213#comment-16684213
]
ASF GitHub Bot commented on IGNITE-9999:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5371
IGNITE-9999 Logical recovery cleanup and refactoring
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9999
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5371.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5371
----
commit 7110ba25a617ffe9317daeca0a608d6e38e72d1f
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-11-12T11:36:53Z
IGNITE-9999 Ignite recovery refactoring + extended logging WIP
commit 86817a5c6b1efaba86f602c1d6b08641ae57e3bc
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-11-12T18:21:12Z
IGNITE-9999 Invoke shutdown page store for non-affinity cache groups to
release possible open file descriptor
----
> Add verbose logging for node recovery
> -------------------------------------
>
> Key: IGNITE-9999
> URL: https://issues.apache.org/jira/browse/IGNITE-9999
> Project: Ignite
> Issue Type: Task
> Reporter: Alexey Goncharuk
> Assignee: Pavel Kovalenko
> Priority: Major
>
> Sometimes we see some difficulties in understanding which state a node is
> after a binary recovery and what state it has after applying all logical
> records from WAL.
> We need to add more information on the state of partitions (update counter,
> size, maybe more additional info) after the binary recovery (can be validated
> against checkpoint records) and after logical recovery (can help to validate
> the correctness of rebalance).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
