[
https://issues.apache.org/jira/browse/IGNITE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171864#comment-16171864
]
Alexey Goncharuk commented on IGNITE-6285:
------------------------------------------
We can keep the first assigned consistent ID (the one obtained during the first
startup) but in this case, it may be confusing because the actual IP address
has changed, but we keep using the old one.
> Enhance persistent store paths logging on start
> -----------------------------------------------
>
> Key: IGNITE-6285
> URL: https://issues.apache.org/jira/browse/IGNITE-6285
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Alexey Goncharuk
> 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)
