Re: ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

2016-03-06 Thread Sargun Dhillon
They're effectively equal Sent from my iPhone On Mar 6, 2016, at 17:32, Robert Latko wrote: Hi all, Found the problem/solution. With the first cluster, I set it up with a ring size of 64. Prior to loading data. I stopped the node(s), changed the ring size to 256, then restarted. Therefore, i

Re: ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

2016-03-06 Thread Robert Latko
Hi all, Found the problem/solution. With the first cluster, I set it up with a ring size of 64. Prior to loading data. I stopped the node(s), changed the ring size to 256, then restarted. Therefore, if I want to add a new node, I FIRST must start the node with a ring size of 64, then stop i

ring_creation_size & ring_partition_number error joining 2.1.3 node to 2.1.1 cluster

2016-03-06 Thread Robert Latko
Hi All, I've got a cluster in 2.1.1 and was wanting to join a 2.1.3 node to it I am getting the following error: # ./bin/riak-admin cluster join a-backend@10.0.0.199 Failed: a-backend@10.0.0.199 has a different ring_creation_size So... for the new 2.1.3 # ./bin/riak-admin status | grep ring ri

Re: Continuous HTTP POSTs to Riak

2016-03-06 Thread Qiang Cao
Thanks for sending this explanation, Vitaly! This helps for sure. Thank you all, guys! -Qiang On Sun, Mar 6, 2016 at 3:24 AM, Vitaly E <13vitam...@gmail.com> wrote: > Hi Qiang, > > You mentioned that my suggestion to synchronize the clocks of your Riak > nodes had solved the problem. Let me expl

Re: Yokozuna inconsistent search results

2016-03-06 Thread Oleksiy Krivoshey
I've found the keys in riak console.log within AAE errors. Thanks! On 5 March 2016 at 22:53, Oleksiy Krivoshey wrote: > 2016-03-01 09:00:17,640 [ERROR] > @SolrException.java:109 > org.apache.solr.common.SolrException: Invalid Date String:'Invalid date' > > However I'm struggling to find the obj

Re: Continuous HTTP POSTs to Riak

2016-03-06 Thread Vitaly E
Hi Qiang, You mentioned that my suggestion to synchronize the clocks of your Riak nodes had solved the problem. Let me explain why -- it may clear things up for you. Riak uses vector clocks / version vectors to keep track