-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Optimize remote store GC flow with pinned timestamps #15943
base: main
Are you sure you want to change the base?
Conversation
❌ Gradle check result for 609bd01: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
609bd01
to
3186ffa
Compare
❌ Gradle check result for 3186ffa: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
3186ffa
to
f07d64d
Compare
❌ Gradle check result for f07d64d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
f07d64d
to
c344045
Compare
❌ Gradle check result for c344045: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
c344045
to
eb12d3c
Compare
❌ Gradle check result for eb12d3c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
eb12d3c
to
6a4dab7
Compare
❌ Gradle check result for 6a4dab7: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6a4dab7
to
5ed7af5
Compare
❌ Gradle check result for 22187b9: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 36eba58: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 36eba58: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
server/src/main/java/org/opensearch/node/remotestore/RemoteStorePinnedTimestampService.java
Show resolved
Hide resolved
server/src/main/java/org/opensearch/index/translog/RemoteFsTimestampAwareTranslog.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/index/translog/RemoteFsTimestampAwareTranslog.java
Show resolved
Hide resolved
server/src/main/java/org/opensearch/index/translog/RemoteFsTimestampAwareTranslog.java
Outdated
Show resolved
Hide resolved
❌ Gradle check result for 04f2a7d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
Signed-off-by: Sachin Kale <[email protected]>
04f2a7d
to
f649a25
Compare
❌ Gradle check result for f649a25: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Failure in https://build.ci.opensearch.org/job/gradle-check/48328/ seems related to pinned timestamps. Taking a look |
❌ Gradle check result for f649a25: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Sachin Kale <[email protected]>
if (indexDeleted == false && previousMinRemoteGenReferenced == minRemoteGenReferenced) { | ||
return; | ||
} else if (previousMinRemoteGenReferenced != minRemoteGenReferenced) { | ||
previousMinRemoteGenReferenced = minRemoteGenReferenced; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we update previousMinRemoteGenReferenced
when we update minRemoteGenReferenced
, as it looks the correct place for same ?
@@ -61,6 +61,7 @@ public class RemoteFsTimestampAwareTranslog extends RemoteFsTranslog { | |||
private final Map<String, Tuple<Long, Long>> oldFormatMetadataFileGenerationMap; | |||
private final Map<String, Tuple<Long, Long>> oldFormatMetadataFilePrimaryTermMap; | |||
private final AtomicLong minPrimaryTermInRemote = new AtomicLong(Long.MAX_VALUE); | |||
private long previousMinRemoteGenReferenced = -1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we move this to RemoteFSTranslog
as it doesn't look related to Timestamp Aware Translog ?
.build(); | ||
} | ||
|
||
private void keepPinnedTimestampSchedulerUpdated() throws InterruptedException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would this fail when pinned timestamp service is running at > 10 sec periodicity ? Should the sleep account for it ?
❌ Gradle check result for c53643c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Description
minRemoteGenReferenced - indexSettings().getRemoteTranslogExtraKeep() <= maxDeletedGenerationOnRemote
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.