Greetings!
First and foremost, search and secondary indexes (2i) are not the same thing.
You need to enable 2i and use the ELevelDB backend as described here:
http://wiki.basho.com/Secondary-Indexes---Configuration-and-Examples.html
Secondly, the default Converter (JSONConverter) in the Java cli
The travis CI build fails occasionally with a map/reduce timeout issue
that isn't due to the client (directly) that still needs addressing.
It's nothing to worry about.
On Tue, Oct 2, 2012 at 9:06 AM, Guido Medina wrote:
> Hi,
>
> Is there any particular issue with the Java Riak HttpClient when
On Wed, Sep 26, 2012 at 4:38 PM, Chris Hicks
wrote:
> However, sending
> the command off to, say, 3 nodes to process means that each of my nodes will
> then ping Riak (if I need 2 responses per query suddenly that means I hit
> Riak nodes a total of 6 times), process, and then all try to save the
On Tue, Oct 2, 2012 at 8:51 AM, Shane McEwan wrote:
> Thanks John and Kelly. It's nice to know we're not the only ones. :-)
>
> As I said, we'll be upgrading to 1.2 in the coming weeks so it's good to
> know that the memory issues might go away after that. It's not a showstopper
> for us, more of
Thanks John and Kelly. It's nice to know we're not the only ones. :-)
As I said, we'll be upgrading to 1.2 in the coming weeks so it's good to
know that the memory issues might go away after that. It's not a
showstopper for us, more of a curiosity and concern it might develop
into something wo
Forgot to paste this in the last email. We ARE seeing the long_gc
messages (but no large_heap):
erlang.log.3:10:43:21.406 [info] monitor long_gc <0.29654.5763>
[{initial_call,{riak_pipe_fitting,init,1}},{almost_current_function,{gen_fsm,loop,7}},{message_queue_len,0}]
[{timeout,102},{old_heap_bloc
On Tue, Oct 2, 2012 at 7:55 AM, Kelly McLaughlin wrote:
> John and Shane,
>
> I have been looking into some memory issues lately and I would be very
> interested in more
> information about your particular problems. If either of you are able to get
> some output
> from etop using the -sort memor
Hi,
Is there any particular issue with the Java Riak HttpClient when
using a version other than 4.1.1? I have a pull request that doesn't
pass the Travis CI build, even though I have verified it shouldn't have
issues except for the that specific difference, if so, could it be tried
with Htt
I understand that having everything on one box have side effect and that I
may be limited by disk IOs. But, still, I do not understand why the same
bucket can use different engine on different node and why Riak Control was
reporting everything as OK whereas some nodes were not responding.
On Mon,
John and Shane,
I have been looking into some memory issues lately and I would be very
interested in more
information about your particular problems. If either of you are able to get
some output
from etop using the -sort memory option when you are having elevated memory
usage it
would be very
I would highly suggest you upgrade to 1.2 when possible. We were, up
until recently, running on 1.4 and seeing the same problems you
describe. Take a look at this graph:
http://i.imgur.com/0RtsU.png
That's just one of our nodes but all of them exhibited the same
behavior. The falloffs are where w
G'day!
Just recently we've noticed memory usage in our Riak cluster constantly
increasing.
The memory usage reported by the Riak stats "memory_total" parameter has
been less than 100MB for nearly a year but has recently increased to
over 1GB.
If we restart the cluster memory usage usually
12 matches
Mail list logo
