Hi Michael,
Could you provide all the result of "riak config generate -l debug" as well as
riak.conf and advanced.config?
Thanks,
Shino
2016-01-07 9:05 GMT+09:00 Michael Walsh :
> All,
>
> I'm trying to set up a RIak S2 instance to integrate with KV and I'm getting
> the following cuttlefish err
All,
I'm trying to set up a RIak S2 instance to integrate with KV and I'm
getting the following cuttlefish error out of advanced.config. Any
suggestions on where I'm going wrong?
notes: erlang error was fixed. All paths are correct.
Thanks!
-Michael Walsh
$riak config generate -l debug
...
Hi,
I run bash bench. i used riakc_pb_text.config in examples..
put operation fails with below error:
[error] Supervisor basho_bench_sup had child undefined started with
basho_bench_worker:start_link(basho_bench_worker_2, 2) at <0.96.0> exit
with reason normal in context child_terminated
17:50
> We're planning on having a rather large cluster rather soon, which was
> the reason for the large ring size. Your documentation indicates ring
> resize is *not* possible with search 2.0 [1], although an issue I
> found on github indicated it might be now? [2]
Yeah, resize not applicable in your
Hi Josh,
Sorry for not getting back sooner.
I am not entirely sure what is going on with your handoffs. It could be that
you have overloaded Solr with handoff activity, and that is causing vnodes to
become unresponsive. We are actively working on a fix for this, which allows
vnodes to conti
Hi,
I need to handle up to 5K writes per second at peak, with payload sizes
ranging from 10KB to 100KB.
I haven't done any benchmarks currently, but just as a high level is this
type of usage scenerio a good fit for Riak?
This will be a write heavy usage, and I will then push things to elastic
s
Hi Luke,
We're planning on having a rather large cluster rather soon, which was
the reason for the large ring size. Your documentation indicates ring
resize is *not* possible with search 2.0 [1], although an issue I
found on github indicated it might be now? [2]
If the situation is resolved we mi
Hi Josh,
1024 is too large of a ring size for 10 nodes. If it's possible to
rebuild your cluster using a ring size of 128 or 256 that would be
ideal
(http://docs.basho.com/riak/latest/ops/building/planning/cluster/#Ring-Size-Number-of-Partitions).
Ring resizing is possible as well
(http://docs.ba
Hi,
We're attempting to use Riak as our primary key-value and search
database for an analytics-typed solution to blocking spam/fraud.
As we expect to eventually be handling a huge amount of data, I
started with a ring size of 1024. We currently have 10 nodes on Google
Cloud n1-standard-16 instanc
