[
https://issues.apache.org/jira/browse/IGNITE-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740463#comment-16740463
]
Stanislav Lukyanov commented on IGNITE-10900:
---------------------------------------------
There are some pros and cons of adding a warning when there is no explicit
consistent ID.
The benefits are described in the Description.
The main downside is that this will be yet another warning printed for the
default configuration - and also for the examples. This is always confusing for
a new user ("I've just started Ignite and I'm already doing something wrong?").
Also, currently there is no easy way to change consistent ID per node when the
configuration file/bean is shared between all nodes.
However, the warning doesn't break any behavior, and the benefit of having
consistent IDs in more installations seems more important than the downsides.
> Print a warning if native persistence is used without an explicit consistent
> ID
> -------------------------------------------------------------------------------
>
> Key: IGNITE-10900
> URL: https://issues.apache.org/jira/browse/IGNITE-10900
> Project: Ignite
> Issue Type: Bug
> Reporter: Stanislav Lukyanov
> Priority: Major
>
> Experience shows that when Native Persistence is enabled, it is better to
> explicitly set ConsistentIDs than use the autogenerated ones.
> First, it simplifies managing the baseline topology. It is much easier to
> manage it via control.sh when the nodes have stable and meaningful names.
> Second, it helps to avoid certain shoot-yourself-in-the-foot issues. E.g. if
> one loses all the data of a baseline node, when that node is restarted it
> doesn't have its old autogenerated consistent ID - so it is not a part of the
> baseline anymore. This may be unexpected and confusing.
> Finally, having explicit consistent IDs improves the general stability of the
> setup - one knows what the the set of nodes, where they run and what they're
> called.
> All in all, it seems beneficial to urge users to explicitly configure
> consistent IDs. We can do this by introducing a warning that is printed every
> time a new consistent ID is automatically generated. It should also be
> printed when a node doesn't have an explicit consistent ID and picks up one
> from an existing peristence folder.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
