I also failed to ask two basic questions:
1. did this failure start after your upgrade to 2.1.3, or happen prior to
upgrade also?
2. did you use a Basho package for Centos 7, or did you build from source code?
Matthew
> On Dec 31, 2015, at 6:06 AM, Antti Kuusela wrote:
>
> Hi Luke,
>
> W
Hi Paulo,
Why are you considering this? Are you running into issues or
limitations using the current Erlang client?
--
Luke Bakken
Engineer
lbak...@basho.com
On Thu, Dec 31, 2015 at 12:47 AM, Paulo Almeida
wrote:
>
> Hi,
>
> A poolboy or other connection pool based solution still means 1 open t
Would you forward the riak.conf for your setup and paste the first 30 lines
from a LOG file from any leveldb vnode a server that has experienced the crash.
Example lines from a LOG file are:
2015/12/27-11:56:53.559717 7f02a47b0700Version: 2.0.10
2015/12/27-11:56:53.55985
Hi Luke,
We erased the btrfs file system, replaced it with xfs on lvm with
thinly-provisioned volumes and continued testing with a new database
from scratch. The same problem continues, though. From /var/log/messages:
Dec 31 03:35:31 storage5 riak[66419]: Starting up
Dec 31 03:35:45 storage5
Hi Paulo,
You’ll need more than client work. If you’re interested in exploring the server
side code riak_api (https://github.com/basho/riak_api) is probably where you
want to look.
I’m happy to help/advise on this if you want to get stuck in :D
Cheers
Russell
On 31 Dec 2015, at 08:47, Paulo A
Hi,
A poolboy or other connection pool based solution still means 1 open tcp
connection per worker. I'm exploring the option of having a single TCP
connection (actually 1 for each Riak node) and then multiplex concurrent
requests to a DB node in a single TCP connection (think HTTP/2 TCP
connection
Hi Paulo,
Riak-erlang-client does not support multiplexing. In fact I believe there would
be some work needed on the riak protocol buffers server code to support
multiplexing.
Riak-erlang-clinet does not use a pool (like poolboy) either.
Cheers
Russell
On 31 Dec 2015, at 01:59, Bryan Hunt wr
