Cross-Compile Riak for Embedded Device

2017-02-09 Thread Darshan Shah
Hi, I am new to Riak and I would like to know steps to cross compile Riak for Embedded Unit. >From website I found steps to compile with source code but I need steps to cross compile. It will be appreciated if you can give steps or links from which I can get idea to cross compile. Thanking in adv

Re: Riak mapreduce error

2017-02-09 Thread raghuveer sj
Hi Magnus, Previously i had used developer branch as master build was failing. Now with the latest changes i see : 10> riakc_pb_socket:mapred_bucket(Riak, <<"training">>, [{map, {qfun, ReFun}, Re, true}]). {error,<<"{\"phase\":0,\"error\":\"{badfun,#Fun}\",\"input\":\"{ok,{r_object,<<\\\" trainin

riak-cs fails to start after reimporting Docker container

2017-02-09 Thread Jean-Marc Le Roux
Hello, here is the original github issue : https://github.com/basho/riak_cs/issues/1329 I'm using riak-cs 2.1.1-1.el6 with stanchion 1.5.0-1.el6 on CentOS 6.8 in a Docker container. To make the data persistent, the following directories are mounted from outside the container : - /var/log

Re: cluster clear without stopping node

2017-02-09 Thread Magnus Kessler
On 8 February 2017 at 21:33, Daniel Miller wrote: > According to the docs > > “Running [riak-admin cluster clear] will also stop the current node in > addition to clearing any staged changes. > > Is there a way to clear the current

Re: cluster clear without stopping node

2017-02-09 Thread Daniel Miller
Hi Magnus, Thanks, this is great news! I was worried that clearing a planned node removal would stop the node from which I was issuing the clear command, which would be bad. Sounds like I have nothing to worry about in that case. On running cluster plan multiple times to generate a new plan: this

Re: riak-cs fails to start after reimporting Docker container

2017-02-09 Thread Luke Bakken
Hi Jean-Marc - Can you provide a complete archive of the log directory? I wonder if another file might have more information. -- Luke Bakken Engineer lbak...@basho.com On Thu, Feb 9, 2017 at 1:58 AM, Jean-Marc Le Roux wrote: > > Hello, > > here is the original github issue : > > https://github.

Re: cluster clear without stopping node

2017-02-09 Thread Magnus Kessler
On 9 February 2017 at 14:46, Daniel Miller wrote: > Hi Magnus, > > Thanks, this is great news! I was worried that clearing a planned node > removal would stop the node from which I was issuing the clear command, > which would be bad. Sounds like I have nothing to worry about in that case. > The b

Re: Cross-Compile Riak for Embedded Device

2017-02-09 Thread Luke Bakken
Hi Darshan, Riak's memory requirements don't lend it to use on embedded devices. Which device are you targeting? -- Luke Bakken Engineer lbak...@basho.com On Wed, Feb 8, 2017 at 5:49 AM, Darshan Shah wrote: > Hi, > > I am new to Riak and I would like to know steps to cross compile Riak for > Em

Re: Object not found after successful PUT on S3 API

2017-02-09 Thread Luke Bakken
Hi Daniel - I don't have any ideas at this point. Has this scenario happened again? -- Luke Bakken Engineer lbak...@basho.com On Wed, Jan 25, 2017 at 2:11 PM, Daniel Miller wrote: > Thanks for the quick response, Luke. > > There is nothing unusual about the keys. The format is a name + UUID +

Re: [Basho Riak] Fail To Update Document Repeatly With Cluster of 5 Nodes

2017-02-09 Thread Alexander Sicular
Speaking of timings: ring_members : ['riak-node1@64.137.190.244','riak-node2@64.137.247.82', 'riak-node3@64.137.162.64','riak-node4@64.137.161.229', 'riak-node5@64.137.217.73'] Are these nodes in the same local area network? On Thu, Feb 9, 2017 at 12:49 PM, my hue wrote: > Dear Russel, > > I di

Re: [Basho Riak] Fail To Update Document Repeatly With Cluster of 5 Nodes

2017-02-09 Thread DeadZen
Why are they public? On Thu, Feb 9, 2017 at 3:11 PM, Alexander Sicular wrote: > Speaking of timings: > > ring_members : ['riak-node1@64.137.190.244','riak-node2@64.137.247.82', > 'riak-node3@64.137.162.64','riak-node4@64.137.161.229', > 'riak-node5@64.137.217.73'] > > Are these nodes in the same