Right, it seems like the DELETEREPLICA could handle this case, I know
there have been some hardening done there lately but don't know if
it'd cover this case. Or maybe I'm thinking of deleting collections...
On Thu, Mar 12, 2015 at 10:26 AM, Varun Thacker
varunthacker1...@gmail.com wrote:
bq.
how is copying a core dir from one node to another a normal use case ?
On Mar 12, 2015 7:22 PM, Varun Thacker varunthacker1...@gmail.com wrote:
Hi Noble,
Well I was just playing around to see if there were scenarios where
different coreNodeNames could register themselves even if they weren't
It is totally possible.
The point is , it was not a security feature and it is extremely easy to
spoof it.
The question is , was it a normal scenario or was it an effort to prove
that the system was not foolproof
--Noble
On Thu, Mar 12, 2015 at 6:23 PM, Varun Thacker varunthacker1...@gmail.com
Hi Noble,
Well I was just playing around to see if there were scenarios where
different coreNodeNames could register themselves even if they weren't
creating using the Collections API.
So I was doing it intentionally here to see what happens. But I can totally
imagine users running into the
bq.Or they're testing out restoring backups
This is in the context of ZK as truth functionality. I guess , in that case
you expect those nodes to work exactly as the other replica
On Thu, Mar 12, 2015 at 8:36 PM, Erick Erickson erickerick...@gmail.com
wrote:
bq: how is copying a core dir from
bq: how is copying a core dir from one node to another a normal use case ?
A user is trying to move a replica from one place to another. While I
agree they should use ADDREPLICA for the new one then DELTERPLICA on
the old replica..
Or they're testing out restoring backups.
I've had clients do
bq. how is copying a core dir from one node to another a normal use case ?
That was just for testing what happens.
Okay here is a real world scenario -
- I create a collection.
- The collection fails to create since it had a bad config. The empty
folders for the replicas gets left
Two scenarios I observed where we can bring up a replica even when I think
it shouldn't. legacyCloud is set to false.
- I have two nodes A and B.
- CREATE collection 'test' with 1 shard, 1 replica. It gets created on
node A.
- manually copy test_shard1_replica1 folder to node B's solr
