Accumulo
  1. Accumulo
  2. ACCUMULO-2150

IllegalArgument while checking on recovery job

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.4.5
    • Fix Version/s: None
    • Component/s: master
    • Labels:
      None

      Description

      I had this error come up while running a continuous ingest with agitation on 1.4.5-SNAPSHOT

      Error checking on job
      	java.lang.IllegalArgumentException: Path cannot be null
      		at org.apache.zookeeper.common.PathUtils.validatePath(PathUtils.java:45)
      		at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1020)
      		at org.apache.accumulo.core.zookeeper.ZooCache$2.run(ZooCache.java:208)
      		at org.apache.accumulo.core.zookeeper.ZooCache.retry(ZooCache.java:130)
      		at org.apache.accumulo.core.zookeeper.ZooCache.get(ZooCache.java:233)
      		at org.apache.accumulo.core.zookeeper.ZooCache.get(ZooCache.java:188)
      		at org.apache.accumulo.server.master.CoordinateRecoveryTask$RecoveryJob.isComplete(CoordinateRecoveryTask.java:176)
      		at org.apache.accumulo.server.master.CoordinateRecoveryTask.run(CoordinateRecoveryTask.java:374)
      		at org.apache.accumulo.core.util.LoggingRunnable.run(LoggingRunnable.java:34)
      		at java.lang.Thread.run(Thread.java:662)
      
      

      Haven't chased it down enough yet to know if it impacts other versions.

        Activity

        Hide
        Mike Drob added a comment -

        Development on 1.4 branch is EOL, please re-open if you see this on a newer version.

        Show
        Mike Drob added a comment - Development on 1.4 branch is EOL, please re-open if you see this on a newer version.
        Hide
        Mike Drob added a comment -

        Saw this again - it seems to happen shortly after losing a tserver.

        Show
        Mike Drob added a comment - Saw this again - it seems to happen shortly after losing a tserver.
        Hide
        Mike Drob added a comment -

        Saw this same error on a stock 1.4.4 cluster, which is to be expected, I imagine.

        Show
        Mike Drob added a comment - Saw this same error on a stock 1.4.4 cluster, which is to be expected, I imagine.
        Hide
        Sean Busbey added a comment -

        AFAICT, no. The message pops up occasionally, but the cluster is still recovering and moving on.

        Show
        Sean Busbey added a comment - AFAICT, no. The message pops up occasionally, but the cluster is still recovering and moving on.
        Hide
        Keith Turner added a comment -

        Did this prevent recovery from happening?

        Show
        Keith Turner added a comment - Did this prevent recovery from happening?

          People

          • Assignee:
            Unassigned
            Reporter:
            Sean Busbey
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development