We have a 1.0.2 cluster with a node that's gone but still listed in
member_status (as legacy):
riak-admin member_status
Attempting to restart script through sudo -u riak
= Membership
==
Status RingPendingNode
-
At 2011-11-28T17:19+, Paul Armstrong wrote:
> We have a 1.0.2 cluster with a node that's gone but still listed in
> member_status (as legacy):
>
> riak-admin member_status
> Attempting to restart script through sudo -u riak
> =
At 2011-12-21T09:49+0800, Zheng Zhibin wrote:
> try to set permission of that folder as 777, I have also encountered
> this kind of error, it is due to user of starting riak changed.
If the user changed, change the user and/or group on the directory with chown.
Using permissions 777 is incredibly
At 2012-01-09T15:12-0800, Jeremiah Peschka wrote:
>However, make sure you do the reading on the SSDs you're going to
>purchase because not all SSDs are created equal. I had a client buy
>some smaller OCZ-Vertex 3s recently which have a wear leveling issue
>(the 120GB drives have few
At 2012-01-31T17:53-0500, Jeff Kirkell wrote:
>You also need a security rule to allow the handoff port between the
>two instances and not the outside world. I apologies for not recalling
>how to do off the top of my head but as Carl said, it is in the
>security firewall rules on the
On 16/02/2012, at 1:18, Aphyr wrote:
> On 02/16/2012 01:07 AM, Jerome Renard wrote:
>> - Will it be a problem if I decide to run Riak on ZFS + compression enabled ?
> I suspect it would work quite well. If you try it, please report back!
It does work very well. Make sure you use SSD for your ZIL
On 16/02/2012, at 1:18, Aphyr wrote:
> On 02/16/2012 01:07 AM, Jerome Renard wrote:
>> - Will it be a problem if I decide to run Riak on ZFS + compression enabled ?
>
> I suspect it would work quite well. If you try it, please report back!
It does work very well. Make sure you use SSD for your Z
