Re: AAE Off

How would the data get repaired then? i.e. looking for complete list of Cons when AAE is Off. On Tue, Feb 28, 2017 at 9:45 AM, Alexander Sicular wrote: > Right. AAE does not come for free. It consumes disk, memory and CPU. > Depending on your circumstances it may or may not

AAE Off

Why would anyone disable AAE in riak 2.x? ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: AAE Off

Right. AAE does not come for free. It consumes disk, memory and CPU. Depending on your circumstances it may or may not be advantageous for your system. On Tue, Feb 28, 2017 at 11:39 Matthew Von-Maszewski wrote: > Performance gains on write intensive applications. > > > On

Re: AAE Off

Performance gains on write intensive applications. > On Feb 28, 2017, at 11:18 AM, al so wrote: > > Why would anyone disable AAE in riak 2.x? > ___ > riak-users mailing list > riak-users@lists.basho.com >

Re: Leveled - Another Erlang Key-Value store

For original testing in isolation I used this: https://github.com/martinsumner/leveled/blob/master/test/volume/single_node/src/basho_bench_driver_eleveleddb.erl But I've focused on testing since within Riak using the standard basho_bench/examples/riakc_pb.config test Testing of secondary

Re: Leveled - Another Erlang Key-Value store

Have a look in https://github.com/martinsumner/leveled/blob/master/docs/FUTURE.md and the "Riak Features Implemented" I'm trying to avoid the need for Riak to Get n times for every request (both a KV GET and a KV PUT), when really it only needs the body once, and the n-1 times it doesn't need the

Re: Leveled - Another Erlang Key-Value store

Cheers indeed! You added HEAD requests so a full GET wouldn't always be required? Did I read that right? *dives into code* %% GET requests first follow the path of a HEAD request, and if an object is %% found, then fetch the value from the Journal via the Inker. ... WHAT? Very nice work, will be

Re: Issue with yokozuna_extractor_map (riak 2.1.1)

Hi Simon - Did you copy the .beam file for your custom extractor to a directory in the Erlang VM's code path? If you run "pgrep -a beam.smp" you'll see an argument to beam.smp like this: -pa /home/lbakken/Projects/basho/riak_ee-2.1.1/rel/riak/bin/../lib/basho-patches On my machine, that adds

[Ann] Riak TS 1.5.2 released

Dear Riak Users, Last week we have released Riak TS 1.5.2, which is available in both OSS and EE editions. It is a bugfix release, no new features or incompatible changes. As always, we encourage you to upgrade to the latest version. Please see Release Notes [1] for details. Additionally, our

Re: Riak: reliable object deletion

Implications when *delete_mode *set to 'keep'*?* On Thu, Feb 23, 2017 at 9:53 PM, al so wrote: > Present both in Solr and Riak. It's a 1-way replication in MDC. MDC is not >> the cause unless there is a bug there as well. >> >> >> On Thu, Feb 23, 2017 at 6:02 AM, Fred

Leveled - Another Erlang Key-Value store

Over the past few months I've been working on an alternative pure-Erlang Key/Value store to act as a backend to Riak KV. This is now open source and available at https://github.com/martinsumner/leveled The store is a work-in-progress prototype, originally started to better understand the impact

Issue with yokozuna_extractor_map (riak 2.1.1)

Hi, I’m currently experimenting with riak 2.1.1 for a project. I recently ran into some trouble with yokozuna trying to register a custom extractor. I’m not sure how I ended up in that situation, but I’m currently stuck with my cluster's yokozuna_extractor_map equal to the atom ignore… I