[
https://issues.apache.org/jira/browse/TAJO-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232925#comment-14232925
]
ASF GitHub Bot commented on TAJO-1143:
--------------------------------------
GitHub user ykrips opened a pull request:
https://github.com/apache/tajo/pull/280
TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis
phase at startup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ykrips/tajo TAJO-1143
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/280.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #280
----
commit 6a9b795d282fd3e75587b9292a72ccac0ed99997
Author: Jihun Kang <[email protected]>
Date: 2014-12-03T08:50:23Z
TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis
phase at startup
commit 792b8540fc28800bacad51576de666675c4c41aa
Author: Jihun Kang <[email protected]>
Date: 2014-12-03T11:47:01Z
TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis
phase at startup
commit 0b6ff69bf604357c2011fcfd945a63a80fcede7e
Author: Jihun Kang <[email protected]>
Date: 2014-12-03T11:58:42Z
TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis
phase at startup
----
> 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)
