Thanks Koji. We tried terminating and it is not working for QueryCassandra processor particularly. The QueryCassandra just refuse to start complaining processor is still in STOPPING state.
Regards, Dnyaneshwar Pawar -----Original Message----- From: Koji Kawamura <[email protected]> Sent: Thursday, November 15, 2018 1:22 PM To: [email protected] Subject: Re: Edit QueryCassandra processor using REST API. Hi Dnyaneshwar, You can terminate remaining thread forcefully by sending a DELETE request to /processors/{id}/threads. https://nifi.apache.org/docs/nifi-docs/rest-api/index.html Thanks, Koji On Thu, Nov 15, 2018 at 4:14 PM Dnyaneshwar Pawar <[email protected]> wrote: > > Hi > > We are trying to edit the QueryCassandra processor using REST API, this > needs processor to be stopped programmatically and start post changes done. > In this processes, initially we were getting issue of processor taking time > to stop. We added wait time of 10 sec and that worked. However, the recent > observation is, sometime processor stuck in STOPPING state and never goes > down in 10 sec time. > > This does not allow start of the processor and that processor remains in > the stopped/stopping state. PFB Error log: > > 6a4bf199-4071-3823-04c1-fa4fe9fba79b cannot be started because it is > not stopped. Current state is STOPPING > > > > We know we can get the processor state by REST URL, however, sometime this > processor stuck in the STOPPING state. Is there any way to force stop this > processor or any max time limit at which processor will go down? > > > > > > > > > > > > Regards, > > Dnyaneshwar Pawar > > DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
