Hi guys,Can someone please help answer below?
Regards,NiravÂ
From: Nirav Shah
To: "riak-users@lists.basho.com"
Sent: Friday, January 2, 2015 10:05 AM
Subject: RIAK Search - Active Anti-Entropy
Hello,I have a production database which is fairly large and uses Secondary
Indexes. I
Hey all,
So, the long and short of it is that Riak doesn't handle objects
larger than 2Mb very well at all. We try to be pretty up-front about
this in the documentation (for example[1]) be we're also aware that
sometimes you need to store big objects. Riak CS was actually created
to deal with thes
Hi,
I'd be interested in the answer to this too, isn't it inevitable that in the
underlying storage you will get compaction delays, you see the same in any key
value store, eg if you were pushing lots of small packets of data into
HBase/Cassandra etc... Eventually the system has to perform the
Hi Cezary,
The keys in a map are pairs, {FieldName, FieldType}, and when map reducing they
haven’t been through the API layer to make the module names friendly, so rather
than {my_name, set} you have {may_name, riak_dt_orswot}.
For example
M = riak_kv_crdt:map_value(V).
[{{<<"m1">>,ria
Hey Andy,
We had the same issue few days ago. We were getting timeouts when trying to
read a key from riak.
Also we were seeing in the logs a warning about reading/writing a large
object. In our case that object was first read from riak and after written
back. It was that big (17Mb) because of so
Hi all,
I've been experiencing stalls where riak won't return any data (queries
time out) with my riak cluster. Here are some basic details:
- 8 nodes
- riak 1.4.10 (upgraded from 1.4.6 -> 1.4.8 -> 1.4.10)
- leveldb backend
- n_val is 2
- allow_mult is false
- ec2 i2.2xlarge boxes (8 cores, 61gb
