Jms queues guarantee only one of the clients will get each message. Unless you build it yourself, Flume doesn't have active/pasive. HA is achieved by having multiple agents running the same configuration.
On 2 March 2016 at 18:12, samnik60 . <[email protected]> wrote: > Hi guys, > I have the following queries about flume ng High Availability, > > - Is it possible to have active/active or active/standby flume agent? If > so kindly point me to a document to refer, i am unable to find it in flume > documentation. > > The Use Case i am trying to address, > > I want to run a flume agent in a node which will take events from a jms > queue and persist it in hdfs. If the flume agent goes down , i want another > flume agent running in another node to take over this responsiblity. ( > active/standby) > > I dont mind having both flume agents trying to process events from same > jms queue , provided a event is taken by only one flume agent without race > condition which i feel is not practical ( active/active). > > > Any information on this is greatly appreciated. > > Thanks, > Sam. > >
