On 1/3/13 5:26 PM, Yonik Seeley wrote:
I agree - it's pointless to have two replicas of the same shard on a
single node. But I'm talking about having replicationFactor as a
target, so when you start up *new* nodes they will become a replica
for any shard where the number of replicas is currentl
Yes that is exactly what I was hoping for. I can live with just adding nodes
manually for now. Would be nice if this feature was included in 4.1 though
as I will be waiting for the 4.1 release to make the jump to SolrCloud.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sol
On Thu, Jan 3, 2013 at 8:46 AM, Per Steffensen wrote:
> There are defaults for both replicationFactor and maxShardsPerNode, so non
> of them HAS to be provided - default is 1 in both cases.
>
> int repFactor = msgStrToInt(message, REPLICATION_FACTOR, 1);
> int maxShardsPerNode = msgStr
Happy to clarify.
- Mark
On Jan 3, 2013, at 10:02 AM, Per Steffensen wrote:
> Ok, sorry. Easy to misunderstand, though.
>
> On 1/3/13 3:58 PM, Mark Miller wrote:
>> MAX_INT is just a place holder for a high value given the context of this
>> guy wanting to add replicas for as many machines as
Ok, sorry. Easy to misunderstand, though.
On 1/3/13 3:58 PM, Mark Miller wrote:
MAX_INT is just a place holder for a high value given the context of this guy
wanting to add replicas for as many machines as he adds down the line. You are
taking it too literally.
- Mark
MAX_INT is just a place holder for a high value given the context of this guy
wanting to add replicas for as many machines as he adds down the line. You are
taking it too literally.
- Mark
On Jan 3, 2013, at 9:02 AM, Per Steffensen wrote:
> On 1/3/13 2:50 AM, Mark Miller wrote:
>> Unfortunate
On 1/3/13 2:50 AM, Mark Miller wrote:
Unfortunately, for 4.0, the collections API was pretty bare bones. You don't
actually get back responses currently - you just pass off the create command to
zk for the Overseer to pick up and execute.
So you actually have to check the logs of the Overseer
On 1/3/13 3:05 AM, davers wrote:
This is what I get from the leader overseer log:
2013-01-02 18:04:24,663 - INFO [ProcessThread:-1:PrepRequestProcessor@419]
- Got user-level KeeperException when processing sessionid:0x23bfe1d4c280001
type:create cxid:0x58 zxid:0xfffe txntype:unknown
There are defaults for both replicationFactor and maxShardsPerNode, so
non of them HAS to be provided - default is 1 in both cases.
int repFactor = msgStrToInt(message, REPLICATION_FACTOR, 1);
int maxShardsPerNode = msgStrToInt(message, MAX_SHARDS_PER_NODE, 1);
Remember than replica
On Wed, Jan 2, 2013 at 9:21 PM, davers wrote:
> So by providing the correct replicationFactor parameter for the number of
> servers has fixed my issue.
>
> So can you not provide a higher replicationFactor than you have live_nodes?
> What if you want to add more replicants to the collection in the
This is what I get from the leader overseer log:
2013-01-02 18:04:24,663 - INFO [ProcessThread:-1:PrepRequestProcessor@419]
- Got user-level KeeperException when processing sessionid:0x23bfe1d4c280001
type:create cxid:0x58 zxid:0xfffe txntype:unknown reqpath:n/a
Error Path:/overseer E
Unfortunately, for 4.0, the collections API was pretty bare bones. You don't
actually get back responses currently - you just pass off the create command to
zk for the Overseer to pick up and execute.
So you actually have to check the logs of the Overseer to see what the problem
may be. I'm wor
12 matches
Mail list logo
