Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-3779

Disable cache pool reader thread when HDFS isn't running

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 2.2.4
    • Impala 2.7.0
    • Catalog

    Description

      When running Impala on s3 (without hdfs started) the logs every minute produce this error:
      E0622 17:11:31.581317 24069 CatalogServiceCatalog.java:197] Error loading cache pools:
      Java exception follows:
      java.lang.IllegalStateException
      at com.google.common.base.Preconditions.checkState(Preconditions.java:129)
      at com.cloudera.impala.common.FileSystemUtil.getDistributedFileSystem(FileSystemUtil.java:329)
      at com.cloudera.impala.catalog.CatalogServiceCatalog$CachePoolReader.run(CatalogServiceCatalog.java:190)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:745)
      I believe that this is because the catalog is checking for hdfs every minute: http://github.mtv.cloudera.com/CDH/Impala/blob/cdh5-trunk/fe/src/main/java/com/cloudera/impala/catalog/CatalogServiceCatalog.java#L163

      Attachments

        Activity

          People

            sailesh Sailesh Mukil
            alex.leblang_impala_e0fc Alex Leblang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: