[
https://issues.apache.org/jira/browse/IGNITE-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168953#comment-16168953
]
Denis Magda commented on IGNITE-6285:
-------------------------------------
[~dsetrakyan], [~yzhdanov], [~agoncharuk],
Binding to the same IP:port is a brittle scheme that might fail periodically in
short term and will definitely fail in the long term resulting in partial
partitions loss due to the redistribution. It's even worse for us if it happens
in years of the cluster being used in production. Even a MAC address as as
constant ID approach is not a problem solver because the hardware can be
replaced.
What if we try the following scheme. A special component will set an UUID as a
consistent ID for a node on startup. All the generated UUID(s) will be
persisted in a single file protected by file system lock. This guarantees IDs
reuse after restarts and should solve the issue once and forever.
> 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)
