[infinispan-issues] [JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040861#comment-13040861 ] 

Sanne Grinovero commented on ISPN-5159:
---------------------------------------

+1
Long time ago I would use the JGroups option {{org.jgroups.protocols.Discovery.num_initial_members}} but this is being ignored now. Not sure why JGroups dropped the feature - probably not a problem for JGroups users but it's a problem for Infinispan users to not have a similar strategy.

> Make concurrent startup smooth
> ------------------------------
>
>                 Key: ISPN-5159
>                 URL: https://issues.jboss.org/browse/ISPN-5159
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Core
>    Affects Versions: 7.1.0.Beta1
>            Reporter: Radim Vansa
>
> When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc.
> Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info.
> ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)