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 h
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 w
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
> wrote:
>
> Thank you so much.
>
> Safe to ignore the following(not a query):-
>
> *Never did this. *But how about this crazy idea:
>
> Take an Amazo
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 r
On Thu, Sep 24, 2015 at 5:00 PM, Siddhartha Singh Sandhu
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
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 mig
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 d
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, S
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
