Hyunsik Choi created TAJO-1143:
----------------------------------
Summary: 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
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)
