Hi Toby, The error you are seeing is a bug which I'm working to resolve. We're currently in the process of reviewing a test to ensure against possible regressions, [1] two bug fixes, [2] [3] and a modification to the copy to clarify what "incompatible" means. [4]
For now, it's safe to assume that the 1.4.1 "incompatible" message is only going to prevent you from inspecting details such as RAM usage in the UI and shouldn't affect things such as cluster management. Sorry for the inconvenience. [1] https://github.com/basho/riak_test/pull/347 [2] https://github.com/basho/riak_control/pull/132 [3] https://github.com/basho/riak_control/pull/133 [4] https://github.com/basho/riak_control/pull/135 - Chris On Thu, Aug 8, 2013 at 12:43 AM, Toby Corkindale < toby.corkind...@strategicdata.com.au> wrote: > On 06/08/13 07:51, Paul Ingalls wrote: > >> Hope you all don't get pissed for me spamming the list….;) >> >> I upgraded my cluster to 1.4.1 in hopes the levelDB changes may help. >> The cluster is now up and running, however Riak Control is complaining: >> >> The following nodes are currently incompatible with Riak Control: >> <all my nodes> >> > > I've hit exactly the same problem, after doing a rolling upgrade to 1.4.1 > on Ubuntu. > I'm using the official Riak apt repo. > > Any hints on how to fix this? > > ta, > Toby > > > ______________________________**_________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/**mailman/listinfo/riak-users_**lists.basho.com<http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com> >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
