apache/hadoop · error · IOException
Outstanding satisfier queue limit: {} exceeded, try later!
Error message
Outstanding satisfier queue limit: {} exceeded, try later! What it means
Error "Outstanding satisfier queue limit: {} exceeded, try later!" thrown in apache/hadoop.
Source
Thrown at hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/sps/StoragePolicySatisfyManager.java:236
* storages.
*/
public Long getNextPathId() {
synchronized (pathsToBeTraversed) {
return pathsToBeTraversed.poll();
}
}
/**
* Verify that satisfier queue limit exceeds allowed outstanding limit.
* @throws IOException
*/
public void verifyOutstandingPathQLimit() throws IOException {
long size = pathsToBeTraversed.size();
// Checking that the SPS call Q exceeds the allowed limit.
if (outstandingPathsLimit - size <= 0) {
LOG.debug("Satisifer Q - outstanding limit:{}, current size:{}",
outstandingPathsLimit, size);
throw new IOException("Outstanding satisfier queue limit: "
+ outstandingPathsLimit + " exceeded, try later!");
}
}
/**
* Removes the SPS path id from the list of sps paths.
*
* @throws IOException
*/
private void clearPathIds(){
synchronized (pathsToBeTraversed) {
Iterator<Long> iterator = pathsToBeTraversed.iterator();
while (iterator.hasNext()) {
Long trackId = iterator.next();
try {
namesystem.removeXattr(trackId,
HdfsServerConstants.XATTR_SATISFY_STORAGE_POLICY);
} catch (IOException e) {View on GitHub (pinned to 2add963021)
Solutions
- Retry later after outstanding storage policy satisfier work drains, or raise dfs.storage.policy.satisfier.queue.limit if load is legitimate.
When it happens
Trigger: A satisfyStoragePolicy request arrives when the SPS outstanding work queue is at its limit.
Common situations: Batch tools flooding the NameNode with storage policy satisfaction requests.
AI-assisted analysis of apache/hadoop@2add963021 (2026-08-22).
Data as JSON: /api/errors/6d63c7db216c61d0.
Report an issue: GitHub.