apache/hadoop · error · IllegalArgumentException

The path {target} does not contain scheme and authority thus

Error message

The path {target} does not contain scheme and authority thus cannot identify its name service

What it means

Error "The path {target} does not contain scheme and authority thus cannot identify its name service" thrown in apache/hadoop.

Source

Thrown at hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/mover/Mover.java:804

          map.put(namenode, null);
        }
        return map;
      }
      final URI singleNs = namenodes.size() == 1 ?
          namenodes.iterator().next() : null;
      for (String path : paths) {
        Path target = new Path(path);
        if (!target.isUriPathAbsolute()) {
          throw new IllegalArgumentException("The path " + target
              + " is not absolute");
        }
        URI targetUri = target.toUri();
        if ((targetUri.getAuthority() == null || targetUri.getScheme() ==
            null) && singleNs == null) {
          // each path must contains both scheme and authority information
          // unless there is only one name service specified in the
          // configuration
          throw new IllegalArgumentException("The path " + target
              + " does not contain scheme and authority thus cannot identify"
              + " its name service");
        }
        URI key = singleNs;
        if (singleNs == null) {
          key = new URI(targetUri.getScheme(), targetUri.getAuthority(),
              null, null, null);
          if (!namenodes.contains(key)) {
            throw new IllegalArgumentException("Cannot resolve the path " +
                target + ". The namenode services specified in the " +
                "configuration: " + namenodes);
          }
        }
        List<Path> targets = map.get(key);
        if (targets == null) {
          targets = Lists.newArrayList();
          map.put(key, targets);
        }

View on GitHub (pinned to 2add963021)

Solutions

1. Provide a fully qualified path including scheme and authority (e.g. hdfs://nn:8020/dir) or configure default fs so the name service can be identified.
2. Ensure fs.defaultFS in core-site.xml matches the intended name service.

When it happens

Trigger: Mover invocation with a path lacking scheme/authority in an HA or multi-nameservice setup, so the target nameservice cannot be determined.

Common situations: See trigger scenarios.

AI-assisted analysis of apache/hadoop@2add963021 (2026-08-22). Data as JSON: /api/errors/3238dff25d87ea2d. Report an issue: GitHub.