Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: CloudSolrServer vs ConcurrentUpdateSolrServer for indexing
From: J Mohamed Zahoor <zahoor@indix.com>
In-Reply-To: <15E4174B-414F-4603-AE72-6B99F46460EA@indix.com>
Date: Tue, 16 Apr 2013 22:13:28 +0530
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1925D0E-9294-4E3D-B0D9-F410CD645A5C@indix.com>
References: <B09E70AE-24FC-480C-B7C3-70F5D8B0D1C1@indix.com>
 <BBB64C4A-D6AA-4B04-BA14-668757A4C0A7@gmail.com>
 <15E4174B-414F-4603-AE72-6B99F46460EA@indix.com>
To: solr-user@lucene.apache.org

It sure increased the performance .
Thanks for the input.

./zahoor

On 14-Apr-2013, at 10:13 PM, J Mohamed Zahoor <zahoor@indix.com> wrote:

> Thanks..
> Will try multithreading with CloudSolrServer.
>=20
> ./zahoor
>=20
> On 13-Apr-2013, at 9:11 PM, Mark Miller <markrmiller@gmail.com> wrote:
>=20
>>=20
>> On Apr 13, 2013, at 11:07 AM, J Mohamed Zahoor <zahoor@indix.com> =
wrote:
>>=20
>>> Hi
>>>=20
>>> This question has come up many times in the list with lots of =
variations (which confuses me a lot).
>>>=20
>>> Iam using Solr 4.1. one collection , 6 shards, 6 machines.
>>> I am using CloudSolrServer  inside each mapper to index my =
documents=85. While it is working fine , iam trying to improve the =
indexing performance.
>>>=20
>>>=20
>>> Question is: =20
>>>=20
>>> 1) is CloudSolrServer multiThreaded?
>>=20
>> No. The proper fast way to use it is to start many threads that all =
add docs to the same CloudSolrServer instance. In other words, =
currently, you must do the multi threading yourself. CloudSolrServer is =
"thread safe".
>>=20
>>>=20
>>> 2) Will using ConcurrentUpdateSolr server increase indexing =
performance?
>>=20
>> Yes, but at the cost of having to specify a server to talk to - if it =
goes down, so does your indexing. It's also not very great at reporting =
errors. Finally, using multiple threads and CloudSolrServer, you can =
approach the performance of ConcurrentUpdateSolr server.
>>=20
>> - Mark
>>=20
>>>=20
>>> ./Zahoor
>>=20
>=20