-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Metasync appears to hang #1387
Comments
Forgot my config:
|
And here is the stuck thread matching the stacktrace from earlier:
|
I'll also frequently see messages like I assume this is a normal condition where metadata wasn't entirely synced, so the metasync overwrites the broken data. |
The result of metasync not working is we can't use template variables in Grafana with OpenTSDB. Which is rather frustrating. |
It seems that this is caused by changing the config for metasync (or an initial run of the metasync crashing). Our solution for this problem was to completely disable compaction and metadata creation on for the TSD daemon and performing both operations through the CLI. Compaction through FSCK operations (and the tool we wrote that was just accepted in #1391 ) and metasync on a cron. |
Turns out this doesn't completely resolve the issue.
|
Ahhhh.... you're using my really ugly tree code huh? Do you really need that enabled? If not and you can disable it that would be your best situation. I'm finally uploading our ElasticSearch meta-data code as part of 3.0 so that will be the best way to sync and search for time series. |
Unless you have another solution to make Grafana display nice filtered graphs in OpenTSDB, we're stuck with this code tree. |
So...this was likely a problem with our data table. The table was so backed up with the compaction queue that it couldn't properly close regions. This made scans and other activity break in weird ways. |
Every time I attempt to manually sync metadata, the job will run for a short period, then appear to hang. I say "appear" because the log of uidmeta objects being created stops progressing, but stracing the metasync process shows activity (although it doesn't look like useful activity).
The log will look similar to:
All data from then on no longer mentions Meta threads...
Each subsequent run of metasync seems to at least be "progressing" in the sense that the UID that shows up at the end of the list is different every time.
Also, each metasync run has at least one appearance of this stacktrace (albeit with a different row mentioned):
I did collect a stack trace (
jstack -l <pid>
) if that's helpful...The text was updated successfully, but these errors were encountered: