[ANN] Riaknostic, your Riak Doctor
matthew at tovbin.com
Fri Mar 2 20:26:49 EST 2012
Seems like a nice tool, but it's nice to have more examples on the homepage.
Because currently I've a problem understanding if the tool is working at
all: no connected nodes info is printed.
See below. Similar happens with other diag commands, such as 'diag disk',
'diag dumps' etc.
#~/riak/bin/riak-admin diag nodes_connected --level debug
17:22:50.885 [debug] Lager installed handler lager_console_backend into
17:22:50.899 [debug] Lager installed handler error_logger_lager_h into
17:22:50.900 [info] Application lager started on node nonode at nohost
17:22:50.990 [debug] Not connected to the local Riak node, trying to
connect. alive:false connect_failed:undefined
17:22:50.991 [debug] Starting distributed Erlang.
17:22:50.994 [debug] Supervisor net_sup started erl_epmd:start_link() at
17:22:50.996 [debug] Supervisor net_sup started auth:start_link() at pid
17:22:50.999 [debug] Supervisor net_sup started
net_kernel:start_link(['riak_diag22848 at riak1',longnames]) at pid <0.44.0>
17:22:50.999 [debug] Supervisor kernel_sup started
erl_distribution:start_link(['riak_diag22848 at riak1',longnames]) at pid
17:22:50.999 [debug] Supervisor inet_gethost_native_sup started undefined
at pid <0.49.0>
17:22:50.999 [debug] Supervisor kernel_safe_sup started
inet_gethost_native:start_link() at pid <0.48.0>
17:22:51.014 [debug] Connected to local Riak node 'riak at riak1'.
17:22:51.014 [debug] Fetching local riak_kv_status.
17:22:51.014 [debug] Local RPC: riak_kv_status:statistics() 
On Fri, Dec 16, 2011 at 15:03, Sean Cribbs <sean at basho.com> wrote:
> Hey Riak users,
> You may have noticed on the Basho Blog yesterday that we made public our
> tool called "Riaknostic" (http://riaknostic.basho.com/). It's a
> collection of short diagnostics, wrapped up in an escript, that can detect
> some common problems you might have with your Riak node or cluster and
> suggest ways to fix them. It's all part of some of the usability
> improvements were baking into the next release of Riak.
> The reason I'm announcing this again on the mailing list is that we're
> looking for contributions from the community. Contribute a diagnostic, find
> and fix a bug, improve the documentation, and we'll send you some Basho
> swag to call your very own! (including but not limited to t-shirts and
> stickers) If you want to write a diagnostic but don't know what might be
> useful, here's some ideas (all of which we plan to implement, so beat us to
> * Make sure that Bitcask merging thresholds are less than or equal to the
> * Check whether swap is enabled, recommend that it be turned off
> * Compare configurations across the cluster, make sure various components
> are configured the same way
> * Check the number of open files owned by the Riak process and the
> open-file-handles limit
> Most of what you need to know is defined in the edocs:
> http://riaknostic.basho.com/edoc/index.html. Make sure to read the top of
> the "riaknostic_check" module documentation. Happy hacking!
> Sean Cribbs <sean at basho.com>
> Developer Advocate
> Basho Technologies, Inc.
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users