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

ThreadID persisted as -1 till OSMetricsCollector() has not run #586

Open
khushbr opened this issue Mar 26, 2021 · 0 comments
Open

ThreadID persisted as -1 till OSMetricsCollector() has not run #586

khushbr opened this issue Mar 26, 2021 · 0 comments

Comments

@khushbr
Copy link
Contributor

khushbr commented Mar 26, 2021

OSMetricsCollector#collectMetrics() is responsible for persisting Thread related info in 'jTidMap'

In case the 'jTidMap' has not been updated and threadState is null, we return -1 when getNativeThreadId() is invoked.

We need to fix this to ensure we do not emit threadID as -1

1616723515000.tmp:^threads/-1/shardbulk/29/finish
1616723515000.tmp:^threads/-1/shardbulk/30/finish
1616723515000.tmp:^threads/22259/shardbulk/44/start
1616723515000.tmp:^threads/22258/shardbulk/45/start
1616723515000.tmp:^threads/22259/shardbulk/46/start
1616723515000.tmp:^threads/22258/shardbulk/47/start
1616723515000.tmp:^threads/22259/shardbulk/46/finish
1616723515000.tmp:^threads/22258/shardbulk/47/finish
@khushbr khushbr changed the title ThreadID persisted w ThreadID persisted as -1 till OSMetricsCollector() has not run Mar 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant