[
https://issues.apache.org/jira/browse/TAJO-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092336#comment-14092336
]
ASF GitHub Bot commented on TAJO-985:
-------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/99#discussion_r16035452
--- Diff:
tajo-core/src/main/java/org/apache/tajo/master/querymaster/Query.java ---
@@ -337,15 +340,24 @@ public SubQuery getSubQuery(ExecutionBlockId id) {
return this.subqueries.values();
}
- public QueryState getState() {
- readLock.lock();
- try {
- return stateMachine.getCurrentState();
- } finally {
- readLock.unlock();
+ protected QueryState getState(boolean async) {
--- End diff --
I think that the variable name ```async``` should be nonblocking.
> Client API should be async
> --------------------------
>
> Key: TAJO-985
> URL: https://issues.apache.org/jira/browse/TAJO-985
> Project: Tajo
> Issue Type: Bug
> Components: query master
> Affects Versions: 0.9.0
> Reporter: Jinho Kim
> Assignee: Jinho Kim
>
> The query status synchronization on state machine always wait for time (event
> processing time) before status changes. If a lot of time are being processed
> to the event dispatcher, client api(getStatus, getProgress) will be waiting
> for changed event status. and query will be session timed out.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
