default bucket settings

Mark Phillips mark at basho.com
Tue Oct 9 15:30:23 EDT 2012


On Tue, Oct 9, 2012 at 11:04 AM, Mark Phillips <mark at basho.com> wrote:

> Hi pozdrawiam,


Oops. Sorry for the name mixup, Paweł. I only speak English, French, and
Erlang. :)

pozdrawiam
Mark



>
> Excellent suggestion. A few things:
>
> * We just redid all of our documentation (and it's live as of this week):
> docs.basho.com.
>
> There's a blog going out about this in a bit, and redirects from
> wiki.basho.com should be in place tomorrow at the latest.
>
> * If you have a few spare minutes, can you add an issue to the basho_docs
> GitHub repo about what we need to clarify/tweak?
>
> https://github.com/basho/basho_docs
>
> Best,
>
> Mark
>
>
>
> On Tue, Oct 9, 2012 at 10:40 AM, kamiseq <kamiseq at gmail.com> wrote:
>
>> thanks for replay.
>>
>> it would be great if someone changed http://wiki.basho.com/Buckets.htmlor
>> http://wiki.basho.com/Configuration-Files.html, I think this would be
>> less misleading
>>
>>    - rw - quorum for both operations (get and put) involved in deleting
>>    an object (default is set at the bucket level)
>>    - r - (read quorum) how many replicas need to agree when retrieving
>>    the object
>>    - w - (write quorum)* how many vnodes must confirm reviving write
>>    request before returning a successful response*
>>    - dw - (durable write quorum) how many replicas to commit to durable
>>    storage before returning a successful response
>>    - pr - (primary read quorum) works like r but requires that the nodes
>>    read from are not fallback nodes
>>    - pw - (primary write quorum) how many replicas to commit to primary
>>    nodes before returning a successful response
>>
>>
>>
>> pozdrawiam
>> Paweł Kamiński
>>
>> kamiseq at gmail.com
>> pkaminski.prv at gmail.com
>> ______________________
>>
>>
>> On 9 October 2012 19:18, Evan Vigil-McClanahan <emcclanahan at basho.com>wrote:
>>
>>> The difference between w and dw is that for r, only the vnode needs to
>>> reply that it's gotten the write.  On dw, the vnode waits for its backend
>>> to reply that it has sent the write to the disk.  So with dw, you trade off
>>> latency for a bit more safety.
>>>
>>>
>>> On Tue, Oct 9, 2012 at 10:14 AM, kamiseq <kamiseq at gmail.com> wrote:
>>>
>>>> you know what, after another day of searching I ve found out that
>>>> (following http://wiki.basho.com/HTTP-Delete-Object.html)
>>>>
>>>>    - rw - quorum for both operations (get and put) involved in
>>>>    deleting an object (default is set at the bucket level)
>>>>    - r - (read quorum) how many replicas need to agree when retrieving
>>>>    the object
>>>>    - pr - (primary read quorum) works like r but requires that the
>>>>    nodes read from are not fallback nodes
>>>>    - w - (write quorum) how many replicas to write to before returning
>>>>    a successful response
>>>>    - dw - (durable write quorum) how many replicas to commit to
>>>>    durable storage before returning a successful response
>>>>    - pw - (primary write quorum) how many replicas to commit to
>>>>    primary nodes before returning a successful response
>>>>
>>>> why such description cannot be added to page about bucket
>>>> configuration, it is really weird to find it in delete object http API
>>>> specification.
>>>>
>>>> still I dont get difference between w and dw but I guess it is not that
>>>> important for now
>>>> pozdrawiam
>>>> Paweł Kamiński
>>>>
>>>> kamiseq at gmail.com
>>>> pkaminski.prv at gmail.com
>>>> ______________________
>>>>
>>>>
>>>> On 9 October 2012 09:19, kamiseq <kamiseq at gmail.com> wrote:
>>>>
>>>>> thanks,
>>>>> I also visited that section but it deals only with n, r and w property
>>>>> in general. and reading only about n, r and w it feels like you know what
>>>>> is going on, and then you see dw, rw, pr and pw and googling doesn't bring
>>>>> clear explanation, so you get more and more confused.
>>>>>
>>>>> (heh I know casing doesn't matter :)
>>>>>
>>>>>
>>>>> pozdrawiam
>>>>> Paweł Kamiński
>>>>>
>>>>> kamiseq at gmail.com
>>>>> pkaminski.prv at gmail.com
>>>>> ______________________
>>>>>
>>>>>
>>>>> On 9 October 2012 07:31, Martin Westergaard Lassen <
>>>>> mwltrifork at gmail.com> wrote:
>>>>>
>>>>>> Hi Pawel
>>>>>>
>>>>>> The "Concept" wiki page (
>>>>>> http://wiki.basho.com/Concepts.html#Reading%2C-Writing%2C-and-Updating-Data)
>>>>>> has a  good introduction to the most important paramters. Casing doesn't
>>>>>> matter, so r=R.
>>>>>>
>>>>>> The Riak Handbook has a good and deep explanation of what those
>>>>>> parameters are http://riakhandbook.com
>>>>>>
>>>>>>  *Martin Westergaard Lassen*
>>>>>> *Software Pilot*
>>>>>> ** **
>>>>>> Trifork A/S****
>>>>>> Margrethepladsen 4 · 8000 Aarhus C. · Denmark****
>>>>>> Mobile +45 31 12 10 59
>>>>>> ** **
>>>>>>
>>>>>>
>>>>>> Den 08/10/2012 kl. 22.56 skrev kamiseq <kamiseq at gmail.com>:
>>>>>>
>>>>>> Im looking for explanation what exactly r, pr, w, dw, pw, rw stands
>>>>>> for.
>>>>>>
>>>>>> Im sorry if this was already posted but I cannot find anything on
>>>>>> that. I tried wiki.basho.com/Riak-Glossary.html,
>>>>>> http://wiki.basho.com/HTTP-API.html#Bucket-Operations,
>>>>>> http://wiki.basho.com/Buckets.html but it only describes N, R, W.
>>>>>>
>>>>>> do I understand correctly that W property is only considered when
>>>>>> updating value and for first store N value is used? or is it:
>>>>>> replicate data N times but return success if it was persisted to W
>>>>>> vnodes.
>>>>>> if DW is durable write then what W really means? can I get successful
>>>>>> response after write operation without object being persisted to
>>>>>> durable storage??
>>>>>>
>>>>>> I must admit Im quite confused here.
>>>>>>
>>>>>> And second question, If I set r, pr, w, dw, pw, rw in app.config for
>>>>>> every configured node in cluster those values will not be added to
>>>>>> gossiped information, right?
>>>>>>
>>>>>> pozdrawiam
>>>>>> Paweł Kamiński
>>>>>>
>>>>>> kamiseq at gmail.com
>>>>>> pkaminski.prv at gmail.com
>>>>>> ______________________
>>>>>>
>>>>>> _______________________________________________
>>>>>> riak-users mailing list
>>>>>> riak-users at lists.basho.com
>>>>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> riak-users mailing list
>>>> riak-users at lists.basho.com
>>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> riak-users mailing list
>> riak-users at lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20121009/d1508d9e/attachment.html>


More information about the riak-users mailing list