[
https://issues.apache.org/jira/browse/HADOOP-19512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938251#comment-17938251
]
Steve Loughran commented on HADOOP-19512:
-----------------------------------------
NPE when interrupting a process trying to do an ls on the root of a nonexistent
bucket.
Looks like the fact an interrupt took place was lost and only the side effect
(null result from the list) picked up.
{code}
Starting: Examine root path
root entry S3AFileStatus{path=s3a://stevel--use1-az2--x-s3/; isDirectory=true;
modification_time=0; access_time=0; owner=stevel; group=stevel;
permission=rwxrwxrwx; isSymlink=false; hasAcl=false; isEncrypted=true;
isErasureCoded=false} isEmptyDirectory=UNKNOWN eTag=null versionId=null
list /
^C^C^C^C^C^C^C
Duration of Examine root path: 0:01:12.235
java.lang.NullPointerException
at
org.apache.hadoop.fs.s3a.S3AFileSystem.lambda$listObjects$12(S3AFileSystem.java:3025)
at
org.apache.hadoop.fs.statistics.impl.IOStatisticsBinding.invokeTrackingDuration(IOStatisticsBinding.java:547)
at
org.apache.hadoop.fs.statistics.impl.IOStatisticsBinding.lambda$trackDurationOfOperation$5(IOStatisticsBinding.java:528)
at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(Invoker.java:468)
at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(Invoker.java:431)
at
org.apache.hadoop.fs.s3a.S3AFileSystem.listObjects(S3AFileSystem.java:3016)
at
org.apache.hadoop.fs.s3a.S3AFileSystem$ListingOperationCallbacksImpl.lambda$listObjectsAsync$0(S3AFileSystem.java:2656)
at
org.apache.hadoop.fs.s3a.impl.CallableSupplier.get(CallableSupplier.java:88)
at
java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
2025-03-25 14:57:30,492 [main] INFO util.ExitUtil
(ExitUtil.java:terminate(241)) - Exiting with status -1:
java.lang.NullPointerException
{code}
> S3A: Test failures testing with unusual bucket configurations
> -------------------------------------------------------------
>
> Key: HADOOP-19512
> URL: https://issues.apache.org/jira/browse/HADOOP-19512
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Steve Loughran
> Assignee: Ahmar Suhail
> Priority: Minor
> Attachments: test-failures.txt
>
>
> 1. The logic to skip vector IO contract tests doesn't work if the analytics
> stream is set on a per-bucket basis for the test bucket
> 2. tests with SSE-C are failing. Test bucket is normally set up to use
> SSE-KMS, FWIW
> {code}
> <property>
> <name>fs.s3a.bucket.stevel-london.encryption.algorithm</name>
> <value>SSE-KMS</value>
> </property>
> {code}
> this only happens when the analytics stream is set for the test bucket
> fs.s3a.bucket.stevel-london.input.stream.type=analytics; set it globally all
> is good
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
