Sylvain,

you should not be using riak HEAD for anything that's close to your production 
environment. Development in Riak is in big flux right now, and it'll be hard 
for us to help you find the specific problem.

Could you please install Riak Search 0.14.2, best with a fresh installation, 
and try running this setup again to see if you get the same erroneous results? 
If you do, some more details on your data and the MapReduce jobs you're running 
would be great to reproduce and figure out the problem.

Mathias Meyer
Developer Advocate, Basho Technologies


On Mittwoch, 29. Juni 2011 at 00:41, Sylvain Niles wrote:

> We recently started trying to move our production environment over to
> riak and we're seeing some weird behavior that's preventing us from
> doing so:
> 
> Running: riak HEAD from github as of last Friday, riak_search turned
> on with indexing of the problem bucket "events".
> When we turn on our processes that start creating objects in the
> bucket "events", the mr_queue directory starts growing massively and
> the riak process starts spending most of its time in io_wait. With a
> total of about 7000 objects (each is a ripple document that's got
> maybe 10-20 lines of text in it) in the events bucket out bitcask dir
> was ~240MB and the mr_queue dir was 1.2GB. Something is going horribly
> wrong.. Our logs only show flow_timeouts for normal requests trying to
> do simple map/reduce lookups. Any ideas where to look?
> 
> Thanks in advance,
> Sylvain
> 
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com (mailto:riak-users@lists.basho.com)
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com



_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to