[ https://issues.apache.org/jira/browse/IGNITE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168847#comment-16168847 ]
Dmitriy Setrakyan commented on IGNITE-6285: ------------------------------------------- I have raised the priority of the issue to Blocker, as it is a critical usability problem. In addition to (1) and (2) above, I believe that the right way to solve it would be to store the previous IP:port binding on disk, to make sure that we reuse the same binding upon restart. > 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 > 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)