Skip to content
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

High load concurrency issues #86

Closed
MarkusQ opened this issue Sep 9, 2011 · 6 comments
Closed

High load concurrency issues #86

MarkusQ opened this issue Sep 9, 2011 · 6 comments

Comments

@MarkusQ
Copy link
Contributor

MarkusQ commented Sep 9, 2011

There are a few remaining tree corruption race condition issues similar to those fixed in #33 which typically only manifest after sustained periods of heavy load, though having a run of bad luck or doing lots of concurrent deletion of non-trivial trees can also expose them.

I have a proposed fix which I will post as soon as it passes another round of load testing (sometime this evening).

@MarkusQ
Copy link
Contributor Author

MarkusQ commented Sep 9, 2011

See:

https://github.com/MarkusQ/awesome_nested_set/tree/ans_del_lock

For my proposed resolution.

@parndt
Copy link
Collaborator

parndt commented Oct 21, 2011

@MarkusQ what became of this? Would you like to turn it into a pull request?

@MarkusQ
Copy link
Contributor Author

MarkusQ commented Jan 13, 2012

@parndt --

Yeah, my intent is to turn it into a pull request; sorry about the delay. I'd hit an additional case that I wanted to include, got caught up in some "needs to be done yesterday" work and then hit some health issues. I haven't forgotten it though.
-- M

@parndt
Copy link
Collaborator

parndt commented Mar 19, 2012

No problem

@vishakhasawant
Copy link

Is this pull request resolved the issue?

@parndt
Copy link
Collaborator

parndt commented Aug 5, 2013

Yes, believe so, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants