-
Notifications
You must be signed in to change notification settings - Fork 207
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
Create and delete point in time for processing an index #2839
Create and delete point in time for processing an index #2839
Conversation
Please comment out the failing tests, if they are failing because of sigv4 |
Signed-off-by: Taylor Gray <[email protected]>
b77da85
to
4aa79ca
Compare
A couple were failing from an unnecessary mock. I fixed those. No unit tests are failing from sigv4 issues. Manual testing was done to see the delete pit call fail with sigv4 |
|
||
public class OpenSearchAccessor implements SearchAccessor, ClusterClientFactory { | ||
|
||
private static final Logger LOG = LoggerFactory.getLogger(OpenSearchAccessor.class); | ||
|
||
static final String PIT_RESOURCE_LIMIT_ERROR_TYPE = "rejected_execution_exception"; |
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.
This error type seems more generic than the PIT logic. Are there other cases where we can get a RejectedExecutionException unrelated to PIT?
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.
Probably but what is the alternative? Check the message contains something unique to the PIT message? Even for other exception we would log it and then give up the index and wait to start processing again, which is ok
…roject#2839) Signed-off-by: Taylor Gray <[email protected]> Signed-off-by: Marcos_Gonzalez_Mayedo <[email protected]>
Description
Create and delete point in time for an index to process it
enable_sigv4
is set to true. I have not been able to debug, but it works properly whenenable_sigv4
is false. I will create a separate issue to work on this bug in the future.Issues Resolved
related to #1985
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.