[jira] [Resolved] (HADOOP-14353) add an SSE-KMS scale test to see if you can overload the keystore in random IO

["Steve Loughran (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-14353.
-------------------------------------
    Resolution: Won't Fix

not seen this happening in the field, doubt you can do it for a scale test. And if you could, it'd distrupt all other users of KMS in the same account

> add an SSE-KMS scale test to see if you can overload the keystore in random IO
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-14353
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14353
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 2.9.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> Maybe add an optional IT test to aggressively seek on an SSE-KMS test file to see if it can overload the KMS infra. The [default limit|http://docs.aws.amazon.com/kms/latest/developerguide/limits.html] is 600 requests/second. This may seem a lot, but with random IO, every new HTTPS request in the chain is potentially triggering a new operation. 
> Someone should see what happens: how easy is it to create, and what is the error message.
> This may not be something we can trigger in a simple IT test, just because it's single host.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org