Hi there,
Using the Python client, in the documentation I can read this:
"The client maintains a connection pool behind the scenes, one for each
protocol. Connections are opened as-needed; a random node is selected when
a new connection is requested."
Imagine that I create my connection like thi
Hi there,
I was testing 2i via PBC on Python and I found a wrong behaviour, this is
my code:
---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---
import riak
client = riak.RiakClient(protocol='pbc',
nodes=[{'host'
** SORRY, WAS SEND BEFORE I FINISHED **
Hi there,
I was testing 2i via PBC on Python and I found a wrong behaviour, this is
my code:
---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---
import riak
client = riak.
Alex,
No, it will only randomize the node when *opening* a connection. After
that, it just uses what is first available in the pool.
We have an outstanding plan to support auto-configuring clients, but that
work did not make it into the 2.0 cycle.
On Wed, Jun 25, 2014 at 7:18 AM, Alex De la ros
Hi Sean,
Thank you very much for your answer. So although I put 5 nodes in the
connection string, only 1 would be use for the overall process (PUT, PUT,
PUT, GET, etc...) until the end of the execution.
My second question was, if I have 5 nodes initially and i put them on my
connection string, an
In the process of developing the Python client for 2.0 features, we're
running into issues with Python 2.6.x (specifically related to pyOpenSSL
and its dependencies). Is anyone out there using Python 2.6 in production
still and wanting to use the Riak client?
--
Sean Cribbs
Software Engineer
Bas
Hello,
I'm using recent versions of Riak on CentOS 6.5 and I ran into some issues
which are similar to these ones reported on Debian:
https://github.com/basho/riak_cs/issues/718
In my case, instead of having problems during startup, I get problems during
shutdown, because for some reason riak
Another issue I just noticed. The RPMs for all the services apparently don't
stop them, before replacing them. I'm not sure if it's intentional, but I'm
worried if it might cause code or data corruption in some cases.
Matthew.
On Wed, Jun 25, 2014 at 05:45:46PM -0700, Matthew Hall wrote:
> Hell
I'm an unfortunate one kind of stuck with 2.6... as well as every other
RHEL6 user out there. I say that tongue and cheek because I understand
that Basho has limited resources and needs to juggle them appropriately.
warm regards,
Bryce
On 06/25/2014 12:09 PM, Sean Cribbs wrote:
In the process
