Please test the code I just pushed. Have a look at the test class WorkflowManagerStateSampler for an example of a sampling state checker. You can copy that class or write something based on it.

from workflow.

Will the newly added 'WorkflowAdmin.getWorkflowManagerState' work with prior versions? Or, is the state a new attribute requiring the scheduling and execution to also use the updated code?

from workflow.

Yeah it works with old versions. It only analyzes the manager it's called from.

Jordan Zimmerman

On Apr 1, 2016, at 1:56 PM, Jim Bugwadia [email protected] wrote:

Will the newly added 'WorkflowAdmin.getWorkflowManagerState' work with prior versions? Or, is the state a new attribute requiring the scheduling and execution to also use the updated code?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

from workflow.

Thanks! This works and I am able to retrieve the state. Here is what I got back:

WorkflowManagerState{isConnectedToZooKeeper=true, schedulerState=LATENT, consumersState=[]}

Can you please explain the schedule and consumer states?

from workflow.

That means that that manager is not the scheduler. More importantly it means it has no task executors. Any idea why?

Jordan Zimmerman

On Apr 1, 2016, at 2:41 PM, Jim Bugwadia [email protected] wrote:

Thanks! This works and I am able to retrieve the state. Here is what I got back:

WorkflowManagerState{isConnectedToZooKeeper=true, schedulerState=LATENT, consumersState=[]}

Can you please explain the schedule and consumer states?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

from workflow.

I connected a new WorkflowManager, from a test program solely to query the
state of the workflow.

Is there a way we can print the state of all other WorkflowManager
instances from this?

Thanks,

Jim

On Fri, Apr 1, 2016 at 1:04 PM, Jordan Zimmerman [email protected]
wrote:

That means that that manager is not the scheduler. More importantly it
means it has no task executors. Any idea why?

Jordan Zimmerman

On Apr 1, 2016, at 2:41 PM, Jim Bugwadia [email protected]
wrote:

Thanks! This works and I am able to retrieve the state. Here is what I
got back:

WorkflowManagerState{isConnectedToZooKeeper=true, schedulerState=LATENT,
consumersState=[]}

Can you please explain the schedule and consumer states?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#25 (comment)

from workflow.

No. That would require major work

Jordan Zimmerman

On Apr 1, 2016, at 3:29 PM, Jim Bugwadia [email protected] wrote:

I connected a new WorkflowManager, from a test program solely to query the
state of the workflow.

Is there a way we can print the state of all other WorkflowManager
instances from this?

Thanks,

Jim

On Fri, Apr 1, 2016 at 1:04 PM, Jordan Zimmerman [email protected]
wrote:

That means that that manager is not the scheduler. More importantly it
means it has no task executors. Any idea why?

Jordan Zimmerman

On Apr 1, 2016, at 2:41 PM, Jim Bugwadia [email protected]
wrote:

Thanks! This works and I am able to retrieve the state. Here is what I
got back:

WorkflowManagerState{isConnectedToZooKeeper=true, schedulerState=LATENT,
consumersState=[]}

Can you please explain the schedule and consumer states?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#25 (comment)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

from workflow.

OK if I close this?

from workflow.

Yes, thanks!

On Tue, May 10, 2016 at 9:45 AM, Jordan Zimmerman [email protected]
wrote:

OK if I close this?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#25 (comment)

from workflow.