Connection spooling is specified by the underlying apache commons connection manager when you create the Server.
The SUSS does socket pooling by default and is the preferred way to do concurrent indexing. There are some quirks in the Server implementation set, and SUSS avoids them. Unless you are willing to root around in the SolrJ Server code and understand exactly how it works, stay with the SUSS. On Fri, May 14, 2010 at 6:44 AM, gabriele renzi <rff....@gmail.com> wrote: > On Fri, May 14, 2010 at 3:35 PM, Anderson vasconcelos > <anderson.v...@gmail.com> wrote: >> Hi >> I wanna to know if has any connection pool client to manage the connections >> with solr. In my system, we have a lot of concurrency index request. I cant >> shared my connection, i need to create one per transaction. But if i create >> one per transaction, i think the performance will down. >> >> How you resolve this problem? > > The commonsHttpSolrServer class does connection pooling, and IIRC also > the StreamingUpdateSolrServer. > > > > -- > blog en: http://www.riffraff.info > blog it: http://riffraff.blogsome.com > -- Lance Norskog goks...@gmail.com
