Yes, you can raise max_open_files as high as you have memory to cover.
The plan for Riak 2.0 is to make these settings automatic and dynamic. Then
the cache_size will automatically decline as max_open_files increases to cover
your dataset. Of course, there will be limits to prevent memory goin
On Sun, Jul 28, 2013 at 10:08 PM, Matthew Von-Maszewski
wrote:
>
> leveldb has two independent caches: file cache and data block cache. You
> have raised the data block cache from its default 8M to 256M per your
> earlier note. I would recommend the follow:
>
> {max_open_files, 50}, %%
Christian,
leveldb has two independent caches: file cache and data block cache. You have
raised the data block cache from its default 8M to 256M per your earlier note.
I would recommend the follow:
{max_open_files, 50}, %% 50 * 4Mbytes allocation for file cache
{cache_size, 10485760
On Thu, Jul 25, 2013 at 2:16 PM, Christian Rosnes <
christian.ros...@gmail.com> wrote:
> During a test I just performed on a small Riak 1.4 cluster setup on Azure,
> I started seeing the Riak errors messages listed below after about 10
> minutes.
>
> The simple test was performed using lastest Jm
YPE_015","pid":"6945","dst":{"sno":"10010","sNum":"4580","dTyp":"DTYPE_020","co":"MK","pFix":"389"},
"bInfo":{"price":39, "cur":"MKD", "iTxt&quo
? Have you tried doing the write and then a read directly
> after? Have you tried a read with curl?
>
>
>> In the error.log and crash.log files I can see:
>> --
>> [error] webmachine error:
>> path="/riak/elists/84kZEElqXqNCLZ_ZCQcRHpTbCD5c77AREvB_K3jGc
ad with curl?
> In the error.log and crash.log files I can see:
> --
> [error] webmachine error:
> path="/riak/elists/84kZEElqXqNCLZ_ZCQcRHpTbCD5c77AREvB_K3jGcm4"
>
> {error,{error,{badmatch,{error,closed}},[{webmachine_request,recv_unchunked_body,4},{webmachine_request,do_re
ng()).execute();
finished successfully and I found a relevant info in the application log.
However later I couldn't find this key in Riak.
In the error.log and crash.log files I can see:
--
[error] webmachine error:
path="/riak/elists/84kZEElqXqNCLZ_ZCQcRHpTbCD5c77AREvB_K3jGcm4&quo
still persisting for you?
-Ryan
[1]:
http://erldocs.com/R14B02/kernel/gen_tcp.html?i=1&search=gen_tcp:rec#recv/3
On Fri, Sep 23, 2011 at 2:07 AM, raghwani sohil wrote:
> Hi ,
>
> I am using php client and I am getting following error
>
> webmachine error: path="/riak/log/3586
Hi ,
I am using php client and I am getting following error
webmachine error: path="/riak/log/3586_232_2011_
09_17_21_30_25.html"
{error,{error,{badmatch,{error,closed}},
[{webmachine_request,recv_unchunked_body,4},
{webmachine_request,do_r
Hi ,
I am using php client and I am getting following error
webmachine error: path="/riak/log/3586_232_2011_09_17_21_30_25.html"
{error,{error,{badmatch,{error,closed}},
[{webmachine_request,recv_unchunked_body,4},
{webmachine_request,do_r
nd the entire document is
indexed under a single field name.)
Also, in 0.13, the raw extractor had a bug that caused it to always use a
field name of "value". I believe this is the source of the webmachine error
that you see. This is tracked here (
https://issues.basho.com/show_bug.cgi?id=
Hello Riak Users,
After a failed attempt to 'put' an object witk riakc_pb_socket api, into a
bucket enabled for indexing and the retrying the same operation with erlang
http
client I get the following error.
It seems to me that this error does not even suppose to appear here.
13 matches
Mail list logo
