[
https://issues.apache.org/jira/browse/HADOOP-14305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971469#comment-15971469
]
Steve Loughran commented on HADOOP-14305:
-----------------------------------------
Not > 1 thread, >1 client process. Our tests run in different VMs. This is
making me wonder if, once one client with encryption turned on creates some
mock empty directories or something, does that stop clients with other
encryption policies *including the no-encryption policy* from working with the
directory structure. I'm not worry about whether process A can read data
created by process B if they have different keys, but HEAD requests are things
I'd expect to work,
If that's not the case, then this is a serious issue which is either going to
need to be fixed (somehow), or used to constrain the usage situations of the
encryption mech, i.e. one policy/key per bucket.
We don't see this problem with AWS-managed SSE, presumably because it sorts out
keys when needed.
> S3A SSE tests won't run in parallel: Bad request in directory GetFileStatus
> ---------------------------------------------------------------------------
>
> Key: HADOOP-14305
> URL: https://issues.apache.org/jira/browse/HADOOP-14305
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-14305-001.patch
>
>
> The S3a encryption tests all run in parallel (they were interfering with each
> other, apparently). This adds ~1 min to the test runs.
> They should run in serial. That they fail when this is attempted due to Bad
> Auth problems must be considered a serious problem, as is indicates issues
> related to working with SSE encryption from hadoop
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
