[
https://issues.apache.org/jira/browse/KARAF-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoli Ding updated KARAF-1348:
-------------------------------
Description:
There are two nodes in default group locally:node1&node2, first stopping
handler 'org.apache.karaf.cellar.config.ConfigurationEventHandler' on node1,
then create new configuration on node1 using standard karaf
commands:'config:edit test.handler' &'config:update', then check this
configuration status on node2 , the new configution is still output on node2
with command 'cluster:config-list default', new configuration synchronized.
Sample:
on node1:
{panel}
karaf@trun> cluster:handler-stop
org.apache.karaf.cellar.config.ConfigurationEventHandler
Node Status Event Handler
xlding:5701 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5701 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5701 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
karaf@trun> config:edit test.handler
karaf@trun> config:update
{panel}
on node2:
{panel}
karaf@trun> cluster:handler-status
Node Status Event Handler
xlding:5701 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5701 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5701 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
xlding:5702 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5702 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5702 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5702 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
karaf@trun> cluster:config-list default
Configuration PIDs for group default
PID
...
test.handler
...
{panel}
Should not output "test.handler" on node2
was:
There are two nodes in default group locally:node1&node2, first stopping
handler 'org.apache.karaf.cellar.config.ConfigurationEventHandler' on node1,
then create new configuration on node1 using standard karaf
commands:'configļ¼edit test.handler' &'config:update', then check this
configuration status on node2 , the new configution is still output on node2
with command 'cluster:config-list default', new configuration synchronized.
Sample:
on node1:
{panel}
karaf@trun> cluster:handler-stop
org.apache.karaf.cellar.config.ConfigurationEventHandler
Node Status Event Handler
xlding:5701 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5701 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5701 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
karaf@trun> config:edit test.handler
karaf@trun> config:update
{panel}
on node2:
{panel}
karaf@trun> cluster:handler-status
Node Status Event Handler
xlding:5701 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5701 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5701 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
xlding:5702 OFF
org.apache.karaf.cellar.config.ConfigurationEventHandler
xlding:5702 ON
org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
xlding:5702 ON org.apache.karaf.cellar.bundle.BundleEventHandler
xlding:5702 ON
org.apache.karaf.cellar.features.FeaturesEventHandler
karaf@trun> cluster:config-list default
Configuration PIDs for group default
PID
...
test.handler
...
{panel}
Should not output "test.handler" on node2
> Can not disable config sync through stopping handler
> org.apache.karaf.cellar.config.ConfigurationEventHandler
> -------------------------------------------------------------------------------------------------------------
>
> Key: KARAF-1348
> URL: https://issues.apache.org/jira/browse/KARAF-1348
> Project: Karaf
> Issue Type: Bug
> Components: cellar-config
> Affects Versions: cellar-2.2.4
> Reporter: Xiaoli Ding
> Priority: Minor
>
> There are two nodes in default group locally:node1&node2, first stopping
> handler 'org.apache.karaf.cellar.config.ConfigurationEventHandler' on node1,
> then create new configuration on node1 using standard karaf
> commands:'config:edit test.handler' &'config:update', then check this
> configuration status on node2 , the new configution is still output on node2
> with command 'cluster:config-list default', new configuration synchronized.
> Sample:
> on node1:
> {panel}
> karaf@trun> cluster:handler-stop
> org.apache.karaf.cellar.config.ConfigurationEventHandler
> Node Status Event Handler
> xlding:5701 OFF
> org.apache.karaf.cellar.config.ConfigurationEventHandler
> xlding:5701 ON
> org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
> xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
> xlding:5701 ON
> org.apache.karaf.cellar.features.FeaturesEventHandler
> karaf@trun> config:edit test.handler
> karaf@trun> config:update
> {panel}
> on node2:
> {panel}
> karaf@trun> cluster:handler-status
> Node Status Event Handler
> xlding:5701 OFF
> org.apache.karaf.cellar.config.ConfigurationEventHandler
> xlding:5701 ON
> org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
> xlding:5701 ON org.apache.karaf.cellar.bundle.BundleEventHandler
> xlding:5701 ON
> org.apache.karaf.cellar.features.FeaturesEventHandler
> xlding:5702 OFF
> org.apache.karaf.cellar.config.ConfigurationEventHandler
> xlding:5702 ON
> org.apache.karaf.cellar.dosgi.RemoteServiceCallHandler
> xlding:5702 ON org.apache.karaf.cellar.bundle.BundleEventHandler
> xlding:5702 ON
> org.apache.karaf.cellar.features.FeaturesEventHandler
> karaf@trun> cluster:config-list default
> Configuration PIDs for group default
> PID
> ...
> test.handler
> ...
> {panel}
> Should not output "test.handler" on node2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
