basho/riak_kv — Issue #293: Keylisting continues after pipe death
Author: jonmeredith
Created: 2012-02-24 23:42:42+00:00
State: open

If MapReduce on a bucket is cancelled (timeout or dropped client connection) the listkeys feeding the objects from the bucket is not cancelled, instead it generates a large number of error messages

```
Pipe worker startup failed:fitting was gone before startup
```

Additionally, these running listkey jobs continue to tie up resources that would otherwise be capable of running other MapReduce queries. If enough listkey jobs end up in this state, subsequent MapReduce queries will be unable to complete and will timeout. In the worst case, all MapReduce queries submitted will timeout until the running listkeys eventually terminate and the cluster recovers.