[
https://issues.apache.org/jira/browse/IGNITE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180770#comment-16180770
]
ASF GitHub Bot commented on IGNITE-6285:
----------------------------------------
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2752
IGNITE-6285: Enhance persistent store paths logging on start
Experimental commits to run TC tests, do not merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6285
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2752.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 #2752
----
commit b150519f05c99e71be83af9d5107ae599c90f05f
Author: dpavlov <dpav...@gridgain.com>
Date: 2017-09-26T13:31:54Z
IGNITE-6285: Enhance persistent store paths logging on start
----
> Enhance persistent store paths logging on start
> -----------------------------------------------
>
> Key: IGNITE-6285
> URL: https://issues.apache.org/jira/browse/IGNITE-6285
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Yakov Zhdanov
> Assignee: Dmitriy Pavlov
> Priority: Blocker
> Labels: usability
> Fix For: 2.3
>
>
> As per this thread -
> http://apache-ignite-users.70518.x6.nabble.com/Specifying-location-of-persistent-storage-location-td16636i20.html
> Ignite may switch storage path in case of changing DHCP lease or similar
> which can lead to consistent ID change.
> In order to help user in spotting the issue Ignite may output the following
> to the logs:
> # Output the store path and tell its (1) size or state that it is empty and
> (2) last data file modification date.
> # Output warning if there are other non-empty storage folders under work
> directory with their sizes and dates.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
