Hi Gary,
Yes, unfortunately, this is a bug. (Tracked here:
https://issues.basho.com/show_bug.cgi?id=867) We have not yet scheduled the
fix for this.
Best,
Rusty
On Mon, Feb 28, 2011 at 1:25 AM, Gary William Flake wrote:
> Ack. I know what's happening with this. Riaksearch is sorting by
> rel
FWIW, here's my workaround written for riak-js:
done = false;
db.addSearch('clips', q, opts)
.map('Riak.mapValuesJson')
.reduce('Riak.reduceSort', 'function(a,b){return a.ctime-b.ctime;}')
.reduce('Riak.reduceSlice', [start,rows])
.run(function(err, x) {
for (var i = 0, n = x.lengt
Hi all,
I've come across some issues while testing what happens when failures happen
on our system, for example a machine failing. One of the (slightly scary)
issues I have come across is for a short while when a Riak node goes down,
data that is read from another node isn't always consistent. I h
I think it has to do with how the vnodes are partitioned against your
physical nodes. You really need a minimum of three physical nodes (or
virtual machines) to deploy and or do any failure testing.
-Alexander
On Mon, Feb 28, 2011 at 13:29, Luca Spiller wrote:
> Hi all,
>
> I've come across some
Hi Luca,
For any request Riak will ask 3 vnodes for an object's value (assuming N=3).
If a majority of vnodes return "not found", Riak will return "not found" to
the client. When a node is taken down other nodes can act as a fallback for
that node. When a fallback node takes over for a primary nod
Hey All,
Just a quick email to spread some great community news...
Over the weekend we added Kevin Burns as a committer on the Riak PHP Client.
If you read the Recaps you already know that Kevin, who goes by
"KevBurnsJr", has been hard at work making the PHP client more robust
and recently start
In the midst of a discussion about messaging and eventual consistency and I'm
wondering if there's a reasonable answer to the question:
Is eventual consistency in a system that needs to know when it can start
querying the system for the just-inserted data not a problem if there is an
event trig
This is handled in Dynamo-style architectures like Riak with quorums. In
Riak's case, you rely on the "W" and "DW" quorum values to determine what is an
acceptable threshold for considering a write to be a success. By default, W
and DW are set to "quorum", which means N/2+1 (for N=3, this is 2
Correct me if I'm wrong but you write a high-performance app by specifying
dw=all on every write. I'm thinking something along the lines of "take your
time inserting the data, just let me know when you're finished". That's
drastically different from "don't return from this call until you've writ
Ah, I misunderstood you. This would be an interesting addition to Riak, but is
not in the current roadmap. The request coordinators currently reply and exit
as soon as quorum is met, even if that's 0, so the replies from the vnodes
never get delivered if the coordinator is gone.
Sean Cribbs
De
Afternoon, Evening, Morning to Everyone,
Here's a short Recap from the last few days.
Enjoy.
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
---
Riak Recap for Feb. 25 - 27
1) Q --- Trying to get riak running on ubuntu. I installed the deb
package, but when
11 matches
Mail list logo
