On Wed, Nov 20, 2013 at 2:38 PM, Gabriel Littman <g...@connectv.com> wrote: > > > 1) We are installed via deb package > ii riak 1.4.1-1 > Riak is a distributed data store >
There's a 1.4.2 out but your issue doesn't seem to have anything do with a specific 1.4.1 bug. > > 2) We did recently upgrade our to riak python library 2.0 but I also have > a cluster still on the 1.4 client that has similar problems. > Okay, so for now we assume the client upgrade didn't cause the issues either. > > 3) We less recently upgraded riak itself from 1.2.x to 1.4. We ended up > starting with an empty riak store in the processes. Honestly we've had > many problems with search index even under 1.2. Mostly riak would get into > a state where it would continuously crash after startup until we > deleted /var/lib/riak/merge_index on the node and then rebuilt the search > index via read/write. The particular problems I'm having now I cannot > confirm if they were happening under riak 1.2 or not. > The 1.2 issues may very well have been caused by a corruption bug that was fixed in 1.4.0 [1]. > > looks like allow_mult is false, but I just confirmed with my colleague > that *it was previously set to true* so it could be that we have a hold > over issue from that. > $ curl 'http://10.1.2.95:8098/buckets/ctv_tvdata/props' > > {"props":{"allow_mult":false,"basic_quorum":false,"big_vclock":50,"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"dw":0,"last_write_wins":false,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"n_val":3,"name":"ctv_tvdata","notfound_ok":false,"old_vclock":86400,"postcommit":[],"pr":0,"precommit":[{"fun":"precommit","mod":"riak_search_kv_hook"},{"mod":"riak_search_kv_hook","fun":"precommit"}],"pw":0,"r":1,"rw":1,"search":true,"small_vclock":50,"w":1,"young_vclock":20}} > So after setting allow_mult back to false you'd have to make sure to resolve any siblings but that should be done automatically for you now that allow_mult is false again. However, the commit hook will also crash if you have allow_mult set to true on Riak Search's special "proxy object" bucket. Looking at your original insert crash message I notice the problem is actually with the proxy objets stored in this bucket [2]. What does the following curl show you: curl 'http://host:post/buckets/_rsid_ctv_tvdata/props' I bet $5 it has allow_mult set to true. Try setting that to false and see what happens. > > Since it is now set to false now would you have a suggestion on how to > clear the problem? (Delete merge_index?) > You shouldn't have to delete merge index files unless they are corrupted. Let's see if we can fix your insert/index problem first. Then we can work on search if it is still broken. -Z [1]: https://github.com/basho/merge_index/pull/30 [2]: It's not easy to see by there is the atom 'riak_idx_doc' which indicates this is a "proxy object" created by Riak Search. If you squint hard enough you can see the analyzed fields as well. I should have looked more closely the first time. This is not an obvious error. I wouldn't expect many people to pick up on it.
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
