Cellar Feature Synchronization Issue: Service/Route fail to restart automatically after restarting Cellar node.

 

Overview

The following scenarios can be observed due to synchronization failure.  

1. Routes that are deployed on a TalendESB configured in Cellar node, do not restart automatically after restarting Cellar node. The feature

associated to the Route needs to be manually installed to start the Route. This means that one need to type "feature install"

command in order to manually reinstall route's feature which installs and starts the Route.

2. When one has the same feature name installed on a cluster group (but with different version),

restarting a Cellar node causes overlap between the two features. This causes failure in starting Service/Route associated to the feature.

Environment

TalendESB,Cellar

Symptoms/Description

There are 2 different symptoms to same problem.

Symptom/Description 1:
An environment consists of 3 TalendESB, each on a distinct physical server, and grouped in a single Cellar Cluster.

Steps to reproduce this scenario:

1. Restart one of the 3 TalendESB that are currently active. Some of the Routes that are currently deployed do not restart
automatically.

2.Type command "camel:context-list". One observes that contexts have been destroyed for these Routes.

3. One needs to type "feature install" command in order to manually reinstall feature. This installs and starts the associated Routes.

Symptom/Description 2:
An environment consists of 3 TalendESB(server1,server2,server3), each on a distinct physical server, and grouped in a single Cellar Cluster. “Cluster1”.

A feature say "XXXYYService-feature" is published and available in Artifact Repository in 2 versions namely 0.1.1 and 0.1.2

Steps to reproduce this scenario:

1. Feature version 0.1.2 deployed on a fresh Cluster1, works correctly. The Route/Service associated to this feature is
up and running. Restarting one node of the cluster don’t cause any issues.

2. Deploy feature version 0.1.1 on to Cluster1. Restart server1.

3. Route/Service associated to the feature version  is not more available in server1 or server2.

Resolution

The problem is linked to the synchronization of the TalendESB when it starts in Cellar Node.

Resolution is to disable the Cellar features sync.

This can be done by editing the file in container/etc/org.apache.karaf.cellar.groups.cfg

Change the following entries.

default.features.sync = false

Version History
Revision #:
1 of 1
Last update:
‎04-13-2017 09:19 PM
Updated by:
 
Labels (1)
Contributors