You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Siddhartha Singh Sandhu <sa...@gmail.com> on 2015/09/24 22:01:40 UTC
Different ports for search and upload request
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.
Re: Different ports for search and upload request
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
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
<sa...@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 <su...@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 <
>> sandhusolr@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.
>> >
>>
Re: Different ports for search and upload request
Posted by Yonik Seeley <ys...@gmail.com>.
On Thu, Sep 24, 2015 at 5:00 PM, Siddhartha Singh Sandhu
<sa...@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.
Not yet, but it's in development.
It won't require a different port either... different endpoints will
be able to have different request queues and thread pools.
-Yonik
Re: Different ports for search and upload request
Posted by Siddhartha Singh Sandhu <sa...@gmail.com>.
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 <su...@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 <
> sandhusolr@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.
> >
>
Re: Different ports for search and upload request
Posted by Susheel Kumar <su...@gmail.com>.
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 <
sandhusolr@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.
>
Re: Different ports for search and upload request
Posted by Uwe Reh <re...@hebis.uni-frankfurt.de>.
Am 25.09.2015 um 00:05 schrieb Siddhartha Singh Sandhu:
> *Never did this. *But how about this crazy idea:
> Take an Amazon EFS and share it between 2 EC2. ....
I think, you are on the right way. Imho this requirement should be
solved external.
Option 1:
Hide your Solr node behind a http-proxy which publishes the APIs/handler
on different Ports. Or publish only the requestHandler like 'select'
and 'get' and let use your updateprocess the full API.
Option 2: Use replication. Update the Master and send your Querys to the
Slave
Uwe
Re: Different ports for search and upload request
Posted by bi...@gmail.com.
Scary stuff
If you did that you better reload the core
Bill Bell
Sent from mobile
> On Sep 24, 2015, at 5:05 PM, Siddhartha Singh Sandhu <sa...@gmail.com> wrote:
>
> Thank you so much.
>
> Safe to ignore the following(not a query):-
>
> *Never did this. *But how about this crazy idea:
>
> Take an Amazon EFS and share it between 2 EC2. Use one EC2 endpt to update
> the index on EFS while the other reads from it. This way each EC2 can use
> its own compute and not share its resources among-st solr threads.
>
> Regards,
> Sid.
>
>> On Thu, Sep 24, 2015 at 5:17 PM, Shawn Heisey <ap...@elyograg.org> wrote:
>>
>>> On 9/24/2015 2:01 PM, Siddhartha Singh Sandhu wrote:
>>> 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.
>>
>> From our perspective, no.
>>
>> I have no idea whether it is possible at all ... it might be something
>> that a servlet container expert could figure out, or it might require
>> code changes to Solr itself.
>>
>> You probably need another mailing list specifically for the container.
>> For virtually all 5.x installs, the container is Jetty. In earlier
>> versions, it could be any container.
>>
>> Another possibility would be putting an intelligent proxy in front of
>> Solr and having it only accept certain handler paths on certain ports,
>> then forward them to the common port on the Solr server.
>>
>> If you did manage to do this, it would require custom client code. None
>> of the Solr clients for programming languages have a facility for
>> separate ports.
>>
>> Thanks,
>> Shawn
>>
>>
Re: Different ports for search and upload request
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
How about you do indexing on a completely different node and then swap
the index into production using Solr aggregate aliases?
https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-CreateormodifyanAliasforaCollection
The problem here is that deleting existing content is harder, so it is
more suitable for things like rolling log collections that are one-way
only.
Regards,
Alex.
----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 24 September 2015 at 18:05, Siddhartha Singh Sandhu
<sa...@gmail.com> wrote:
> Thank you so much.
>
> Safe to ignore the following(not a query):-
>
> *Never did this. *But how about this crazy idea:
>
> Take an Amazon EFS and share it between 2 EC2. Use one EC2 endpt to update
> the index on EFS while the other reads from it. This way each EC2 can use
> its own compute and not share its resources among-st solr threads.
>
> Regards,
> Sid.
>
> On Thu, Sep 24, 2015 at 5:17 PM, Shawn Heisey <ap...@elyograg.org> wrote:
>
>> On 9/24/2015 2:01 PM, Siddhartha Singh Sandhu wrote:
>> > 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.
>>
>> From our perspective, no.
>>
>> I have no idea whether it is possible at all ... it might be something
>> that a servlet container expert could figure out, or it might require
>> code changes to Solr itself.
>>
>> You probably need another mailing list specifically for the container.
>> For virtually all 5.x installs, the container is Jetty. In earlier
>> versions, it could be any container.
>>
>> Another possibility would be putting an intelligent proxy in front of
>> Solr and having it only accept certain handler paths on certain ports,
>> then forward them to the common port on the Solr server.
>>
>> If you did manage to do this, it would require custom client code. None
>> of the Solr clients for programming languages have a facility for
>> separate ports.
>>
>> Thanks,
>> Shawn
>>
>>
Re: Different ports for search and upload request
Posted by Siddhartha Singh Sandhu <sa...@gmail.com>.
Thank you so much.
Safe to ignore the following(not a query):-
*Never did this. *But how about this crazy idea:
Take an Amazon EFS and share it between 2 EC2. Use one EC2 endpt to update
the index on EFS while the other reads from it. This way each EC2 can use
its own compute and not share its resources among-st solr threads.
Regards,
Sid.
On Thu, Sep 24, 2015 at 5:17 PM, Shawn Heisey <ap...@elyograg.org> wrote:
> On 9/24/2015 2:01 PM, Siddhartha Singh Sandhu wrote:
> > 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.
>
> From our perspective, no.
>
> I have no idea whether it is possible at all ... it might be something
> that a servlet container expert could figure out, or it might require
> code changes to Solr itself.
>
> You probably need another mailing list specifically for the container.
> For virtually all 5.x installs, the container is Jetty. In earlier
> versions, it could be any container.
>
> Another possibility would be putting an intelligent proxy in front of
> Solr and having it only accept certain handler paths on certain ports,
> then forward them to the common port on the Solr server.
>
> If you did manage to do this, it would require custom client code. None
> of the Solr clients for programming languages have a facility for
> separate ports.
>
> Thanks,
> Shawn
>
>
Re: Different ports for search and upload request
Posted by Shawn Heisey <ap...@elyograg.org>.
On 9/24/2015 2:01 PM, Siddhartha Singh Sandhu wrote:
> 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.
>From our perspective, no.
I have no idea whether it is possible at all ... it might be something
that a servlet container expert could figure out, or it might require
code changes to Solr itself.
You probably need another mailing list specifically for the container.
For virtually all 5.x installs, the container is Jetty. In earlier
versions, it could be any container.
Another possibility would be putting an intelligent proxy in front of
Solr and having it only accept certain handler paths on certain ports,
then forward them to the common port on the Solr server.
If you did manage to do this, it would require custom client code. None
of the Solr clients for programming languages have a facility for
separate ports.
Thanks,
Shawn