Skip to content

[CCR] Added auto_follow_exception.timestamp field to auto follow stats#36947

Merged
martijnvg merged 3 commits intoelastic:masterfrom
martijnvg:ccr_auto_follow_stats_recent_follow_errors_timestamp
Dec 24, 2018
Merged

[CCR] Added auto_follow_exception.timestamp field to auto follow stats#36947
martijnvg merged 3 commits intoelastic:masterfrom
martijnvg:ccr_auto_follow_stats_recent_follow_errors_timestamp

Conversation

@martijnvg
Copy link
Copy Markdown
Member

Currently auto follow stats users are unable to see whether an auto follow
error was recent or old. The new timestamp field will help user distinguish
between old and new errors.

…ats.

Currently auto follow stats users are unable to see whether an auto follow
error was recent or old. The new timestamp field will help user distinguish
between old and new errors.
@martijnvg martijnvg added >enhancement v7.0.0 :Distributed/CCR Issues around the Cross Cluster State Replication features v6.7.0 labels Dec 21, 2018
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-distributed

@martijnvg martijnvg changed the title [CCR] Added auto_follow_exception.timestamp field to auto follow stats [CCR] Added auto_follow_exception.timestamp field to auto follow stats Dec 21, 2018
Copy link
Copy Markdown
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want a real clock instead of the relative clock, so that the timestamps are meaningful.

}

synchronized void updateStats(List<AutoFollowResult> results) {
long newStatsReceivedTimeStamp = relativeMillisTimeProvider.getAsLong();
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want the absolute time provider here!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops, you're absolutely right. I guess I made it this change too quickly...

@martijnvg
Copy link
Copy Markdown
Member Author

@jasontedor I've addressed the sloppiness in this PR.

Copy link
Copy Markdown
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@martijnvg martijnvg merged commit 44fe265 into elastic:master Dec 24, 2018
martijnvg added a commit that referenced this pull request Dec 24, 2018
#36947)

Currently auto follow stats users are unable to see whether an auto follow
error was recent or old. The new timestamp field will help user distinguish
between old and new errors.
@jimczi jimczi added v7.0.0-beta1 and removed v7.0.0 labels Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed/CCR Issues around the Cross Cluster State Replication features >enhancement v6.7.0 v7.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants