Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1143

TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup

    Details

      Description

      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.

        Activity

        Hide
        hyunsik Hyunsik Choi added a comment -

        We also should check Hadoop version for runtime.

        Show
        hyunsik Hyunsik Choi added a comment - We also should check Hadoop version for runtime.
        Hide
        ykrips Jihun Kang added a comment -

        Did you start a work on this issue? If you don't, can I start to work on it?

        Show
        ykrips Jihun Kang added a comment - Did you start a work on this issue? If you don't, can I start to work on it?
        Hide
        hyunsik Hyunsik Choi added a comment -

        Sure, you can start this issue. I didn't start this issue

        Thank you!

        Show
        hyunsik Hyunsik Choi added a comment - Sure, you can start this issue. I didn't start this issue Thank you!
        Hide
        githubbot ASF GitHub Bot added a comment -

        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 <ykrips@gmail.com>
        Date: 2014-12-03T08:50:23Z

        TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup

        commit 792b8540fc28800bacad51576de666675c4c41aa
        Author: Jihun Kang <ykrips@gmail.com>
        Date: 2014-12-03T11:47:01Z

        TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup

        commit 0b6ff69bf604357c2011fcfd945a63a80fcede7e
        Author: Jihun Kang <ykrips@gmail.com>
        Date: 2014-12-03T11:58:42Z

        TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup


        Show
        githubbot ASF GitHub Bot added a comment - 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 <ykrips@gmail.com> Date: 2014-12-03T08:50:23Z TAJO-1143 : TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup commit 792b8540fc28800bacad51576de666675c4c41aa Author: Jihun Kang <ykrips@gmail.com> Date: 2014-12-03T11:47:01Z TAJO-1143 : TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup commit 0b6ff69bf604357c2011fcfd945a63a80fcede7e Author: Jihun Kang <ykrips@gmail.com> Date: 2014-12-03T11:58:42Z TAJO-1143 : TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65643665

        Hello @hyunsik ,
        Thank you for your appreciation.
        I totally understand what a diagnosis phase have. This is my missing point, and I will add it to this patch.

        Now let's discuss about the naming issue. At first, I feel that this rule engine and some pre-defined rules will cover overall functionalities of Tajo cluster components. For instance, these rules will check or verify status of connectivity, configurations, and so on. With my rule design, I gave a general name to these classes. Otherwise, I think that it could be limiting the scope of rule implementation.

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65643665 Hello @hyunsik , Thank you for your appreciation. I totally understand what a diagnosis phase have. This is my missing point, and I will add it to this patch. Now let's discuss about the naming issue. At first, I feel that this rule engine and some pre-defined rules will cover overall functionalities of Tajo cluster components. For instance, these rules will check or verify status of connectivity, configurations, and so on. With my rule design, I gave a general name to these classes. Otherwise, I think that it could be limiting the scope of rule implementation.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65756490

        Hello @hyunsik,
        Some defined rules has created for TajoMaster and TajoWorker. However, I don't have much idea about the startup issues. Do you have any idea for preconditions before these cluster components start up?

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65756490 Hello @hyunsik, Some defined rules has created for TajoMaster and TajoWorker. However, I don't have much idea about the startup issues. Do you have any idea for preconditions before these cluster components start up?
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user hyunsik commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65756856

        Hi @ykrips,

        I agree with your direction. As you mentioned, this rule engine and some pre-defined rules will cover overall functionalities of Tajo cluster components. So, I'd like to suggest the word 'self diagnosis'. I believe this work is proper to this direction.

        I'll also give some appropriate code locations which are nice to verify such rules shortly.

        Show
        githubbot ASF GitHub Bot added a comment - Github user hyunsik commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65756856 Hi @ykrips, I agree with your direction. As you mentioned, this rule engine and some pre-defined rules will cover overall functionalities of Tajo cluster components. So, I'd like to suggest the word 'self diagnosis'. I believe this work is proper to this direction. I'll also give some appropriate code locations which are nice to verify such rules shortly.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user hyunsik commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65757536

        I think that around ```checkAndInitializeSystemDirectories()``` method would be the best place for the startup diagnosis of TajoMaster. Also, serviceInit() would be the best place for TajoWorker. The constructor of TajoClient would best.

        Your patch already includes two rules: Hadoop runtime version check and TajoConf verification. Both are necessary in TajoMaster and TajoWorker components. Since Hadoop dependency will be removed from TajoClient (see https://issues.apache.org/jira/browse/TAJO-1160), only TajoConf verification would be necessary in TajoClient.

        Cheers,
        Hyunsik

        Show
        githubbot ASF GitHub Bot added a comment - Github user hyunsik commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65757536 I think that around ```checkAndInitializeSystemDirectories()``` method would be the best place for the startup diagnosis of TajoMaster. Also, serviceInit() would be the best place for TajoWorker. The constructor of TajoClient would best. Your patch already includes two rules: Hadoop runtime version check and TajoConf verification. Both are necessary in TajoMaster and TajoWorker components. Since Hadoop dependency will be removed from TajoClient (see https://issues.apache.org/jira/browse/TAJO-1160 ), only TajoConf verification would be necessary in TajoClient. Cheers, Hyunsik
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65758611

        Thank you for your quick review.
        I agree with your suggestion, and will fix up my patch.

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65758611 Thank you for your quick review. I agree with your suggestion, and will fix up my patch.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-65761937

        @hyunsik,
        I have uploaded a modified patch set to this issue. If you have additional suggestions on this issue, feel free to leave a comment on this page.

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-65761937 @hyunsik, I have uploaded a modified patch set to this issue. If you have additional suggestions on this issue, feel free to leave a comment on this page.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user hyunsik commented on a diff in the pull request:

        https://github.com/apache/tajo/pull/280#discussion_r21502424

        — Diff: tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java —
        @@ -278,6 +283,16 @@ private void checkAndInitializeSystemDirectories() throws IOException

        { LOG.info("Staging dir '" + stagingPath + "' is created"); }

        }
        +
        + private void evaluatePredefinedRules() throws EvaluationFailedException {
        — End diff –

        In my opinion, using predefined rules seem to be general. I'd like to recommend doSelfDiagnosis(), diagnoseSystem(), or diagnoseTajoMaster. It's just a suggestion Similarly, we may be need to rethink the names in TajoClient and TajoWorker.

        Show
        githubbot ASF GitHub Bot added a comment - Github user hyunsik commented on a diff in the pull request: https://github.com/apache/tajo/pull/280#discussion_r21502424 — Diff: tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java — @@ -278,6 +283,16 @@ private void checkAndInitializeSystemDirectories() throws IOException { LOG.info("Staging dir '" + stagingPath + "' is created"); } } + + private void evaluatePredefinedRules() throws EvaluationFailedException { — End diff – In my opinion, using predefined rules seem to be general. I'd like to recommend doSelfDiagnosis(), diagnoseSystem(), or diagnoseTajoMaster. It's just a suggestion Similarly, we may be need to rethink the names in TajoClient and TajoWorker.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user hyunsik commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-66222070

        Hi @ykrips,

        This patch needs to be rebased against the latest revision. But, since it's trivial, I reviewed the patch. It would be happy if you rebase it.

        The patch seems to be ready to be committed, and it's excellent design and implementation. I leave one trivial suggestion.

        Show
        githubbot ASF GitHub Bot added a comment - Github user hyunsik commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-66222070 Hi @ykrips, This patch needs to be rebased against the latest revision. But, since it's trivial, I reviewed the patch. It would be happy if you rebase it. The patch seems to be ready to be committed, and it's excellent design and implementation. I leave one trivial suggestion.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on the pull request:

        https://github.com/apache/tajo/pull/280#issuecomment-66232739

        Hello @hyunsik,
        No problems. I will rebase it, and upload a change in a short time.

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on the pull request: https://github.com/apache/tajo/pull/280#issuecomment-66232739 Hello @hyunsik, No problems. I will rebase it, and upload a change in a short time.
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user ykrips commented on a diff in the pull request:

        https://github.com/apache/tajo/pull/280#discussion_r21506582

        — Diff: tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java —
        @@ -278,6 +283,16 @@ private void checkAndInitializeSystemDirectories() throws IOException

        { LOG.info("Staging dir '" + stagingPath + "' is created"); }

        }
        +
        + private void evaluatePredefinedRules() throws EvaluationFailedException {
        — End diff –

        Oh, I understand. You want to emphasize the purpose of this feature. I think, it looks better to append the component name to suffix of function name. I will commit my code changes shortly.

        Show
        githubbot ASF GitHub Bot added a comment - Github user ykrips commented on a diff in the pull request: https://github.com/apache/tajo/pull/280#discussion_r21506582 — Diff: tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java — @@ -278,6 +283,16 @@ private void checkAndInitializeSystemDirectories() throws IOException { LOG.info("Staging dir '" + stagingPath + "' is created"); } } + + private void evaluatePredefinedRules() throws EvaluationFailedException { — End diff – Oh, I understand. You want to emphasize the purpose of this feature. I think, it looks better to append the component name to suffix of function name. I will commit my code changes shortly.
        Hide
        githubbot ASF GitHub Bot added a comment -

        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!

        Show
        githubbot ASF GitHub Bot added a comment - 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!
        Hide
        githubbot ASF GitHub Bot added a comment -

        Github user asfgit closed the pull request at:

        https://github.com/apache/tajo/pull/280

        Show
        githubbot ASF GitHub Bot added a comment - Github user asfgit closed the pull request at: https://github.com/apache/tajo/pull/280
        Hide
        hyunsik Hyunsik Choi added a comment -

        I just committed to master branch. Thanks!

        Show
        hyunsik Hyunsik Choi added a comment - I just committed to master branch. Thanks!
        Hide
        hudson Hudson added a comment -

        SUCCESS: Integrated in Tajo-master-build #494 (See https://builds.apache.org/job/Tajo-master-build/494/)
        TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup (hyunsik: rev a0d67bb60ea995dc2c0ad014a8b71852e936cd56)

        • tajo-common/src/main/java/org/apache/tajo/rule/base/BaseRuleProvider.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleProvider.java
        • tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java
        • tajo-core/src/main/java/org/apache/tajo/worker/TajoWorker.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRule.java
        • CHANGES
        • tajo-common/src/main/java/org/apache/tajo/rule/base/TajoConfValidationRule.java
        • tajo-common/src/test/java/org/apache/tajo/rule/TestRuleEngine.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationResult.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationContext.java
        • tajo-common/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider
        • tajo-client/src/main/java/org/apache/tajo/client/TajoClientImpl.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleSession.java
        • tajo-common/src/main/java/org/apache/tajo/rule/base/CheckHadoopRuntimeVersionRule.java
        • tajo-core/src/main/java/org/apache/tajo/worker/rule/WorkerRuleProvider.java
        • tajo-core/src/main/java/org/apache/tajo/master/rule/FileSystemRule.java
        • tajo-core/src/test/java/org/apache/tajo/master/rule/TestMasterRules.java
        • tajo-core/src/main/java/org/apache/tajo/worker/rule/ConnectivityCheckerRuleForTajoWorker.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleVisibility.java
        • tajo-common/src/test/java/org/apache/tajo/rule/TestRuleSession.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleEngine.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationFailedException.java
        • tajo-core/src/main/java/org/apache/tajo/master/rule/MasterRuleProvider.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleDefinition.java
        • tajo-common/pom.xml
        • tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java
        • tajo-core/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider
        • tajo-core/pom.xml
        Show
        hudson Hudson added a comment - SUCCESS: Integrated in Tajo-master-build #494 (See https://builds.apache.org/job/Tajo-master-build/494/ ) TAJO-1143 : TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup (hyunsik: rev a0d67bb60ea995dc2c0ad014a8b71852e936cd56) tajo-common/src/main/java/org/apache/tajo/rule/base/BaseRuleProvider.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleProvider.java tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java tajo-core/src/main/java/org/apache/tajo/worker/TajoWorker.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRule.java CHANGES tajo-common/src/main/java/org/apache/tajo/rule/base/TajoConfValidationRule.java tajo-common/src/test/java/org/apache/tajo/rule/TestRuleEngine.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationResult.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationContext.java tajo-common/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider tajo-client/src/main/java/org/apache/tajo/client/TajoClientImpl.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleSession.java tajo-common/src/main/java/org/apache/tajo/rule/base/CheckHadoopRuntimeVersionRule.java tajo-core/src/main/java/org/apache/tajo/worker/rule/WorkerRuleProvider.java tajo-core/src/main/java/org/apache/tajo/master/rule/FileSystemRule.java tajo-core/src/test/java/org/apache/tajo/master/rule/TestMasterRules.java tajo-core/src/main/java/org/apache/tajo/worker/rule/ConnectivityCheckerRuleForTajoWorker.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleVisibility.java tajo-common/src/test/java/org/apache/tajo/rule/TestRuleSession.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleEngine.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationFailedException.java tajo-core/src/main/java/org/apache/tajo/master/rule/MasterRuleProvider.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleDefinition.java tajo-common/pom.xml tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java tajo-core/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider tajo-core/pom.xml
        Hide
        hudson Hudson added a comment -

        FAILURE: Integrated in Tajo-master-CODEGEN-build #135 (See https://builds.apache.org/job/Tajo-master-CODEGEN-build/135/)
        TAJO-1143: TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup (hyunsik: rev a0d67bb60ea995dc2c0ad014a8b71852e936cd56)

        • tajo-common/src/main/java/org/apache/tajo/rule/base/BaseRuleProvider.java
        • tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRule.java
        • tajo-common/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleVisibility.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleSession.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationFailedException.java
        • tajo-common/src/test/java/org/apache/tajo/rule/TestRuleSession.java
        • tajo-core/src/test/java/org/apache/tajo/master/rule/TestMasterRules.java
        • tajo-core/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider
        • tajo-common/src/test/java/org/apache/tajo/rule/TestRuleEngine.java
        • tajo-core/src/main/java/org/apache/tajo/master/rule/FileSystemRule.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationResult.java
        • tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleEngine.java
        • tajo-common/src/main/java/org/apache/tajo/rule/base/CheckHadoopRuntimeVersionRule.java
        • tajo-core/src/main/java/org/apache/tajo/worker/TajoWorker.java
        • tajo-core/src/main/java/org/apache/tajo/master/rule/MasterRuleProvider.java
        • tajo-core/src/main/java/org/apache/tajo/worker/rule/WorkerRuleProvider.java
        • tajo-core/pom.xml
        • tajo-common/src/main/java/org/apache/tajo/rule/base/TajoConfValidationRule.java
        • CHANGES
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleProvider.java
        • tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleDefinition.java
        • tajo-core/src/main/java/org/apache/tajo/worker/rule/ConnectivityCheckerRuleForTajoWorker.java
        • tajo-common/pom.xml
        • tajo-client/src/main/java/org/apache/tajo/client/TajoClientImpl.java
        • tajo-common/src/main/java/org/apache/tajo/rule/EvaluationContext.java
        Show
        hudson Hudson added a comment - FAILURE: Integrated in Tajo-master-CODEGEN-build #135 (See https://builds.apache.org/job/Tajo-master-CODEGEN-build/135/ ) TAJO-1143 : TajoMaster, TajoWorker, and TajoClient should have diagnosis phase at startup (hyunsik: rev a0d67bb60ea995dc2c0ad014a8b71852e936cd56) tajo-common/src/main/java/org/apache/tajo/rule/base/BaseRuleProvider.java tajo-core/src/main/java/org/apache/tajo/master/TajoMaster.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRule.java tajo-common/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleVisibility.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleSession.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationFailedException.java tajo-common/src/test/java/org/apache/tajo/rule/TestRuleSession.java tajo-core/src/test/java/org/apache/tajo/master/rule/TestMasterRules.java tajo-core/src/main/resources/META-INF/services/org.apache.tajo.rule.SelfDiagnosisRuleProvider tajo-common/src/test/java/org/apache/tajo/rule/TestRuleEngine.java tajo-core/src/main/java/org/apache/tajo/master/rule/FileSystemRule.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationResult.java tajo-common/src/main/java/org/apache/tajo/conf/TajoConf.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleEngine.java tajo-common/src/main/java/org/apache/tajo/rule/base/CheckHadoopRuntimeVersionRule.java tajo-core/src/main/java/org/apache/tajo/worker/TajoWorker.java tajo-core/src/main/java/org/apache/tajo/master/rule/MasterRuleProvider.java tajo-core/src/main/java/org/apache/tajo/worker/rule/WorkerRuleProvider.java tajo-core/pom.xml tajo-common/src/main/java/org/apache/tajo/rule/base/TajoConfValidationRule.java CHANGES tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleProvider.java tajo-common/src/main/java/org/apache/tajo/rule/SelfDiagnosisRuleDefinition.java tajo-core/src/main/java/org/apache/tajo/worker/rule/ConnectivityCheckerRuleForTajoWorker.java tajo-common/pom.xml tajo-client/src/main/java/org/apache/tajo/client/TajoClientImpl.java tajo-common/src/main/java/org/apache/tajo/rule/EvaluationContext.java

          People

          • Assignee:
            ykrips Jihun Kang
            Reporter:
            hyunsik Hyunsik Choi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development