Hi,
I upgraded Riak from 1.4.12 to 2.0.2. The tomcat application doesn't
work correctly...
We have 2 issues:
- We are using mapreduce with javascript. The meta data is saved in
Riak with low case, for example: x-test-lala, but the javascript
object that the mapreduce function returns is in
Hi Brian,
Thank you for your prompt reply, I thought that might be the case (and I agree,
the way generics ended up being implemented is sadistic)
I went with B) already but I wanted to make sure this is recorded.
I filed this here for reference:
I’m doing a fairly “by the book” clobber update (store and fetch below work
fine) on an entity using the Java client. I’m seeing an error that happens at
type-inference time within the Riak Java client. I’m pasting below the exact
test that I’m using to generate this, as well as the stacktrace.
?
https://github.com/LMAX-Exchange/disruptor/wiki/Introduction
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20150114/8fb93117/attachment-0001.html
Hi,
I have a cluster of 6 machines and wanted to check them using riak
control. I tried to enabled it on node-01 (riak.conf = riak_control =
on), restart riak on that node. But nothing appears on port 8069...
where else can i configure these parameters? Or check what is wrong?
Thanx
Bruno
Is it possible to mimic most or all of Disruptor's behaviour with Riak?
https://github.com/LMAX-Exchange/disruptor/wiki/Introduction
___
riak-users mailing list
riak-users@lists.basho.com
On Wed, Jan 14, 2015 at 4:00 PM, Bruno René Santos
bruno-r-san...@telecom.pt wrote:
Hi,
I have a cluster of 6 machines and wanted to check them using riak control.
I tried to enabled it on node-01 (riak.conf = riak_control = on), restart
riak on that node. But nothing appears on port 8069...
Just a thought, but have you tried to replicate the problem when using
haproxy (with the example configs provided on basho's site)?
That might let you discover if the problem really IS with Apache, or
if it's something to do with your Riak config instead.
On 15 January 2015 at 11:05, Fred Grim
I'm going to take a punt that you're using the wrong domain name.
Eg. you've told riak to use, say, s3.internal as the base, but you're
actually sending queries to s3.example.com (or if you are using
default settings on some tools, s3.amazonaws.com)
If you're using a reverse proxy in front, check
