Skip to content
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

Adding kpl metric to track the time for oldest future in processing #324

Merged
merged 1 commit into from
Dec 14, 2020

Conversation

yatins47
Copy link
Contributor

@yatins47 yatins47 commented Nov 24, 2020

Issue #, if available:

Description of changes: Adding metrics for future time.

Old PR Link : #319

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@yatins47 yatins47 changed the title Adding metrics for future time. Adding kpl metric to track the time for oldest future in processing. Also adding fix for clearing futures in case of unknown messages from native layer. Nov 24, 2020
Copy link
Contributor

@ashwing ashwing left a comment

Choose a reason for hiding this comment

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

Leaving comments. Can you also link the previous PR that had some review comments as well?

@@ -18,6 +18,8 @@

int getOutstandingRecordsCount();

long getOldestRecordTimeInSeconds();
Copy link
Contributor

Choose a reason for hiding this comment

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

We discussed that this should be default right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added. Will need to update the java version to be 1.8 as well from 1.7 currently

@ashwing ashwing changed the title Adding kpl metric to track the time for oldest future in processing. Also adding fix for clearing futures in case of unknown messages from native layer. Adding kpl metric to track the time for oldest future in processing Dec 14, 2020
Copy link
Contributor

@ashwing ashwing left a comment

Choose a reason for hiding this comment

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

lgtm. Fixed the title.

@@ -200,6 +203,10 @@ public long getAggregationMaxSize() {
return aggregationMaxSize;
}

public long getFutureTimeoutInSeconds() {
Copy link
Contributor

Choose a reason for hiding this comment

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

Few customers are sensitive to even 500ms. Can we change this to ms?

@@ -147,6 +151,7 @@ public void run() {
log.info(String.format(
"Put %d of %d so far (%.2f %%), %d have completed (%.2f %%)",
put, total, putPercent, done, donePercent));
log.info("Oldest future as of now is " + producer.getOldestRecordTimeInSeconds());
Copy link
Contributor

Choose a reason for hiding this comment

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

nit : oldest Record. You can fix in next round

@yatins47
Copy link
Contributor Author

Merging in changes after Ashwin's approval

@yatins47 yatins47 merged commit 09d48dd into awslabs:master Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants