[
https://issues.apache.org/jira/browse/HADOOP-15604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-15604:
--------------------------------
Description:
When there are ~50 files being committed; each in their own thread from the
commit pool; probably the DDB repo is being overloaded just from one single
process doing task commit. We should be backing off more, especially given that
failing on a write could potentially leave the store inconsistent with the FS
(renames, etc)
It would be nice to have some tests to prove that the I/O thresholds are the
reason for unprocessed items in DynamoDB metadata store
was:
Confirm that the I/O thresholds are the reason for unprocessed items in
DynamoDB metadata store
There are ~50 files being committed; each in their own thread from the commit
pool; assume the DDB repo is being overloaded just from one single process
doing task commit. We should be backing off more, especially given that failing
on a write could potentially leave the store inconsistent with the FS (renames,
etc)
> Test if the unprocessed items in S3Guard DDB metadata store caused by I/O
> thresholds
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-15604
> URL: https://issues.apache.org/jira/browse/HADOOP-15604
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Gabor Bota
> Priority: Major
>
> When there are ~50 files being committed; each in their own thread from the
> commit pool; probably the DDB repo is being overloaded just from one single
> process doing task commit. We should be backing off more, especially given
> that failing on a write could potentially leave the store inconsistent with
> the FS (renames, etc)
> It would be nice to have some tests to prove that the I/O thresholds are the
> reason for unprocessed items in DynamoDB metadata store
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
