-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
stability: index out of range on (*TxnMeta).MarshalTo #5998
Comments
Without having looked closely, that looks like sharing transaction protos. On Tue, Apr 12, 2016 at 6:20 AM marc notifications@github.com wrote:
-- Tobias |
ooh, even better:
This one is on |
Thanks! I don't think the data will be useful for this one. Feel free to On Tue, Apr 12, 2016 at 9:11 AM marc notifications@github.com wrote:
-- Tobias |
I'm running into concurrent proto accesses quite a bit (eg: #6020, #6052). I'll see if I can get beefy-enough machines to run with race-enabled builds. I tried before, but it gobbles up memory way too quickly to catch anything. It may even be worth doing this in the long term. I think 3 nodes with load for a start would be good. |
Yeah, I think that's a good idea in general. I'm also going to get started on reducing these races. |
This could also have been fixed by #6111, but I'm a little less certain here - now that you're running race-enabled builds, we should close the race-disabled race issues since they're essentially going to be very hard to reason about. |
probably fixed by #6111, will re-open or file new issue if it reoccurs. |
I don't see how this one could have been fixed by #6111: that fix related to errors returned by |
yeah, I was a bit aggressive in closing race-related things. The plan is to re-open what we find on the rho cluster. Actual data race dumps make it much simpler to debug too. |
build sha: c382dd7
brand new beta cluster with photos and block-writer (concurrency=5).
Ran for less than an hour before seeing logs of errors along the lines of:
I stopped block_writers to start poking around, when node 1 (
ec2-54-209-69-52.compute-1.amazonaws.com
) crashed with:Node log:
node1.log.parse.txt
The text was updated successfully, but these errors were encountered: