[
https://issues.apache.org/jira/browse/TAJO-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153208#comment-14153208
]
Jongyoung Park commented on TAJO-1065:
--------------------------------------
The cause is set of worker status is different between one of client and one of
server.
For example, client was checking "LIVE", not "RUNNING". But, server sends a
status "RUNNING" for a live node.
> The \admin -cluster argument doesn't run as expected.
> -----------------------------------------------------
>
> Key: TAJO-1065
> URL: https://issues.apache.org/jira/browse/TAJO-1065
> Project: Tajo
> Issue Type: Bug
> Components: cli
> Reporter: Jaehwa Jung
> Assignee: Jongyoung Park
> Priority: Minor
> Labels: newbie
>
> Currently, tajo command-line interface provides utilities for administrator.
> But the -cluster argument doesn't run as expected. It just print zero even
> thought there are one or more running daemons as follows:
> {code:xml}
> default> \admin -cluster;
> Query Master
> ============
> Live Dead Tasks
> ----- ----- -----
> 0 0 0
> Live QueryMasters
> =================
> No Live QueryMasters
> Worker
> ======
> Live Dead
> ----- -----
> 0 0
> Live Workers
> ============
> No Live Workers
> Dead Workers
> ============
> No Dead Workers
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
