updates docs with delete permissions notice #2819
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
owen-d
requested review from
achatterjee-grafana and
oddlittlebird
as code owners
|
@oddlittlebird, looking at this now. |
Codecov Report
@@ Coverage Diff @@
## master #2819 +/- ##
=======================================
Coverage 61.30% 61.30%
=======================================
Files 179 179
Lines 14438 14438
=======================================
Hits 8851 8851
- Misses 4775 4779 +4
+ Partials 812 808 -4
|
owen-d
force-pushed
the
upgrade-shipper-delete-perms
branch
from
ad92e27
to
ce2f562
Compare
| @@ -113,6 +113,10 @@ We recommend running a Compactor since a single Ingester creates 96 files per da | |||
|
|
|||
| Example compactor configuration with GCS: | |||
|
|
|||
| #### Delete Permissions | |||
|
|
|||
| In the course of compacting index files, the compactor writes a new file and deletes the unoptimized ones. Therefore, ensure the compactor has appropriate permissions for deleting files, such as `s3:DeleteObject` for AWS S3. | |||
There was a problem hiding this comment.
When compacting index files, the compactor writes a new file and deletes all unoptimized files. Ensure that the compactor has appropriate permissions for deleting files, for example, s3:DeleteObject permission for AWS S3.
docs/sources/upgrading/_index.md
Outdated
| @@ -154,6 +154,10 @@ Ingesters now expose a new RPC method that queriers use when the index type is ` | |||
| Queriers generally roll out faster than ingesters, so if new queriers query older ingesters using the new RPC, the queries would fail. | |||
| To avoid any query downtime during the upgrade, rollout ingesters before queriers. | |||
|
|
|||
| #### If running the compactor, ensure it has delete permissions for the object storage. | |||
|
|
|||
| The compactor is an optional but suggested component combines and deduplicates the boltdb-shipper index files. In the course of compacting these, it writes a new file and deletes the unoptimized ones. Therefore, ensure the compactor has appropriate permissions for deleting files in this bucket, such as `s3:DeleteObject` for AWS S3. | |||
There was a problem hiding this comment.
The compactor is an optional but suggested component that combines and deduplicates the boltdb-shipper index files. When compacting index files, the compactor writes a new file and deletes all unoptimized files. Ensure that the compactor has appropriate permissions for deleting files, for example, s3:DeleteObject permission for AWS S3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.