Hi,
In the security documentation here:
http://docs.basho.com/riak/latest/ops/advanced/security/
Instructions are given for how to limit the port ranges used for internode
communications. E.g.
{ kernel, [
{inet_dist_listen_min, 6000},
{inet_dist_listen_max, 7999}
Hi,
So I'm writing a Java client app. I'm running a 5 node Riak cluster and I want
my client to know about all the nodes to avoid single points of failure.
So, I load a config file with the node addresses in, and configure a
PBClusterConfig instance with a number of PBClientConfig instances, on
So the issue we’re having is only with bucket listing.
alxndrmlr@alxndrmlr-mbp $ time s3cmd -c .s3cfg-riakcs-admin ls
s3://bonfirehub-resources-can-east-doc-conversion
DIR
s3://bonfirehub-resources-can-east-doc-conversion/organizations/
real 2m0.747s
user 0m0.076s
sys 0
Hi Simon,
Quick answer: the more (ports open), the merrier. At least 6.
As these are Erlang specific settings, I recommend having a look at the
official answer [0].
[0] http://www.erlang.org/faq/how_do_i.html#idp27500560
Regards,
Ciprian
On Fri, Aug 15, 2014 at 3:15 PM, Simon Hartley <
simon
We’ve been using Riak with Java client for more than two years in production,
and best solution is ha-proxy.
Your Java client connects to one ha-proxy, configured for round-robin to all
the nodes. We run ha-proxy on our front-ends, so clients always connect to
localhost.
If you’re planning to a
Hi there,
I installed riak-2.0rc1 and the Python client through "easy_intall riak",
however, when importing the "riak" library I got the following error:
Traceback (most recent call last):
File "x.py", line 1, in
import riak
File
"/usr/local/lib/python2.7/dist-packages/riak-2.1.0rc1-py2.
< 2.0 the java cluster client was actively unhelpful (in that it didn't
track node health, so if one node was down, the client would regularly try
it still, IIRC), and a client-local haproxy (or such) is the way to go.
>= 2.0 the java cluster client looks like it's smarter about tracking node
heal
Hi there,
I installed RIAK using the packagecloud.io repository [
https://packagecloud.io/basho/riak/install ], however, every time that I do
an "aptitude update" I receive that RIAK has a new version although is not
true:
aptitude safe-upgrade
The following packages will be upgraded:
riak
1 pa
Fixed, instead of using "easy_install riak" I used "pip install riak" and
it worked like a charm :)
Thanks!
Alex
On Fri, Aug 15, 2014 at 5:29 PM, Alex De la rosa
wrote:
> Hi there,
>
> I installed riak-2.0rc1 and the Python client through "easy_intall riak",
> however, when importing the "riak
Hi Alex,
Try with: pip install cryptography
:tele
On Fri, 15 Aug 2014 17:29:29 +0200
Alex De la rosa wrote:
> Hi there,
>
> I installed riak-2.0rc1 and the Python client through "easy_intall
> riak", however, when importing the "riak" library I got the following
> error:
>
> Traceback (most
Thanks for your reply, I already fixed it deleting everything and using
"pip install riak" instead.
Thanks!
Alex
On Fri, Aug 15, 2014 at 5:59 PM, tele wrote:
> Hi Alex,
>
> Try with: pip install cryptography
>
> :tele
>
>
> On Fri, 15 Aug 2014 17:29:29 +0200
> Alex De la rosa wrote:
>
> > Hi
Hi there,
I created a "counter" bucket called "likes" with the following shell script:
riak-admin bucket-type create likes '{"props":{"datatype":"counter"}}'
When I try to follow the guide [
http://docs.basho.com/riak/2.0.0/dev/using/data-types ] to use this bucket
with Python, I found the follo
Hi Alex,
Use the version from git and see if you get the same error:
git clone https://github.com/basho/riak-python-client.git
cd riak-python-client
python setup.py install
:tele
On Fri, 15 Aug 2014 18:12:09 +0200
Alex De la rosa wrote:
> Hi there,
>
> I created a "counter" bucket called "l
My preference is for each client application node to connect to an instance
of haproxy on the localhost, that way cluster changes only requires
updating and reloading the haproxy config--which is cleaner and safer for
production services.
An example haxproxy config can be found on the Riak docs:
h
Hi, thanks for your suggestion, but I would prefer to use the official
packages, and for what I saw on the list some days ago, the new version was
published, so I wonder why is not yet working.
Thanks,
Alex
On Fri, Aug 15, 2014 at 6:20 PM, tele wrote:
> Hi Alex,
>
> Use the version from git an
Hi Alex,
The published version is not a final release, so it won't be
automatically installed by pip. Try this: pip install riak==2.1.0rc1
Also, did you activate your bucket-type using riak-admin? It won't be
usable until it's activated.
On Fri, Aug 15, 2014 at 12:02 PM, Alex De la rosa
wrote:
Hi Sean,
I activated the bucket as follows:
riak-admin bucket-type create likes '{"props":{"datatype":"counter"}}'
So in theory is good to go; seems I have version 2.0.3 installed instead of
2.1.0rc1. It might be this. If I install it with your command, would I have
any compatibility issues once
Alex,
Creating a bucket type does not also activate it. That is a separate step:
*riak-admin bucket-type activate likes*
If that returns *likes has been activated* or something along those lines,
then the bucket type is ready to be used.
Luc
On Fri, Aug 15, 2014 at 10:37 AM, Alex De la rosa
Hi Luc,
Thanks for your input! I missed that line in the documentation :) is fully
activated now.
Thanks,
Alex
On Fri, Aug 15, 2014 at 7:40 PM, Luc Perkins wrote:
> Alex,
>
> Creating a bucket type does not also activate it. That is a separate step:
>
> *riak-admin bucket-type activate likes*
Old thread, but we're still running into similar issues in 2014 (possibly due
to https://github.com/basho/riak_kv/issues/311)
In case it helps anyone, here's a quick ruby script to crawl through and
remove the tombstones
*use at your own risk* - you're not supposed to list all keys in production
Hello Alex. Would you mind sharing what version of Riak and Riak CS you
are using? Also if you can post the the contents of your Riak CS
app.config file
it might help give a better idea of what might be going on.
Generally listing the contents of a bucket is more expensive than a
normal downlo
21 matches
Mail list logo
