Hector, thanks for getting back to me. Sorry I did not make it clear.
If I start clean, with the only difference in riak.conf being listening to
all ips (0.0.0.0 instead of 127.0.0.1) and nodename changed to the server
name or ip, it does not work. It is not a matter of old data. If I start
with t
Hector, thanks a lot! I figured it out. It does not like the hostname, but
fqdn when I retested. With fqdn it works now.
John Shen
On Fri, Jan 17, 2014 at 3:55 AM, John Shen wrote:
> Hector, thanks for getting back to me. Sorry I did not make it clear.
>
> If I start clean, with the only diffe
Hi everybody,
I have a 3 node Riak 1.1.1 cluster running on Centos 6.3. I wanted to
upgrade it to the most recent version and I was told that first I have
to upgrade to version 1.3.2 and then I can upgrade to 1.4.X version.
So I followed the instructions in Rolling upgrades guide (stop, upgra
I'm running into a yokozuna/solr issue I'm hoping someone can help me with.
I'm have a 5 node dev cluster and I'm inserting ~20 documents. When I run
searches on the data different numFounds are returned each time even though the
query is the same. I started looking at each shard individu
We’ll be talking CorrugatedIron with Jeremiah Peschka and David Rusek at 2
Eastern. Learn more about sausage-making in the client libraries.
https://plus.google.com/events/cmovsvget093sa91rjas3ac4a3s
-John
___
riak-users mailing list
riak-users@lists
By default, w=2, so only two of the default three nodes need to be successfully
written for a write to be a success. That final write could potentially take
some time to replicate, especially if you're loading a lot of data at once. You
could try setting 3=w on initial bulk upload to ensure valu
Invalid hint files will be rebuilt automatically during the Bitcask merge
process. I believe you are seeing a one-time consequence of switching to
signed hint files during the upgrade. Not to worry, they will be
regenerated through normal merge activity.
Regards,
-cv
On Jan 17, 2014 6:56 AM, "
