[
https://issues.apache.org/jira/browse/UNOMI-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399639#comment-17399639
]
Serge Huber commented on UNOMI-503:
-----------------------------------
Actually I think the unomi:start/stop could be replaced by using features.
Another solution might have been to use bundle state listener instead of
deactivating the cluster sync. But at least this proposal is safe.
> Cluster state of unomi bundles is not correct after unomi:start
> ---------------------------------------------------------------
>
> Key: UNOMI-503
> URL: https://issues.apache.org/jira/browse/UNOMI-503
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.6.0
> Reporter: Kevan Jahanshahi
> Assignee: Kevan Jahanshahi
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The main issue is that unomi commands like:
> unomi:start and unomi:stop
> are just installing/starting the bundle locally on the karaf instance, they
> are not considered (installed or started) by the cluster. because we just use
> local bundle management and we are not updating the bundle states in cellar.
> I would say that for a workaround it's ok to disable the cluster sync, but
> may be in the future we will have to provide a better cluster support of
> unomi bundles.
> This can be verified by doing the provided commands, on a fresh install
> 1.6.0-SNAPSHOT:
> * *s*tart a fresh install of *jcustomer 1.6.0-SNAPSHOT*
> * execute command: *unomi:start*
> * execute command: *bundle:list | grep -vi active*
> ** nothing, everything is active (all bundles are started correctly)
> * execute command: *cluster:bundle:list | grep -vi active*
> ** All this bundle are considered resolved in the cluster:
> {noformat}
> Bundles in cluster group default
> ID │ State │ Lvl │ Located │ Blocked │ Version │ Name
> ────┼──────────┼─────┼───────────────┼─────────┼───────────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
> 1 │ Resolved │ │ cluster/local │ │ 4.2.8 │
> Apache Karaf :: Features :: Extension
> 57 │ Resolved │ │ cluster/local │ │ 1.0.0 │
> Apache Aries Blueprint Core Compatiblity Fragment Bundle
> 68 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-blueprint
> 69 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-core
> 70 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-core-osgi
> 71 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-ftp
> 72 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-http-common
> 73 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-jackson
> 74 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-kafka
> 75 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-servlet
> 76 │ Resolved │ │ cluster/local │ │ 2.20.2 │
> camel-stream
> 79 │ Resolved │ │ cluster/local │ │ 3.6.0 │
> Apache Commons Net
> 88 │ Resolved │ │ cluster/local │ │ 3.3.4 │
> Apache CXF RS Cross-Origin Resource Sharing
> 135 │ Resolved │ │ cluster/local │ │ 4.2.8 │
> Apache Karaf :: Shell :: Console
> 147 │ Resolved │ │ cluster/local │ │ 0.1.54.1 │
> Apache ServiceMix :: Bundles :: jsch
> 174 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Extensions :: Router :: API
> 175 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Extensions :: Router :: Core
> 176 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Extensions :: Router :: REST API
> 177 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Extensions :: Router :: Services
> 180 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Tools :: Shell commands
> 181 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Tools :: Shell Dev commands
> 182 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Core Web Application
> 183 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> Apache Unomi :: Extension :: Web Tracker :: Wab
> 217 │ Resolved │ │ cluster/local │ │ 1.6.0.SNAPSHOT │
> jCustomer :: Plugins :: Scripting :: Bundle
> 223 │ Resolved │ │ cluster/local │ │ 3.13.2 │
> JLine JANSI Terminal
> 244 │ Resolved │ │ cluster/local │ │ 3.23.8 │
> Swagger UI
> 247 │ Resolved │ │ cluster/local │ │ 0 │
> wrap_file__Users_kevan_Servers_jcustomer-1.6.0-SNAPSHOT_system_org_apache_kafka_kafka-clients_0.10.1.0_kafka-clients-0.10.1.0.jar{noformat}
> As you can see even with a fresh install of jcustomer the cluster state is
> incorrect after the startup of unomi.
> This will cause issues when a node will join the cluster it will synchronize
> on this state, making all Unomi bundles not started on the joining node.
> Since the cluster sync is not handle properly with unomi bundle lifecycle I'm
> ok to disable the sync. so here is
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
