yes,i did it yesterday. the ThreadUnsafe still there. I review libmc code, update _client.pyx
def _check_thread_ident(self): pass It worked, but sometimes, I got segmentfault randomly. PAN, Myautsai <kelvin0...@gmail.com>于2015年11月18日周三 14:48写道： > Dear Alex, > > Thanks for trying libmc. Basically one libmc client can only exists in > just one thread (instead of using it across multi threads). If you want to > use libmc in a multi-thread environment, the simplest way is to create > libmc client in each thread, otherwise you may need to on write connection > pool wrapper by yourself. > > Please refer https://github.com/douban/libmc#is-libmc-thread-safe- first > and open a new issue on GitHub https://github.com/douban/libmc/issues/new with > the code snippet to reproduce for further discussion. > > Best Regards. > > -- > Douban Inc. | PAN, Myautsai > Sent with Sparrow <http://www.sparrowmailapp.com/?sig> > > On Tuesday, November 17, 2015 at 20:29, Zhang Alex wrote: > > Hi, It's awsome > I want get mc from connection pool. I got error "ThreadUnsafe: mc client > created in (28740, 'Thread-4')". > > 在 2015年4月4日星期六 UTC+8下午2:09:41，PAN Myautsai写道： > > Dear all, > > A few days ago, we just released a new memcached client for C++/Python: > libmc. > > libmc is a memcached client library for Python without any other > dependencies in runtime. It's mainly written in C++ and Cython. libmc can > be considered as a drop in replacement for *libmemcached and * > *python-libmemcached* <https://github.com/douban/python-libmemcached>. > > libmc is developing and maintaining by Douban Inc. Currently, It is > working in production environment, powering all web traffics in douban.com. > Realtime benchmark is available on travis: > https://travis-ci.org/douban/libmc/builds/57124335#L1611 . > > The source code has been open sourced on GitHub: > https://github.com/douban/libmc . > > Best Regards. > > Douban Inc. | PAN, Myautsai > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/memcached/HGkAp5KxPCo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/memcached/HGkAp5KxPCo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
