Fix the earliest last modified age of translog issue.#64753
Fix the earliest last modified age of translog issue.#64753dnhatn merged 6 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/es-distributed (Team:Distributed) |
dnhatn
left a comment
There was a problem hiding this comment.
Thanks @howardhuanghua. I prefer fixing the issue when adding a translog stats instead.
|
Thanks @dnhatn , you mean add a extra check to |
|
Yes, but 0L is more appropriate than Long.MAX_VALUE for the timestamp of an empty translog. |
|
Hi @dnhatn, I have updated the change, please help to review again, thanks. |
dnhatn
left a comment
There was a problem hiding this comment.
Thanks @howardhuanghua. I left a small comment.
| this.uncommittedSizeInBytes += translogStats.uncommittedSizeInBytes; | ||
| this.earliestLastModifiedAge = | ||
| Math.min(this.earliestLastModifiedAge, translogStats.earliestLastModifiedAge); | ||
| if (this.earliestLastModifiedAge < 1) { |
There was a problem hiding this comment.
Let's use this.earliestLastModifiedAge == 0.
There was a problem hiding this comment.
Updated, thanks.
|
@elasticmachine ok to test |
Currently translog's `earliest_last_modified_age` field is always 0 in `_nodes/stats` response.
Currently translog's `earliest_last_modified_age` field is always 0 in `_nodes/stats` response.
Currently translog's `earliest_last_modified_age` field is always 0 in `_nodes/stats` response.
Currently translog's
earliest_last_modified_agefield is always 0 in_nodes/statsresponse.