Hi James,
Gonna move this back to the list so that others can add to the
discussion. Definitely sounds like it may be a firewall issue. You
should get "Firewall is stopped" if it is actually stopped.
$ sudo service iptables status
Firewall is stopped.
From your output, it is still running.
Hi James,
We have a 5 node cluster running in production with no problems on
CentOS. We have each node isolated on a private lan. Our application
server has two interfaces, one to the outside world with a very
restricted firewall, and the second connected to the private lan with
the 5 nodes
I am running into a minor issue where "riak restart" does not work on a 5
nodes test cluster on CentOS 5.8.
This happens on both 1.2.0 and 1.2.1 riak. Doing 'riak stop' then 'riak
start' work. The 'restart' kill riak, but never start it back up.
And I am doing this as root, btw. So not a perm
> Hello, I am attempting to create a 4 node riak installation on 4
> separate CentOS servers. Installation of Riak went well. We have run
> simple tests like riak ping, sudo curl \-v
> http://127.0.0.1:8098/riak/test, ect, and everything seems fine with the
^^^
Did you ch
I've posted the list of buffer files [1] and segment files [2].
The current data set I have in Riak is static, so no new items are
being written. So this looks like the reason as to why compaction
isn't happening since there is no time based trigger on the merge
index. To get compaction to kick in
Jeremy,
This is how Merge Index (the index store behind Riak Search) works. It is
log-based meaning deletes are first logical before they become physical.
It does not update in-place as you stated in one of your replies. When
you performed those deletes new logs were created containing logical
D,
Go here: http://basho.com/blog/technical/2012/10/30/leveldb-in-riak-1p2/
leveldb has code that will explicitly stall write operations if it gets too far
behind in compaction. 3 to 4 seconds is nothing. 1.1 can stall into the
minutes range if you push it hard enough.
You either need to th
Seeing 99th percentile put latencies at around 30-40 ms with 99.9th
percentile jumping all the way up to 3-4s. This is riak 1.1 with the
eleveldb backend on a 9-node cluster, N = 2, W = 1. Lots of free iops, but
CPU is consistently burning 30-40% across all 8 cores.
Wondering if this could be caus
Hi there,
have you checked the value of the cookie in the vm.args? they need to be
the same on all nodes in order to the nodes to speak together.
On Tue, Oct 30, 2012 at 11:39 AM, SWEENEY, JAMES wrote:
> Hello, I am attempting to create a 4 node riak installation on 4 separate
> CentOS servers.
Hello, I am attempting to create a 4 node riak installation on 4 separate
CentOS servers. Installation of Riak went well. We have run simple tests
like riak ping, sudo curl \-v http://127.0.0.1:8098/riak/test, ect, and
everything seems fine with the riak servers, they all start up with no
Herman,
First: Note that nodejs, while asynchronous, is single threaded. Make sure
you're not overwhelming your server (100% CPU, swapping memory), or running
into internal http connection pool limits (Node's default is 5 simultaneous
connections, I bump mine to 200). If you are, look at cluste
Hi list.
I am doing a research on using riak as a solution to store comments.
Unfortunately my results were far from favorable. I will develop the
architecture I used, schemas chosen, steps taken and results; Hoping to
get feedbackboth from basho or any experienced user on what to do to
impro
Hi list.
I am doing a research on using riak as a solution to store comments.
Unfortunately my results were far from favorable. I will develop the
architecture I used, schemas chosen, steps taken and results; Hoping to
get feedbackboth from basho or any experienced user on what to do to
impro
13 matches
Mail list logo
