Comment #2 on issue 331 by [email protected]: assoc_maintenance_thread
unlocks mutex without locking first
http://code.google.com/p/memcached/issues/detail?id=331
It caused a bug, but not on Linux (where the spurious
pthread_mutex_unlock() seems to be silently ignored) but rather a new
operating system, whose pthread_mutex_unlock() croaks if called on an
already-unlocked mutex.
What if we add a call to pause in the *beginning* of the
assoc_maintenance_thread() function (not right before the resume) -
wouldn't this be the right fix? Then, any time the
assoc_maintenance_thread() function is working, the rebalancer is paused -
except during the wait where the rebalancer is explicitly resumed.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
