Thanks all for your commits.
I followed Shawn steps (rsync) cause everything on that volume (ZooKeeper,
Solr home and data) and everything went great.
Thanks again,
Mahmoud
On Sun, Aug 6, 2017 at 12:47 AM, Erick Erickson
wrote:
> bq: I was envisioning a scenario where the entire solr home is
bq: I was envisioning a scenario where the entire solr home is on the old
volume that's going away. If I were setting up a Solr install where the
large/fast storage was a separate filesystem, I would put the solr home
(or possibly even the entire install) under that mount point. It would
be a lot
On 8/2/2017 9:17 AM, Erick Erickson wrote:
> Not entirely sure about AWS intricacies, but getting a new replica to
> use a particular index directory in the general case is just
> specifying dataDir=some_directory on the ADDREPLICA command. The index
> just needs an HTTP connection (uses the old re
Shawn:
Not entirely sure about AWS intricacies, but getting a new replica to
use a particular index directory in the general case is just
specifying dataDir=some_directory on the ADDREPLICA command. The index
just needs an HTTP connection (uses the old replication process) so
nothing huge there. T
To add to this, not sure of solr cloud uses it, but you're going to want to
destroy the wrote.lock file as well
> On Aug 1, 2017, at 9:31 PM, Shawn Heisey wrote:
>
>> On 8/1/2017 7:09 PM, Erick Erickson wrote:
>> WARNING: what I currently understand about the limitations of AWS
>> could fill vo
On 8/1/2017 7:09 PM, Erick Erickson wrote:
> WARNING: what I currently understand about the limitations of AWS
> could fill volumes so I might be completely out to lunch.
>
> If you ADDREPLICA with the new replica's data residing on the new EBS
> volume, then wait for it to sync (which it'll do al
WARNING: what I currently understand about the limitations of AWS
could fill volumes so I might be completely out to lunch.
If you ADDREPLICA with the new replica's data residing on the new EBS
volume, then wait for it to sync (which it'll do all by itself) then
DELETEREPLICA on the original you'
On 8/1/2017 4:00 PM, Mahmoud Almokadem wrote:
> I'm using ubuntu and I'll try rsync command. Unfortunately I'm using one
> replication factor but I think the downtime will be less than five minutes
> after following your steps.
>
> But how can I start Solr backup or why should I run it although I
Thanks Shawn,
I'm using ubuntu and I'll try rsync command. Unfortunately I'm using one
replication factor but I think the downtime will be less than five minutes
after following your steps.
But how can I start Solr backup or why should I run it although I copied
the index and changed theo path?
Way back in the 1.x days, replication was done with shell scripts and rsync,
right?
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Aug 1, 2017, at 2:45 PM, Shawn Heisey wrote:
>
> On 7/31/2017 12:28 PM, Mahmoud Almokadem wrote:
>> I've a SolrClou
On 7/31/2017 12:28 PM, Mahmoud Almokadem wrote:
> I've a SolrCloud of four instances on Amazon and the EBS volumes that
> contain the data on everynode is going to be full, unfortunately Amazon
> doesn't support expanding the EBS. So, I'll attach larger EBS volumes to
> move the index to.
>
> I can
Hello,
I've a SolrCloud of four instances on Amazon and the EBS volumes that
contain the data on everynode is going to be full, unfortunately Amazon
doesn't support expanding the EBS. So, I'll attach larger EBS volumes to
move the index to.
I can stop the updates on the index, but I'm afraid to u
12 matches
Mail list logo
