Elastic ip addresses?
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
> Am 25.02.2019 um 08:22 schrieb Addison, Alex (LNG-LON)
> :
>
> Hi all, we're looking at how to run Solr & Zookeeper in production. We're
> running everything in AWS, and for resiliency we'r
And or aws route 53
> Am 25.02.2019 um 08:46 schrieb Jörn Franke :
>
> Elastic ip addresses?
> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
>
>> Am 25.02.2019 um 08:22 schrieb Addison, Alex (LNG-LON)
>> :
>>
>> Hi all, we're looking at how to run Solr & Zoo
I don’t think an autoscaling group is the right way to bring back a Zookeeper
node. ZK nodes have identity. This is key to the operation of ZK. You cannot
just swap in a new random node. It doesn’t “scale up”.
Size the ZK cluster for the number of anticipated failures. I like a five node
cluste
Hi All,
I'm a newer about Solr. I am trying to use Solr 7.6 in japanese environment.
I noticed that [Kuromoji] is used in Solr by default.
Now, if I want to use [Mecab] to analyze words, I have no ideas about this at
all.
Of course, I googled, I just found very very old information and all about
Hi all, we're looking at how to run Solr & Zookeeper in production. We're
running everything in AWS, and for resiliency we're using Exhibitor with
Zookeeper and keeping Zookeeper in an auto-scaling group just to re-create
instances that are terminated for whatever reason.
Unfortunately it's not
Hi,
Anyone else has other suggestions or have faced the same problem?
Regards,
Edwin
On Wed, 20 Feb 2019 at 16:58, Zheng Lin Edwin Yeo
wrote:
> Hi Paul,
>
> If I tried to execute the second step first, then I will only get a single
> for those with 2 .
> For those that we originally get 4 , t
