Jean-Baptiste Onofré created KARAF-4664:
-------------------------------------------
Summary: Cellar can stop bundles whereas it should not
Key: KARAF-4664
URL: https://issues.apache.org/jira/browse/KARAF-4664
Project: Karaf
Issue Type: Bug
Components: cellar-bundle, cellar-features
Affects Versions: cellar-4.0.1
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Fix For: cellar-4.0.2
If we have a cluster of 2 nodes running, both with all the same bundles
deployed and activated. We stop the second node, then the first one. We start
the first node, wait until it is fully initialized, then start the second one.
The issue is that sometimes second node startup causes few bundles on the first
node to stop.
My guess is that the second node, when joining the cluster, pushes its state to
the cluster while some of its bundles are still starting and in RESOLVED state,
which causes corresponding bundles on the first node to stop and stay RESOLVED
too. My hypothesis is supported by the fact that once I change the
"default.*.sync" options in the "org.apache.karaf.cellar.groups.cfg" from
"cluster" to "clusterOnly", the issue stops happening. However, I think we
still should support the "cluster" synchronization strategy if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
