Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-13944

Unable to disable explore on CM or Ambari clusters

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.0.0
    • Fix Version/s: None
    • Component/s: Explore
    • Labels:
      None
    • Rank:
      1|i00fkf:

      Description

      Right now, it is impossible to disable explore service on CM or Ambari clusters.
      The following error will be encountered:

      2018-07-27 05:14:54,371 WARN org.apache.twill.internal.zookeeper.LeaderElection: Exception thrown when calling leader() method. Withdraw from the leader election process.
      java.lang.IllegalArgumentException: Runnable explore.service is not defined in the application.
              at com.google.common.base.Preconditions.checkArgument(Preconditions.java:119) ~[com.google.guava.guava-13.0.1.jar:na]
              at org.apache.twill.yarn.YarnTwillPreparer.confirmRunnableName(YarnTwillPreparer.java:175) ~[org.apache.twill.twill-yarn-0.13.0.jar:0.13.0]
              at org.apache.twill.yarn.YarnTwillPreparer.withConfiguration(YarnTwillPreparer.java:189) ~[org.apache.twill.twill-yarn-0.13.0.jar:0.13.0]
              at co.cask.cdap.data.runtime.main.MasterServiceMain$MasterLeaderElectionHandler.prepareServiceConfig(MasterServiceMain.java:1057) ~[na:na]
              at co.cask.cdap.data.runtime.main.MasterServiceMain$MasterLeaderElectionHandler.startTwillApplication(MasterServiceMain.java:967) ~[na:na]
              at co.cask.cdap.data.runtime.main.MasterServiceMain$MasterLeaderElectionHandler.monitorTwillApplication(MasterServiceMain.java:793) ~[na:na]
              at co.cask.cdap.data.runtime.main.MasterServiceMain$MasterLeaderElectionHandler.leader(MasterServiceMain.java:668) ~[na:na]
              at org.apache.twill.internal.zookeeper.LeaderElection.becomeLeader(LeaderElection.java:234) [org.apache.twill.twill-zookeeper-0.13.0.jar:0.13.0]
              at org.apache.twill.internal.zookeeper.LeaderElection.access$1900(LeaderElection.java:54) [org.apache.twill.twill-zookeeper-0.13.0.jar:0.13.0]
              at org.apache.twill.internal.zookeeper.LeaderElection$5.onSuccess(LeaderElection.java:212) [org.apache.twill.twill-zookeeper-0.13.0.jar:0.13.0]
              at org.apache.twill.internal.zookeeper.LeaderElection$5.onSuccess(LeaderElection.java:191) [org.apache.twill.twill-zookeeper-0.13.0.jar:0.13.0]
              at com.google.common.util.concurrent.Futures$6.run(Futures.java:799) [com.google.guava.guava-13.0.1.jar:na]
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_161]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_161]
              at java.lang.Thread.run(Thread.java:748) [na:1.8.0_161] 

      This will also happen on other clusters (4.3.0 onwards) if explore is disabled and there is a cdap-site.xml configuration with the prefix "explore.executor.twill.". This is due to the changes inĀ https://github.com/caskdata/cdap/pull/9351.
      Ambari and CM clusters have such configurations by default, sinceĀ https://issues.cask.co/browse/CDAP-12767.

      A fix would be to ignore the "explore.executor.twill." configurations when explore is disabled.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                shankar Shankar Selvam
                Reporter:
                ali.anwar Ali Anwar
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: