Keylisting continues after pipe death

[basho]

Keylisting continues after pipe death

[pavlobaron]

hi,

how can I prevent the local Erlang client from dropping the connection on a long running pipe? In riak_mongo, when running the count test which leads to mapred of all keys in a bucket, I get just as many keys counted as came through before the pipe has died. I absolutely well understand that it's stupid to ask for all keys in the bucket for many reasons, but that's how the corresponding MongoDB js test is counting the items:

db.things.find().toArray().length

Which leades to count(*) in the KV store when getting translated. I can't work with the count approximation since the corresponding test simply compares in and out count in an assertion. So i need to mapred and thus count all the keys in a potential long-runner.

Any idea how to increase the local client timeout?

Anyway,

Thanks!
cheers pb

[seancribbs]

This also happens with regular key-listing where the client disconnects before the key-listing finishes.

[beerriot]

This should be fixed as of #408. A few of those messages may still print, as in-flight messages are consumed from mailboxes, but it should be a small fixed number (#vnodes or #vnodes/N-value), instead of the endless run.