b_backend, [
>{data_root,"/home/pi/src/riak/deps/eleveldb"}
>]},
>{be_blocks, riak_kv_bitcask_backend, [
>{data_root,"/home/pi/src/riak/deps/bitcask"}
> ]}
>]}
> ]}.
Please let me know if that configuration change gets you go
generically-applicable information about [cluster capacity
planning]
<http://docs.basho.com/riak/kv/2.2.3/setup/planning/cluster-capacity/> in the
Riak KV documentation.
Thanks again for your interest,
Charlie Voiselle
Sr. Product Manager, Riak KV/Clients
Basho Technologies
@angrycub
[cluster ca
unt is required).
If you run Riak KV on AWS, you can also update to using the latest AMI.
As always, we would like to hear your feedback, suggestions or bug reports.
Best regards,
Charlie Voiselle
Senior Product Manager - Riak KV, Basho Technologies
@angrycub
[issue] - https://github.com
We have identified a late-breaking issue specific to the Ubuntu builds. We have
pulled the packages from their hosted locations in the interim, and they will
be available shortly. I will send an email to the list once we have resolved
this issue.
Thanks,
Charlie Voiselle
Senior Product
f you run Riak KV on AWS, you can also update to using the latest AMI.
As always, we would like to hear your feedback, suggestions or bug reports.
Best regards,
Charlie Voiselle
Senior Product Manager - Riak KV, Basho Technologies
@angrycub
[fixed] - https://github.com/basho/node_package/pull/
ers can download Riak KV from your Zendesk page (valid
Basho Zendesk account is required).
If you run Riak KV on AWS, you can also update to using the latest AMI.
As always, we would like to hear your feedback, suggestions or bug reports.
Best regards,
Charlie Voiselle
Senior Product Manager - Ria
your Zendesk page (valid
Basho Zendesk account is required).
If you run Riak KV on AWS, you can also update to using the latest AMI once it
is released.
As always, we would like to hear your feedback, suggestions or bug reports.
Best regards,
Charlie Voiselle
Senior Product Manager - Ri
. We have seen this
before at a customer site where they were collecting the statics from the
vnode-status command into their metrics system.
Regards,
Charlie Voiselle
> On Feb 23, 2017, at 7:14 AM, Douglas Rohrer wrote:
>
> Andrey:
>
> It's waiting for 60 seconds, l
.
Basho customers with any questions are encouraged to contact either their
account managers or the Basho Client Services <https://help.basho.com/> team.
Basho community members can contact us via the riak-users mailing list.
Best regards,
Charlie Voiselle
Senior Product Manager - Riak KV,
ownload Riak KV from your Zendesk page (valid
Basho Zendesk account is required).
If you run Riak KV on AWS, you can also update to using the latest AMI.
As always, we would like to hear your feedback, suggestions or bug reports.
Best regards,
Charlie Voiselle
Senior Product Manager - Ri
ing with our community and our customers on this new release of Riak KV.
Charlie Voiselle
Senior Product Manager - Riak KV, Basho Technologies
@angrycub
[1] - http://basho.com/posts/technical/riak-kv-2-2-release-highlights/
[2] - http://docs.basho.com/riak/kv/2.2.0/release-notes/
[3] - http:
cements to Multi-data Center Replication
I sincerely appreciate your feedback.
Regards,
Charlie Voiselle
Product Manager, Riak KV and Clients
> On Oct 3, 2016, at 1:34 PM, Ricardo Mayerhofer wrote:
>
> Hi everyone,
> Despite seeing new components being added to Basho data solutions,
{be_blocks, riak_kv_bitcask_backend, [
{data_root, "/var/lib/riak/bitcask"}
]}
]}
]}
].
Give that a shot and let us know if it works for you!
Thanks,
Charlie Voiselle
> On Jan 7, 2016, at 11:53 AM, Michael Walsh wrote:
>
> Sur
, sorry I think I was misled by the `config OK` signal at the beginning
> of the error.
>
> On Tue, Nov 24, 2015 at 11:40 AM, Charlie Voiselle <mailto:cvoise...@basho.com>> wrote:
> Ben:
>
> It is not uncommon to see the
>> [os_mon] memory supervisor port (mems
Another thing that I have seen cause riak_kv to stall like this is LevelDB
corruption preventing vnodes from starting properly. I use this command to
look for LOG files with the word error in them. It is also worth checking the
anti_entropy levelDB LOG files as well.
find . -name "LOG" -exec
nodes.
Hope this gets you back up and going,
Charlie Voiselle
Client Services, Basho
>
> On May 25, 2015, at 11:43 AM, Vitaly E <13vitam...@gmail.com> wrote:
>
> Which version of Riak are you using? Do you see any error messages?
>
> Also, what Java program are you ref
to restore the
replicas from the adjacent partitions. I can provide more information if you
find that to be the case.
Regards,
Charlie Voiselle
Client Services, Basho
On May 14, 2015 10:06 PM, "Engel Sanchez" mailto:en...@basho.com>> wrote:
Hi Johnny. Make sure that the confi
This error is usually caused when `admin.listener` is configured in
riak-cs.conf. Either remove that line from the configuration file, or use
that IP and port for your create user request.
Please let me know if that helps you out
Charlie Voiselle
Basho Client Services
On Apr 23, 2015 8:46 AM
g),
{Targets, Fallbacks} = lists:split(N, Preflist),
Targets.
Verify that `N` matches your clusters N-val. Change `my_bucket` and `my_key` as
appropriate. If all of your nodes are up and healthy, this will give you the
primaries in the `Targets` variable and the fallback partitions in order of
pre
tion for the version that you have installed
Cheers,
Charlie Voiselle
Basho Client Services
> On Jan 12, 2015, at 8:58 AM, Ildar Alishev wrote:
>
> i have changed nodename and now it says
>
> root@salo:~# riak stop
> Node 'riak@192.168.1.55 <mailto:riak@192.168.1.5
Invalid hint files will be rebuilt automatically during the Bitcask merge
process. I believe you are seeing a one-time consequence of switching to
signed hint files during the upgrade. Not to worry, they will be
regenerated through normal merge activity.
Regards,
-cv
On Jan 17, 2014 6:56 AM, "
},
{use_bloomfilter, true},
{max_open_files, 20}]},
This might not solve your specific problem, but it will certainly improve your
AAE performance.
Thanks,
Charlie Voiselle
On Dec 31, 2013, at 12:04 PM, Edgar Veiga wrote:
> Hey g
Louis-Philippe et al:
You can follow the rolling upgrade procedure to upgrade a node from 1.2 to
1.4.x directly. The note in the instructions only concerns upgrading from 1.0
to 1.4.
No need to stop at 1.3.2.
Thanks,
Charlie Voiselle
On Aug 13, 2013, at 9:23 AM, Guido Medina wrote
Kevin:
As mentioned in the Riak MapReduce documentation, you can find more information
about the pre-built MR jobs here:
https://github.com/basho/riak_kv/blob/master/src/riak_kv_mapreduce.erl --
Erlang Module that contains all of the pre-built Erlang MapReduce Phases
https://github.com/basho/r
827966271488},
{913438523331814323877303020447676887284957839360},
{1096126227998177188652763624537212264741949407232},
{1278813932664540053428224228626747642198940975104}]}
Hope this helps!
Charlie Voiselle
---
[0] https://github.com/basho/riak_core/blob/master/src/chash.erl#L88
[1] https://github.com/basho/riak_core/blo
ed to
1096126227998177188652763624537212264741949407232 makes sense. That partition
would hold items that hash from
913438523331814323877303020447676887284957839361 to
1096126227998177188652763624537212264741949407232
Does this help?
Thanks,
Charlie Voiselle
On Jan 24, 2013, at 12:05 AM, Donald Yan wrote:
> Hi there,
>
&g
, it's easier to roll
back the changes to the configuration and get the nodes starting again.
Once they are started and running, here's a writeup of the scheme you would use
to do the rolling configuration changes: https://gist.github.com/4566736
Thanks,
Charlie Voiselle
On Dec 29,
rking cluster (to save on cost).
>
> By using the 'riaknode1.priv' hostname method you describe, would I be able
> to stop and then restart a whole cluster of nodes at once? (As described by
> Deepak, AWS assigns new IPs when a VM starts).
>
> Thanks
> Matt
>
>
Deepak:
When you name a node in app.config with -name it has to have a '.' in it, like
r...@hostname.net As you have surmised, you can get around that if you use the
-sname argument instead.
They have to be done consistently. In your example, had you used the -sname
argument, `riak@riaknod
29 matches
Mail list logo
