+
Skip to content

Conversation

scality-gdoumergue
Copy link
Contributor

No description provided.

@scality-gdoumergue scality-gdoumergue requested a review from a user November 21, 2021 19:23
*Simplest way*: dump all S3 keys locally and upload them to the S3 bucket.

```
# docker run --net=host patrickdos/report-sproxyd-keys:basic --debug -s <start_date> -e <end_date> http://127.0.0.1:9000 > /var/tmp/s3_keys.txt
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice fix. I didnt catch the awscli streaming was memory constrained until we run it in a large enough environment.

### Filter the listkeys to return only the SPROXY main_chunk + sproxyd single keys

This step is the longest. For each sproxyd key listed in ``<RING_NAME>/s3-bucketd/``, spark workers
send a ``HEAD`` request to their local srebuildd. Each spark worker scans 2,7M keys a day with spark.executor.cores=3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect fluctuation of the 2.7M/day due to GHz of cores and resource contention when the customer has not made the platform idle for the work.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks for the PR!

@scality-gdoumergue scality-gdoumergue merged commit b13a891 into master Nov 29, 2021
@TrevorBenson TrevorBenson deleted the improvement/S3_FSCK_doc branch June 15, 2023 22:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载