We have a 5 node cluster running 2.0.0beta1. Our 2i indexes seem to return
different responses depending on which node you hit, so I'm trying to
rebuild them.
I'm trying to run riak-admin repair-2i and it fails with Error:
index_scan_timeout
An example:
# riak-admin repair-2i 0
Will repair 2i on these partitions:
0
Watch the logs for 2i repair progress reports
console.log:
2015-02-26 14:55:32.099 [info] <0.7489.15>@riak_kv_2i_aae:init:139 Starting
2i repair at speed 100 for partitions [0]
2015-02-26 14:55:32.100 [info]
<0.7491.15>@riak_kv_2i_aae:repair_partition:259 Acquired lock on partition 0
2015-02-26 14:55:32.100 [info]
<0.7491.15>@riak_kv_2i_aae:repair_partition:261 Repairing indexes in
partition 0
2015-02-26 14:55:32.100 [info]
<0.7491.15>@riak_kv_2i_aae:create_index_data_db:326 Creating temporary
database of 2i data in /data/riak/anti_entropy/2i/tmp_db
2015-02-26 14:55:32.114 [info]
<0.7491.15>@riak_kv_2i_aae:create_index_data_db:363 Grabbing all index data
for partition 0
2015-02-26 15:00:32.118 [error] <0.2701.0> gen_server <0.2701.0> terminated
with reason: bad argument in call to
eleveldb:async_get(#Ref<0.0.77.168699>, <<>>,
<<131,104,2,109,0,0,0,12,80,68,45,101,118,101,110,116,98,97,115,101,109,0,0,0,22,48,48,48,48,48,...>>,
[]) in eleveldb:get/3 line 150
2015-02-26 15:00:32.119 [error] <0.2701.0> CRASH REPORT Process <0.2701.0>
with 0 neighbours exited with reason: bad argument in call to
eleveldb:async_get(#Ref<0.0.77.168699>, <<>>,
<<131,104,2,109,0,0,0,12,80,68,45,101,118,101,110,116,98,97,115,101,109,0,0,0,22,48,48,48,48,48,...>>,
[]) in eleveldb:get/3 line 150 in gen_server:terminate/6 line 744
2015-02-26 15:00:32.121 [error] <0.2696.0> Supervisor
{<0.2696.0>,poolboy_sup} had child riak_core_vnode_worker started with
{riak_core_vnode_worker,start_link,undefined} at <0.2701.0> exit with
reason bad argument in call to eleveldb:async_get(#Ref<0.0.77.168699>,
<<>>,
<<131,104,2,109,0,0,0,12,80,68,45,101,118,101,110,116,98,97,115,101,109,0,0,0,22,48,48,48,48,48,...>>,
[]) in eleveldb:get/3 line 150 in context child_terminated
2015-02-26 15:00:32.237 [info]
<0.7489.15>@riak_kv_2i_aae:next_partition:160 Finished 2i repair:
Total partitions: 1
Finished partitions: 1
Speed: 100
Total 2i items scanned: 0
Total tree objects: 0
Total objects fixed: 0
With errors:
Partition: 0
Error: index_scan_timeout
I found a previous post about this:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2014-August/015655.html
I tried to set the aae_2i_batch_size, 10 in the advanced.conf, the server
started, but I'm not sure how to confirm this setting took.
If it did take It didn't seem to help.
Any other suggestions?
Let me know if you need more details.
Thanks,
*Jason Greathouse*
Sr. Systems Engineer
*[image: LeanKitlogo] <https://leankit.com/>*
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
