Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs for Standalone GC #8427

Merged
merged 7 commits into from
Dec 17, 2024
Merged

Improve docs for Standalone GC #8427

merged 7 commits into from
Dec 17, 2024

Conversation

talSofer
Copy link
Contributor

@talSofer talSofer added docs Improvements or additions to documentation exclude-changelog PR description should not be included in next release changelog minor-change Used for PRs that don't require issue attached labels Dec 16, 2024
Copy link

github-actions bot commented Dec 16, 2024

♻️ PR Preview c3d15d4 has been successfully destroyed since this PR has been closed.

🤖 By surge-preview

Copy link

E2E Test Results - DynamoDB Local - Local Block Adapter

13 passed

Copy link

E2E Test Results - Quickstart

11 passed

Copy link
Collaborator

@ozkatz ozkatz left a comment

Choose a reason for hiding this comment

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

Thank you!

Copy link
Contributor

@yonipeleg33 yonipeleg33 left a comment

Choose a reason for hiding this comment

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

Thanks, looking good overall!
Had some comments

docs/howto/garbage-collection/standalone-gc.md Outdated Show resolved Hide resolved
docs/howto/garbage-collection/standalone-gc.md Outdated Show resolved Hide resolved
docs/howto/garbage-collection/standalone-gc.md Outdated Show resolved Hide resolved
@talSofer talSofer requested a review from yonipeleg33 December 17, 2024 09:47
Copy link
Contributor

@yonipeleg33 yonipeleg33 left a comment

Choose a reason for hiding this comment

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

Almost LGTM!
Blocking mainly for the broken link.


Standalone GC is a limited version of the Spark-backed GC that runs without any external dependencies, as a standalone docker image.
Standalone GC is a simplified version of the Spark-backed GC that runs without any external dependencies, delivered as a standalone
docker image. It supports S3 and [self-managed S3 compatible storages](#s3-compatible-clients) such as MinIO.
Copy link
Contributor

Choose a reason for hiding this comment

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

The link is invalid - I think you meant to link the "using-s3-compatible-clients" section?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

More about that in the [Get the List of Objects Marked for Deletion](./standalone-gc.md#get-the-list-of-objects-marked-for-deletion) section.

### Lab tests
1. **No horizontal scalability**: Only a single instance of `lakefs-sgc` can operate on a given repository at a time.
Copy link
Contributor

@yonipeleg33 yonipeleg33 Dec 17, 2024

Choose a reason for hiding this comment

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

Now that I think about it - is it correct to say that another limitation compared to the spark-backed GC is that this one only supports AWS (and s3 compatible) storage? the spark-backed one supports any blockstore, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added a bullet

Comment on lines 135 to 137
Standalone GC supports S3 and S3-compatible storage backends and relies on AWS credentials for authentication. To set up
credentials, follow AWS guidelines, such as those outlined in [this guide](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-configure.html).
For details on how to pass credentials to `lakefs-sgc`, refer to the instructions in [How to Run Standalone GC](#how-to-run-standalone-gc).
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider being a bit more direct about configuring the docker container:

Suggested change
Standalone GC supports S3 and S3-compatible storage backends and relies on AWS credentials for authentication. To set up
credentials, follow AWS guidelines, such as those outlined in [this guide](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-configure.html).
For details on how to pass credentials to `lakefs-sgc`, refer to the instructions in [How to Run Standalone GC](#how-to-run-standalone-gc).
Standalone GC supports S3 and S3-compatible storage backends and relies on AWS credentials for authentication. To set up
credentials on the `lakefs-sgc` docker container, follow AWS guidelines, such as those outlined in [this guide](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-configure.html).
For details on how to pass credentials to `lakefs-sgc`, refer to the instructions in [How to Run Standalone GC](#how-to-run-standalone-gc).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@talSofer talSofer requested a review from yonipeleg33 December 17, 2024 12:43
Copy link
Contributor

@yonipeleg33 yonipeleg33 left a comment

Choose a reason for hiding this comment

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

Thank you very much, LGTM!

@talSofer talSofer merged commit fb5648f into master Dec 17, 2024
39 checks passed
@talSofer talSofer deleted the docs/sgc-improvements branch December 17, 2024 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation exclude-changelog PR description should not be included in next release changelog minor-change Used for PRs that don't require issue attached
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants