-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] Handle read-after-write #155330
Comments
Pinging @elastic/apm-ui (Team:APM) |
Should we also document places where we are writing data to ES ? |
@achyutjhunjhunwala Good point! I've added a list of the areas affected by this. Please add to the list if you can think of other areas affected. |
Service groups and general settings are saved objects and will be using |
Yes. Alternatively we can disable custom links on serverless. I prefer whichever is easiest (I think that is applying |
Closes: #155330 Adds `index.fast_refresh` to `.apm-custom-link` in order to ensure fast index refreshes on serverless (1 second periodic refreshes instead of 5 second which is the new default on serverless). This is pending on Elasticsearch adding support for `index.fast_refresh` (elastic/elasticsearch#96660) --------- Co-authored-by: miriam.aparicio <miriam.aparicio@gmail.com> Co-authored-by: Miriam <31922082+MiriamAparicio@users.noreply.github.com>
We leave it for now, we don’t control how many times it will be called (it could be many, thus expensive). |
Background:
Action items:
index.fast_refresh: true
to.apm-custom-link
(#159674)refresh: true
when creating API keysAreas affected by read-after-write:
Related:
The text was updated successfully, but these errors were encountered: