Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Run RemoteReporter's flush timer in daemon thread. #124

Merged
merged 2 commits into from
Feb 1, 2017

Conversation

aristidisp
Copy link
Contributor

This prevents the flush timer's thread from keeping a process alive after main() has returned.

This prevents the flush timer's thread from keeping a process alive after main() has returned.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@@ -59,12 +61,14 @@ public RemoteReporter(final Sender sender, int flushInterval, int maxQueueSize,
commandQueue = new ArrayBlockingQueue<>(maxQueueSize);

// start a thread to append spans
long serialNumber = nextSerialNumber.getAndIncrement();
Copy link
Member

Choose a reason for hiding this comment

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

I am not sure why we need this. In a real application there would be only one thread with each name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Seemed like a good idea to ensure thread name uniqueness, but you're right, it's not necessary. This is my first pull request on GitHub: do I make the change in my repo then push, or do you do it here directly?

Copy link
Member

Choose a reason for hiding this comment

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

yes, you make the change in the same branch as you did and just push that branch, the PR should be automatically updated.

@yurishkuro yurishkuro merged commit dfb89a9 into jaegertracing:master Feb 1, 2017
@aristidisp aristidisp deleted the flush_timer_daemon branch February 1, 2017 18:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants