-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
TSM1: Panic "missed stack barrier" when profiling enabled #4328
Comments
Possibly related: #4308 (comment) |
This issue in Go 1.5 looks similar: golang/go#12238. A fix went into 1.5 but looks like they weren't able to exactly repro the issue. Maybe there is still a related bug. |
I can bump our build process to 1.5.1 in an instant. On Mon, Oct 5, 2015 at 12:28 PM, dgnorton notifications@github.com wrote:
|
Just say the word. On Mon, Oct 5, 2015 at 12:31 PM, Philip O'Toole philip@influxdb.com wrote:
|
"As you can see from the stack trace, cgo code has called into Go code, the The testing that brought this out was running with profiling enabled. On Mon, Oct 5, 2015 at 12:32 PM, Philip O'Toole philip@influxdb.com wrote:
|
@mjdesa hit this a second time, again with a binary built using 1.5. |
OK, I haven't seen anyone hit this on the go project bug tracker, so I think it's up to us to report it. @mjdesa, could you send me the logs you have so I can prepare something for the go folks? |
@mjdesa -- your test system is running with profiling enabled, correct? |
correct |
@otoolep I don't think the config option for profiling does anything.
Whole config here
|
That config option in the file is a different thing, it does not control You'll see profiling has been enabled if you check influxd in the process On Tuesday, October 20, 2015, Michael Desa notifications@github.com wrote:
|
@otoolep how do I shut profiling off? I believe that I used the ansible playbook that had profiling disabled by default. I could be mistaken though. |
false alarm. Profiling was still enabled in |
All testing so far shows that this is only an issue when profiling is enabled. |
I think this was fixed in 0.9.6 |
During 200K EPS burn-in testing of TSM1, the follow panic brought testing to a halt.
cc @jwilder @pauldix
The text was updated successfully, but these errors were encountered: