Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-09-04 Thread Effenberg, Simon
not self healing? Cheers Simon On Wed, Sep 03, 2014 at 07:55:53PM +, Effenberg, Simon wrote: >The repair worked.. >Total 2 items scanned: 12961170 >Total tree objects: 9258332 >Total objects fixed: 538423 >So it seems that it had to fix a lot. But sh

AW: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-09-03 Thread Effenberg, Simon
The repair worked.. Total 2 items scanned: 12961170 Total tree objects: 9258332 Total objects fixed: 538423 So it seems that it had to fix a lot. But shouldn't this be impossible with AAE enabled? Von Samsung Mobile gesendet Ursprüngliche Nachricht Von: "Effenb

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-09-03 Thread Effenberg, Simon
ybe it will break.. I'm looking forward. Cheers Simon On Mon, Aug 11, 2014 at 08:24:44AM +, Effenberg, Simon wrote: > Hi, > > any updates on this issue? I'm still able to search a range of 2i and > I'm getting 3 results.. 0, 557 and 13853 :(.. > > I cannot rely o

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-11 Thread Effenberg, Simon
Hi, any updates on this issue? I'm still able to search a range of 2i and I'm getting 3 results.. 0, 557 and 13853 :(.. I cannot rely on 2i right now nor can I repair it. Cheers Simon On Fri, Aug 08, 2014 at 07:12:58AM +, Effenberg, Simon wrote: > Hi Bryan, > > thanks f

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-08 Thread Effenberg, Simon
Hi Bryan, thanks for this. I tried it but to be honest I cannot see any specific stuff in the logs (on the specific host). I attached the logfile from the specific node. If you think it is also/more important to look into the logfiles on the other nodes I can send them as well.. but a quick look

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-08 Thread Effenberg, Simon
ions/#Monitoring-Repairs > > Repairs can also be monitored using the `riak-admin transfers` command. > > http://docs.basho.com/riak/1.4.9/ops/running/recovery/repairing-partitions/#Running-a-Repair > > Best Regards, > > Bryan Hunt > > Bryan Hunt - Client Services

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-08 Thread Effenberg, Simon
> Bryan Hunt > > Bryan Hunt - Client Services Engineer - Basho Technologies Limited - > Registered Office - 8 Lincoln’s Inn Fields London WC2A 3BP Reg 07970431 > > On 6 Aug 2014, at 12:53, Effenberg, Simon wrote: > > > Hi E

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-06 Thread Effenberg, Simon
>wrote: > > Hi Simon, > Sorry for the delays. I'm on vacation for a couple of days. Will pick > this up on Monday. > > Cheers > Russell > On 1 Aug 2014, at 09:56, Effenberg, Simon > wrote: > > > Hi R

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-08-01 Thread Effenberg, Simon
, Jul 30, 2014 at 09:22:56AM +, Effenberg, Simon wrote: > Great. Thanks Russell.. > > if you need me to do something.. feel free to ask. > > Cheers > Simon > > On Wed, Jul 30, 2014 at 10:19:56AM +0100, Russell Brown wrote: > > Thanks Simon, > > > >

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-30 Thread Effenberg, Simon
Great. Thanks Russell.. if you need me to do something.. feel free to ask. Cheers Simon On Wed, Jul 30, 2014 at 10:19:56AM +0100, Russell Brown wrote: > Thanks Simon, > > I’m going to spend a some time on this day. > > Cheers > > Russell > > On 30 Jul 2014, at 10:

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-30 Thread Effenberg, Simon
o eleveldb:async_get(#Ref<0.0.2698.198008>, <<>>, <<131,104,2,109,0,0,0,20,99,111,110,118,101,114,115,97,116,105,111,110,95,115,101,99,114,101,116,...>>, []) in eleveldb:get/3 line 143 in gen_server:terminate/6 line 747 2014-07-30 06:16:09.154 UTC [error] <0.

AW: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
I tried it now with one partition on 6 different machines and everywhere the same result: index_scan_timeout and the info: bad argument in call to eleveldb:async_get (2x) or async_write (4x). Von Samsung Mobile gesendet Ursprüngliche Nachricht Von: "Effenberg, Simon&q

AW: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
this is not a disk corruption issue.. Simon Von Samsung Mobile gesendet Ursprüngliche Nachricht Von: bryan hunt Datum:29.07.2014 18:21 (GMT+01:00) An: "Effenberg, Simon" Cc: riak-users@lists.basho.com Betreff: Re: repair-2i stops with "bad argument in call to eleve

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
Said to say but the issue stays the same.. even after the upgrade to 1.4.10. Any ideas what is happening here? Cheers Simon On Tue, Jul 29, 2014 at 08:46:42AM +, Effenberg, Simon wrote: > Already started to prepare everything for it.. :) > > On Tue, Jul 29, 2014 at 09:43:22AM +01

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
othing > major changed, just bug fixes, here is the release notes' link for > reference: > > https://github.com/basho/riak/blob/1.4/RELEASE-NOTES.md > > Best regards, > > Guido. > > On 29/07/14 09:35, Effenberg, Simon wrote: > >Hi, > > > >

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
One thing I realized right now.. the new node is on wheezy whereas all other 12 nodes are running squeeze.. but shouldn't be a problem, right? On Tue, Jul 29, 2014 at 08:35:15AM +0000, Effenberg, Simon wrote: > Hi, > > we have some issues with 2i queries like that: > >

repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-07-29 Thread Effenberg, Simon
Hi, we have some issues with 2i queries like that: seffenberg@kriak46-1:~$ while :; do curl -s localhost:8098/buckets/conversation/index/createdat_int/0/23182680 | ruby -rjson -e "o = JSON.parse(STDIN.read); puts o['keys'].size"; sleep 1; done 13853 13853 0 557 557 557 13853 0 ... So I trie

accessing list of keys from AAE MANIFEST file

2014-07-18 Thread Effenberg, Simon
Hi, can I somehow access/format the /var/lib/riak/anti_entropy//MANIFEST-X file easily so that I get all bucket/keys out of it? I would like to get somehow all existing keys (since the last AAE was build on this vnode) without trying to get it out of the cluster via HTTP /buckets/bucket/keys?k

big cache vs. many partitions and replicas placement

2013-01-28 Thread Effenberg, Simon
Hi, we want to save plenty of mails in riak which are in average 14k big. Our cluster will become between 10 to 20 nodes so the question is: what is better, having more partitions but each has less cache or is it the other way around so having less partitions with more cache size? Also with an