I could do that - I'll have to see if I can trim it down to a reasonable size without all the unrelated code in it.
Is it obvious on GitHub where people can submit error samples? I haven't done that before. - Tim On Friday, January 23, 2015 at 1:27:05 AM UTC-8, David Pilato wrote: > > Yes I am. > > Client is thread safe. Any chance you could share on github a small > project which reproduce this error? > > David > > Le 23 janv. 2015 à 01:18, TimOnGmail <timb...@gmail.com <javascript:>> a > écrit : > > I changed the code to use a Singleton. Even so, when I made the indexing > and searching happen in 2 different threads (without waiting for responses > - just ignoring the returned future), it failed similarly - even if I > waited for awhile before issuing the search. > > If I did the same thing, but didn't do it in 2 threads, it succeeded. > > So I am wondering if there is some issue when accessing the Singleton > client in different threads, some non-threadsafe issue at work. > > David, are you a dev on the Elasticsearch team? If not, I hope one of > them chimes in here. > > - Tim > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c405d2af-cc0f-4803-8197-7791b0133845%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
