- Original Message -
From: "Russell Brown"
To: "Jason Campbell"
Cc: "riak-users" , "Viable Nisei"
Sent: Saturday, 21 December, 2013 8:25:01 PM
Subject: Re: May allow_mult cause DoS?
>Hi,
>What is a "sibling with no parent object”?
Hi,
On 20 Dec 2013, at 23:16, Jason Campbell wrote:
>
> - Original Message -
> From: "Andrew Stone"
> To: "Jason Campbell"
> Cc: "Sean Cribbs" , "riak-users"
> , "Viable Nisei"
> Sent: Saturday, 21 December, 2
- Original Message -
From: "Andrew Stone"
To: "Jason Campbell"
Cc: "Sean Cribbs" , "riak-users" ,
"Viable Nisei"
Sent: Saturday, 21 December, 2013 10:01:29 AM
Subject: Re: May allow_mult cause DoS?
> Think of an object with thous
of those 10,000.
>
> -Andrew
>
>
> On Fri, Dec 20, 2013 at 5:41 PM, Jason Campbell wrote:
>
> From: "Sean Cribbs"
> To: "Jason Campbell"
> Sent: Saturday, 21 December, 2013 3:17:57 AM
>
> Subject: Re: May allow_mult cause DoS?
>
> > No,
0,000.
-Andrew
On Fri, Dec 20, 2013 at 5:41 PM, Jason Campbell wrote:
>
> --
> *From: *"Sean Cribbs"
> *To: *"Jason Campbell"
> *Sent: *Saturday, 21 December, 2013 3:17:57 AM
>
> *Subject: *Re: May allow_mult cause DoS?
>
>
- Original Message -
From: "Sean Cribbs"
To: "Jason Campbell"
Sent: Saturday, 21 December, 2013 3:17:57 AM
Subject: Re: May allow_mult cause DoS?
> No, the behavior in LevelDB is no different than the behavior of any of our
> other backends, namel
On Thu, Dec 19, 2013 at 11:14 PM, Jason Campbell wrote:
> Can anyone familiar with Riak internals describe how siblings are handled
> in Level DB? I think part of this issue is a misunderstanding of how that
> works and false expectations.
>
> As far as I understand, siblings are light at write t
users@lists.basho.comSubject: SV: May allow_mult cause DoS?Save the transaction list inside the customer object keyed by customerid. Index this object with 2i on storeids for each contained tx.If some customer objects grow too big, you can move old txs into archive objects keyed by customerid_seqno. For you
alistic data
> sizes/shapes and access patterns. It's fastest if we come onsite for a couple
> of days and work with you to set it up, but we can also help you offsite.
>
> Write me if you're interested, then we can do a call.
>
> Rune Skou Larsen
> Trifork, Denma
, but we can also help you
> offsite.
>
> Write me if you're interested, then we can do a call.
>
> Rune Skou Larsen
> Trifork, Denmark
>
>
> - Reply message -
> Fra: "Viable Nisei"
> Til: "riak-users@lists.basho.com"
> Emne: M
s and work with you to set it up, but we can also help you offsite.
Write me if you're interested, then we can do a call.
Rune Skou Larsen
Trifork, Denmark
- Reply message -
Fra: "Viable Nisei"
Til: "riak-users@lists.basho.com"
Emne: May allow_mult cause D
-- Forwarded message --
From: Viable Nisei
Date: Thu, Dec 19, 2013 at 2:11 AM
Subject: Re: May allow_mult cause DoS?
To: Russell Brown
Hi.
Thank you for your descriptive and so informative answer very much.
On Wed, Dec 18, 2013 at 3:29 PM, Russell Brown wrote:
> Hi,
>
hat it's optimized for...
> Can you tell us exactly why you need Bitcask rather than LevelDB? 2i would
> probably do it.
> Otherwise, storing a list of items under each key could be a solution,
> depending of course on the number of items per key. (But do perform conflict
> re
items under each key could be a solution,
> depending of course on the number of items per key. (But do perform
> conflict resolution.)
> /Erik
>
>
>
> Oprindelig meddelelse
> Fra: Viable Nisei
> Dato:
> Til: riak-users@lists.basho.com
> Emne:
key could be a solution,
depending of course on the number of items per key. (But do perform conflict
resolution.)
/Erik
Oprindelig meddelelse
Fra: Viable Nisei
Dato:
Til: riak-users@lists.basho.com
Emne: May allow_mult cause DoS?
Hi.
Recently we've described tha
On Tue, Dec 17, 2013 at 10:28 AM, Viable Nisei wrote:
> Here you can check our code sample (in java) reproducing this behavior:
> https://bitbucket.org/vsnisei/riak-allow_mult_wtf
> ...
> Anyway, looks like that some DoS/DDoS attack approach utilizing this
> behavior may be proposed. We should onl
Hey,
Are you _resolving_ the siblings that you create? It sounds like you’re
purposely creating siblings and not resolving them, as I read things like
‘only 80-100 values per … keys’. Riak is not intended to be used this way.
80 siblings is a lot, and will dramatically decrease performance for tha
Hi.
Recently we've described that something is going unexpectedly. We are using
Riak 1.4.2 with some buckets with allow_mult=true.
We've tried our app under load then found that... concurrently writes into
bucket with allow_mult turning Riak into irresponsible slowpoke and even
crash it.
Core i3
18 matches
Mail list logo