[
https://issues.apache.org/jira/browse/TAJO-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241603#comment-14241603
]
ASF GitHub Bot commented on TAJO-1143:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/280#issuecomment-66511922
+1
I've manually verified 'mvn clean install'. The patch looks good to me.
TravisCI showed one unit test failures. It's not related to this issue.
I'll file the failure in Jira.
Thank you Jihun for your contribution!
> TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup
> -----------------------------------------------------------------------------
>
> Key: TAJO-1143
> URL: https://issues.apache.org/jira/browse/TAJO-1143
> Project: Tajo
> Issue Type: Improvement
> Components: client, query master, tajo master
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
> Fix For: 0.9.1
>
>
> I propose that all cluster components (TajoMaster, TajoWorker, and
> TajoClient) in a Tajo cluster should have a diagnosis phase to eliminate or
> detect invalid situations prior to runtime query errors.
> For example, your query can cause some runtime exception due to wrong config
> after a query takes 2 hours. This situation is definitely not acceptable in
> production.
> I think that the diagnosis phase should check all configs, connectivities
> among cluster components, and status of workers.
> In detail, we need a diagnosis executor, extensible diagnosis rule interface,
> and its rules. Also, one of diagnosis rules would be TAJO-1114.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
