On Thu, Jan 26, 2012 at 9:48 PM, Ryan Fisher <rfis...@cyberpointllc.com>wrote:
> > I used the RAW tag to try and drop that log in, not sure why that didn't > come through but anyway it is the tainted ring message! Good guess! > Let me try again... > --------------- > 2012-01-26 08:49:38.120 [error] > <0.1434.0>@riak_core_ring:check_tainted:216 > Error: riak_core_ring/ring_ready called on tainted ring > 2012-01-26 08:49:38.179 [error] > <0.1453.0>@riak_core_ring:check_tainted:216 > Error: riak_core_ring/ring_ready called on tainted ring > 2012-01-26 08:49:42.796 [error] <0.117.0>@riak_core_ring:check_tainted:216 > Error: riak_core_gossip/send_ring_to :: Sending tainted ring over gossip > 2012-01-26 08:49:42.882 [error] <0.263.0>@riak_core_ring:check_tainted:216 > Error: riak_core_ring/ring_ready called on tainted ring > 2012-01-26 08:49:42.884 [error] > <0.4441.0>@riak_core_ring:check_tainted:216 > Error: riak_core_ring/ring_ready called on tainted ring > --------------- > > So is that ok to have? Or is something still not right in the ring? > This is not a good msg to have. I'm not sure if it's causing you any harm but Riak has two notions of the ring. A per-node ring which is internal to the node and a gossiped ring which all nodes share with each other. For some reason, an internal ring has leaked into the gossip. Do you notice any issues with your cluster? What does `riak-admin ring_status` and `riak-admin member_status` show? What about `riak-admin transfers`? > > So in order to re-index all the keys can I run the simply run the > search-cmd > on the bucket w/ some params? Or do I need to use one of the clients to > literately open each key, and then re-save it? > No, there is no simple command to run to reindex everything in Search. It's a matter of iterating all keys and reindexing them one-by-one.
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
