Conrad, The Processor will only be scheduled to run on the Primary Node. However, it will be initialized on all nodes. It looks like the initialization step is where the Processor is opening the listening port.
We should probably reconsider this in the future. It may make sense to instead run the initialization logic only on the Primary Node and then run the shutdown logic if the Node loses its designation as Primary. Right now, though, all of this happens on each node. It is just that the other nodes are not triggered to perform their tasks. Thanks -Mark > On Mar 17, 2016, at 8:01 AM, Conrad Crampton <[email protected]> > wrote: > > Hi, > I have a ListenSyslog processor set to run ‘On primary node’ only as its > scheduling strategy with a port set in properties as expected. However, when > it runs there are errors being reported that it can’t bind to that port on > other nodes in my cluster (other than the primary node) which I am surprised > it is trying to do given the scheduling strategy. It would appear that it is > actually running (or trying to) on all nodes and therefore ignoring the > scheduling strategy. The other ports are actually being used on the other > nodes so the errors themselves are unsurprising, it is that fact that I > wouldn’t expect the processor to be running on them at all. > > Is this behaviour expected? > > Thanks > Conrad > > 6 node cluster v0.5.1, NCM on own server. > > > SecureData, combating cyber threats > > The information contained in this message or any of its attachments may be > privileged and confidential and intended for the exclusive use of the > intended recipient. If you are not the intended recipient any disclosure, > reproduction, distribution or other dissemination or use of this > communications is strictly prohibited. The views expressed in this email are > those of the individual and not necessarily of SecureData Europe Ltd. Any > prices quoted are only valid if followed up by a formal written quote. > > SecureData Europe Limited. Registered in England & Wales 04365896. Registered > Address: SecureData House, Hermitage Court, Hermitage Lane, Maidstone, Kent, > ME16 9NT >
