Hi Douglas. Would you mind sharing the riak_core section of your
app.config? And also the output of `riak-admin bucket-type status default`
for a node that has been restarted after the app.config has been updated
with the change to the default bucket properties.
On Wed, Jun 10, 2015 at 10:06 AM, D
Hi Timo. Did you check if there is active anti-entropy activity? [1] That
could generate a lot of I/O in the background while building the trees with
the data needed for automatic repair or running exchanges to verify
replicas are up to date.
[1] http://docs.basho.com/riak/latest/ops/advanced/aae
Hi Henning. While Alex Moore in the clients team is looking at the client
side of this issue, I looked up the error messages you were getting in the
log and sent to him. Messages like this:
2015-05-08 14:12:18.103 [error] <0.937.0> gen_server <0.937.0>
terminated with reason: no function clause ma
Hi Johnny. Make sure that the configuration on that node is not different
to the others. For example, it could be configured to never merge Bitcask
files, so that space could never be reclaimed.
http://docs.basho.com/riak/latest/ops/advanced/backends/bitcask/#Configuring-Bitcask
On Thu, May 14, 2
load command in the Riak console after placing it in
the basho-patches directory. You would need to run bin/riak attach, the
issue the command:
> l(riak_kv_bitcask_backend).
That is a lowercase L up there, btw. This should resolve the Bitcask merge
issues.
On Wed, Sep 3, 2014 at 1:00 PM, En
Hi Lucas.
Unfortunately, you have hit a bug in the Bitcask backend that we
overlooked. The attached beam file is a patched version of the backend
code that should resolve the issue for you. To use it, stop each node, then
place riak_kv_bitcask_backend.beam in your basho-patches directory, then
re
Simon: The data scan for that partition seems to be taking more than 5
minutes to collect a batch of 1000 items, so the 2i repair process is
giving up on it before it has a chance to finish. You can reduce the
likelihood of this happening by configuring the batch parameter to
something small. I
know
how the stats and the logs look like after AAE is off to see what else we
can do.
On Thu, Jun 5, 2014 at 1:05 PM, Engel Sanchez wrote:
> Hi Alain. I don't think you are seeing the AAE issue. The problem with
> upgrading from 1.4.4-1.4.7 to 1.4.8 was a broken hash function in tho
Hi Alain. I don't think you are seeing the AAE issue. The problem with
upgrading from 1.4.4-1.4.7 to 1.4.8 was a broken hash function in those,
which made the AAE trees incompatible. You should not have the same problem
in 1.4.0. It seems that Erlang processes are repeatedly crashing and
restartin
Hey there. There are a couple of things to keep in mind when deleting
invalid AAE trees from the 1.4.3-1.4.7 series after upgrading to 1.4.8:
* If AAE is disabled, you don't have to stop the node to delete the data in
the anti_entropy directories
* If AAE is enabled, deleting the AAE data in a rol
Toby,
Since data inserted into the AAE trees while versions 1.4.4 -> 1.4.7 of
Riak were running was incorrect, they should be discarded before the
upgrade. You are seeing them valiantly trying to repair themselves based
on the incoming writes, but that activity is wasted since they require a
full
Hello there,
This looks puzzling. Just from looking at the code we haven't found
anything suspicious. Would you mind posting a pair of those files that
failed to match somewhere so we can look at the differences?
Thanks for reporting this.
Engel@Basho
On Fri, Nov 8, 2013 at 2:41 PM, finkle mcg
Hi Dave,
The stats calculation was fixed in 1.3.1, but the read-repair with
Last-write-wins=true was not backported. That one will make it to 1.4,
which is scheduled in the near future. I hope that helps.
--
Engel Sanchez
On Thu, Apr 4, 2013 at 11:05 AM, Dave Brady wrote:
> Hi Jared,
&g
Hi Oved. If Riak search is anything like Lucene search, the correct way to
query that would be:
Name:c1 OR Name:c2
Did you try that? I believe this also works in lucene: Name:(c1 OR c2)
Sorry to answer without actually trying this on Riak, just from my Lucene
experience. But it's worth a try.
14 matches
Mail list logo
