Hello Folks,
Welcome to a new year, the first Riak Recap of 2017 and a bunch of Riak
related content. Hope you all had a great couple of weeks and are ready to
ease into January with a few blog posts while steeping in some new features
and updates in the Riak ecosystem.
Are you working on somethi
Hi Alex,
You seem to be referring to bitcask metadata. That metadata is loaded into
ram on each node. As you note, the bitcask capacity planner calculates ram
required by a cluster to service a certain number of keys. I think where
you are confused is that this metadata is not synced across the cl
Hi Riak Users,
I am a little bit confused about the metadata, it is stored in memory and
synced in every node, so bascially every node share the same metadata,
right ?
But then from the official document, the formula to calcuate the RAM
requirement, the RAM requirement is for whole cluster, for ex
Ricardo
There is a comprehensive help facility which you can explore by typing:
riak-shell>help;
Your feedback on that, and if it is useful would be appreciated…
Gordon
> On 6 Jan 2017, at 16:12, Ricardo Mayerhofer wrote:
>
> That's was it. I had my config file pointing to riak@127.0.0.1
> <
That's was it. I had my config file pointing to riak@127.0.0.1 and changed
to point to the node name riak@ip-adress. It worked fine.
Thanks.
On Fri, Jan 6, 2017 at 1:01 PM, Brett Hazen wrote:
> Ricardo -
>
> What does your riak_shell.config file look like? How many nodes are in
> your cluster?
Ricardo -
What does your riak_shell.config file look like? How many nodes are in
your cluster? Guessing there might be some hostname resolution issues.
Here's the documentation on the config file:
http://docs.basho.com/riak/ts/1.5.0/using/riakshell/#configuration
Cheers,
Brett
On January 6, 2
Hi all,
I'm unable to use Riak TS 1.5 shell in Ubuntu 14.04 deploy. When I try to
star riak-shell the following messages appear:
root@ip-192-168-5-177:/var/lib/riak# riak-shell
Erlang R16B02_basho10 (erts-5.10.3) [source] [64-bit] [smp:4:4]
[async-threads:10] [hipe] [kernel-poll:false] [frame-poi