Grokbase Groups Camel dev May 2016

On Wed, Jun 1, 2016 at 7:34 PM, Matt Pavlovich wrote:


I could see a lot of value in having this feature for file://, ftp:// and
several other components as well.

Are you thinking Context or Route level or both?
At first it should be route level as that is the most common use case.
Also its easier to implement as there is one route in the question.

If its context level, then you need to keep track of more, such as all
routes and figure out when to fail if any of those routes starts to
have problems. But down the road we should allow both levels.

To aid both we should also look at introducing some health API in
camel-core, so that makes this easier as well. So you can check for
health status on context / routes level. And custom components can
implement custom logic to check their health, such as connecting to a
FTP server and do a FTP list, or do a HTTP remote call etc.


On 5/28/16 2:52 AM, Claus Ibsen wrote:


We have a few components that offer capability to run a Camel routes
in master/slave mode, where one node is elected as master and only
runs the route at that node, and the other nodes are in slave mode,
and then will failover if needed.

For example camel-zookeeper, and camel-quartz can do that. And now
also camel-consul. And possible others I have forgot.

I wonder if we should introduce some API those components
implementations can implement so we would better be able to manage and
know about this. Then we can have JMX information about routes being
in master/slave mode, and you can see for example in a 4 node cluster
that its node-b that is the master.

node-a route-foo: slave
node-b route-foo: master
node-c route-foo: slave
node-d route-foo: slave

We have a bit old JIRA ticket about this:

Claus Ibsen
----------------- @davsclaus
Camel in Action 2:

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 8 | next ›
Discussion Overview
groupdev @
postedMay 28, '16 at 7:52a
activeJun 7, '16 at 2:13p



site design / logo © 2019 Grokbase