Re: Bug on riak-client 1.0.6 - Riak index property not serialized

Guido, I guess that is the other side of the coin. Thank for the tip. Deepak Bala On Wed, Sep 26, 2012 at 1:51 PM, Guido Medina wrote: > Deepak, > > That's why in our company we have index annotations at method level, for > us we agreed that an index is not really a POJO property but a > pse

Fwd: Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down?

I forgot to cc to riak-users. -- Forwarded message -- From: Tatsuya Kawano Date: 2012/9/27 Subject: Re: Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down? To: Mike Oxford Hi Mike, Thanks for the detailed info. I'm currently running a

Fwd: Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down?

I forgot to cc to riak-users. -- Forwarded message -- From: Tatsuya Kawano Date: 2012/9/27 Subject: Re: Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down? To: Evan Vigil-McClanahan Thanks, Evan. I tried pr=all and verified it failed

Re: Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down?

What is the time between "node down" and "read with R=3" ? Did you "shut down" the node or kill it by brutally powering the box down or yanking the network cable? It possible that Riak noticed the node_down and had already done the recovery. While net_ticktime can be as long as 60 seconds by defa

Re: Riak client for node.js

Having a Basho backed official client for node.js sounds promising. I'll give it a try and test it. For now, I have one question: I didn't completely get how to set 2i. Do you put something like { indexkey: value } in the option field when calling save? it seems from the code that the x-riak-index-

Reading with "r = all" always succeeds in Riak 1.2 even when one of the primary nodes is down?

Hi, I'm having hard time to verify this behavior on the Riak wiki with my Riak 1.2 test environment. Can anybody help me to figure out what is happening? http://wiki.basho.com/Eventual-Consistency.html#Failure-Scenarios > Reading When One Primary Fails > -- > > 1. Da

Re: Riak client for node.js

The drop of PB in the new js branch is for now just temporary. Allows us to focus on getting the JavaScript code base up to speed at least feature-wise and get a feeling for how things could evolve for its API. Help on getting PB support back into that branch is more than welcome! But I'll also

Re: Key expiration

On Wed, Sep 26, 2012 at 10:04:54PM +0200, Kresten Krab Thorup wrote: > While we're discussing merge and expiry semantic here, I'd like to explain > how HanoiDB does it since that may be a reason for trying it out on your > problem. > > With the HanoiDB backend, merging and expiration is "increm

Re: Key expiration

On Wed, Sep 26, 2012 at 08:33:24PM +0200, Nico Meyer wrote: > Great, this explains why bitcask went merging crazy after we updated > from 0.14 to 1.1! The workaround was to constrain merging to the > nighttime, and since it kind of worked(TM) since then, I never came > round to look for the reason

riak_core application design questions

Hello everyone, I'm in the beginning phases of building a riak_core application and am curious as to how others might recommend I set up my application. Every single bit of my application will be computation only, that is that all storage and data will be managed by Riak. Basically, a client se

Re: Key expiration

While we're discussing merge and expiry semantic here, I'd like to explain how HanoiDB does it since that may be a reason for trying it out on your problem. With the HanoiDB backend, merging and expiration is "incremental", which means that log(N / #partitions) merge/expire operations are perfor

Re: Key expiration

Great, this explains why bitcask went merging crazy after we updated from 0.14 to 1.1! The workaround was to constrain merging to the nighttime, and since it kind of worked(TM) since then, I never came round to look for the reason for the increased I/O load after the update. I just checked, an

Re: Riak client for node.js

The drop of Protocol Buffers (according to the readme) is a sad thing. AFAIK there is not a single usable Riak client lib for node that supports PB :-/D On 26.09.2012, at 20:25, Mark Phillips wrote: > Hi Callixte - > > On Wed, Sep 26, 2012 at 12:51 PM, Callixte Cauchois > wrote: >> Hello, >>

Re: Riak client for node.js

Hi Callixte - On Wed, Sep 26, 2012 at 12:51 PM, Callixte Cauchois wrote: > Hello, > > what would you guys advise me to use to connect to riak in node.js? > Basho seems to push for Voxer's node_riak > (https://github.com/mranney/node_riak), but are there better alternatives? In addition to node_r

Riak client for node.js

Hello, what would you guys advise me to use to connect to riak in node.js? Basho seems to push for Voxer's node_riak ( https://github.com/mranney/node_riak), but are there better alternatives? Thanks. C. ___ riak-users mailing list riak-users@lists.bash

Re: Problem getting Riak multi-backend working

I left out the <<>> around the backend names. My bad. After fixing it, multi backend support seems to be working. From: Lei Gu mailto:l...@e-dialog.com>> Date: Wednesday, September 26, 2012 1:30 PM To: "riak-users@lists.basho.com" mailto:riak-users@lists.basho.

Re: data modeling question

I think, I may copy the contents of each message in the PlayerMessage model to avoid having another lookup. I'll choose higher storage capacity over 10 calls to load each individual message. On Wed, Sep 26, 2012 at 2:51 AM, Rune Skou Larsen wrote: > On 25-09-2012 23:18, Charlie Bowman wrote:

Problem getting Riak multi-backend working

We want to explore Riak multi backend support for the following scenario, configuration data stored in Level DB, while some transit data will be stored in memory and expires after a certain time. Unfortunately I have the toughest time getting multi-backend support to work, every time I tried to

Re: applications inside the same VM as Riak

We're also running several applications inside riak; it's quite simple to just add relevant -pa and -s arguments at the end of vm.args. Kresten On Sep 25, 2012, at 10:56 PM, Mike Oxford mailto:moxf...@gmail.com>> wrote: I am stacking my application and Riak on the same machine. It seems waste

Re: applications inside the same VM as Riak

I've been successfully running a monitoring application (to gather stats from riak) inside of the riak application for over a year with no issues. I also know of another company which uses the internal client because of performance issues with the PB client, so its completely possible to run an ap

Re: Pruning (merging) after storage reaches a certain size?

The only other time I've seen this documented is in a thread from 2011 about pruning (merging) after deletes. Here's the message in question in case any historians are lurking: http://markmail.org/message/4nakwhixkw3jcxvi --- Jeremiah Peschka Managing Director, Brent Ozar PLF, LLC On Thu, Jul 28,

Re: Key expiration

One thing to note about expiration and bitcask, which unfortunately has been causing us much consternation is that key expiration is a silent merge trigger. I guess what happens is if a key expires that somehow causes riak to want to merge that bitcask. If you have keys constantly expiring (which

Re: data modeling question

On 25-09-2012 23:18, Charlie Bowman wrote: Can I load 10 messages in 1 call? similar to a sql call "select * from messages where id in (1,2,3,4,5,6,7,8)" You can specify an array of keys as inputs to a MapReduce job. http://wiki.basho.com/MapReduce-Implementation.html#Inputs MR jobs can be slow

Re: Bug on riak-client 1.0.6 - Riak index property not serialized

Deepak, That's why in our company we have index annotations at method level, for us we agreed that an index is not really a POJO property but a pseudo/computed property, it was a waste for us to add a field just because an index, so we have our own branch of the Riak java client where the m