But they would still compete for the servlet engine's threads. Putting
them on different ports will not change anything. Now, if you wanted
to put them on different network interfaces, that could be something.
But I do not think it is possible, as the select and update are both
just configuration defined end-points (in solrconfig.xml).
Regards,
Alex.
----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 24 September 2015 at 17:00, Siddhartha Singh Sandhu
<sandhus...@gmail.com> wrote:
> Hey,
>
> Thank you for your reply.
>
> The use case would be that I can concurrently load data into my index via
> one port and then make that(*data) available(NRT search) to user through
> another high availability search endpoint without the fear of my requests
> clogging one port.
>
> Regards,
>
> Sid.
>
> On Thu, Sep 24, 2015 at 4:45 PM, Susheel Kumar <susheel2...@gmail.com>
> wrote:
>
>> I am not aware of such a feature in Solr but do want to know your use case
>> / logic behind coming up with different ports. If it is for security /
>> exposing to user, usually Solr shouldn't be exposed to user directly but
>> via application / service / api.
>>
>> Thanks,
>> Susheel
>>
>> On Thu, Sep 24, 2015 at 4:01 PM, Siddhartha Singh Sandhu <
>> sandhus...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > I wanted to know if we can configure different ports as end points for
>> > uploading and searching API. Also, if someone could point me in the right
>> > direction.
>> >
>> > Regards,
>> >
>> > Sid.
>> >
>>
