Riak crashed and crashed again when recovering
Hi all,
I am testing Riak for my document base and i got a problem when i was
migrating documents from my previous
system to Riak.
I have two nodes and one bucket for the beginning.
There are more than 480 000 documents in the bucket and the documents
are html pages.
In the following you'll find all the files and informations after a node
was restarted.
After a while, riak crashed again for the two nodes I restarted ... :(
$ ls -lh /reiser/riak/dets/
total 49G
[...]
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:22
639406966332270026714112114313373821099470487552
-rw-r--r-- 1 riak riak 260K 2010-05-05 11:06
639406966332270026714112114313373821099470487552.TMP
-rw-r--r-- 1 riak riak 3,7M 2010-05-05 07:24
662242929415565384811044689824565743281594433536
-rw-r--r-- 1 riak riak 3,3M 2010-05-05 07:24
68507889249886074290797726533575766546371837952
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:27
685078892498860742907977265335757665463718379520
-rw-r--r-- 1 riak riak 2,8M 2010-05-05 07:24
707914855582156101004909840846949587645842325504
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:27
730750818665451459101842416358141509827966271488
-rw-r--r-- 1 riak riak 2,0M 2010-05-05 07:24
753586781748746817198774991869333432010090217472
-rw-r--r-- 1 riak riak 1,9G 2010-05-05 07:28
776422744832042175295707567380525354192214163456
-rw-r--r-- 1 riak riak 2,9M 2010-05-05 07:24
799258707915337533392640142891717276374338109440
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:28
822094670998632891489572718402909198556462055424
-rw-r--r-- 1 riak riak 3,4M 2010-05-05 07:24
844930634081928249586505293914101120738586001408
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:27
867766597165223607683437869425293042920709947392
-rw-r--r-- 1 riak riak 4,7M 2010-05-05 07:24
890602560248518965780370444936484965102833893376
-rw-r--r-- 1 riak riak 1,9G 2010-05-05 07:27
91343852333181432387730302044767688728495783936
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:27
913438523331814323877303020447676887284957839360
-rw-r--r-- 1 riak riak 5,3M 2010-05-05 07:24
936274486415109681974235595958868809467081785344
-rw-r--r-- 1 riak riak 2,0G 2010-05-05 07:27
959110449498405040071168171470060731649205731328
-rw-r--r-- 1 riak riak 2,9M 2010-05-05 07:24
981946412581700398168100746981252653831329677312
-rw-r--r-- 1 riak riak 140M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.273
-rw-r--r-- 1 riak riak 8,7M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.290
-rw-r--r-- 1 riak riak 9,1M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.307
-rw-r--r-- 1 riak riak 8,6M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.324
-rw-r--r-- 1 riak riak 8,9M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.341
-rw-r--r-- 1 riak riak 8,7M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.358
-rw-r--r-- 1 riak riak 9,0M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.375
-rw-r--r-- 1 riak riak 8,7M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.392
-rw-r--r-- 1 riak riak 8,7M 2010-05-05 11:08
fs_r...@10.0.0.40_5223_1273_50399_129540.409
-rw-r--r-- 1 riak riak 8,5M 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.426
-rw-r--r-- 1 riak riak 9,0M 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.443
-rw-r--r-- 1 riak riak 8,8M 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.460
-rw-r--r-- 1 riak riak 8,7M 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.477
-rw-r--r-- 1 riak riak 9,3M 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.494
-rw-r--r-- 1 riak riak 581K 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.495
-rw-r--r-- 1 riak riak 546K 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.496
-rw-r--r-- 1 riak riak 571K 2010-05-05 11:09
fs_r...@10.0.0.40_5223_1273_50399_129540.497
$ curl
http://10.0.0.40:8098/riak/mybucket/1714432724f7f975610be47146fec6c7e74bf4bbccdbeea5208ac6e3540e6f4b
500 Internal Server
ErrorInternal Server ErrorThe server
encountered an error while processing this
request:[{webmachine_decision_core,'-decision/1-lc$^1/1-1-',
[{error,
{error,
{case_clause,{error,timeout}},
[{riak_kv_wm_raw,content_types_provided,2},
{webmachine_resource,resource_call,3},
{webmachine_resource,do,3},
{webmachine_decision_core,resource_call,1},
{webmachine_decision_core,decision,1},
{webmachine_decision_core,handle_request,2},
{webmachine_mochiweb,loop,1},
{mochiweb_http,headers,5}]}}]},
{webmachine_decision_core,decision,1},
{webmachine_decision_core,handle_request,2},
{webmachine_mochiweb,loop,1},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]mochiweb+webmachine
web server
$ riak-admin status
1-minute stats for 'r...@10.0.0.40'
---
vnode gets : 0
vnode_puts : 0
vnode_gets_total : 0
vnode_puts_total : 0
node_ge
Re: Riak crashed and crashed again when recovering
I got other informations when I launched "riak console" on the both
nodes, as you can see here.
I hope this will be useful for you and then for me :)
10.0.0.40:$ riak console
[...]
=INFO REPORT 5-May-2010::13:04:48 ===
Starting handoff of partition
479555224749202520035584085735030365824602865664 to 'r...@10.0.0.41'
dets: file
"/reiser/riak/dets/639406966332270026714112114313373821099470487552" not
properly closed, repairing ...
=INFO REPORT 5-May-2010::13:05:48 ===
Dropping partition 479555224749202520035584085735030365824602865664
=INFO REPORT 5-May-2010::13:08:47 ===
alarm_handler: {set,{system_memory_high_watermark,[]}}
=INFO REPORT 5-May-2010::13:19:32 ===
"dets:open_file failed"
=ERROR REPORT 5-May-2010::13:19:32 ===
** Generic server riak_kv_vnode_master terminating
** Last message in was {'$gen_cast',
{start_vnode,
639406966332270026714112114313373821099470487552}}
** When Server state == {state,12307,[]}
** Reason for termination ==
** {{badmatch,
{error,
{{badmatch,
{error,
{no_more_space_on_file,
"/reiser/riak/dets/639406966332270026714112114313373821099470487552.TMP"}}},
[{riak_kv_vnode,init,1},
{gen_fsm,init_it,6},
{proc_lib,init_p_do_apply,3}]}}},
[{riak_kv_vnode_master,get_vnode,2},
{riak_kv_vnode_master,handle_cast,2},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]}
=INFO REPORT 5-May-2010::13:19:32 ===
Spidermonkey VM host stopping (<0.117.0>)
=INFO REPORT 5-May-2010::13:19:32 ===
Spidermonkey VM host stopping (<0.115.0>)
=INFO REPORT 5-May-2010::13:19:32 ===
Spidermonkey VM host stopping (<0.119.0>)
=INFO REPORT 5-May-2010::13:19:32 ===
Spidermonkey VM host stopping (<0.112.0>)
=INFO REPORT 5-May-2010::13:19:32 ===
Spidermonkey VM host stopping (<0.114.0>)
Erlang has closed
=INFO REPORT 5-May-2010::13:19:32 ===
alarm_handler: {clear,system_memory_high_watermark}
/usr/lib/riak/lib/os_mon-2.2.5/priv/bin/memsup: Erlang has closed.
==
10.0.0.41:$ riak console
[...]
=INFO REPORT 5-May-2010::13:03:41 ===
Spidermonkey VM host starting (<0.120.0>)
Eshell V5.7.5 (abort with ^G)
(r...@10.0.0.41)1> dets: file
"/reiser/riak/dets/616571003248974668617179538802181898917346541568" not
properly closed, repairing ...
=INFO REPORT 5-May-2010::13:04:48 ===
Receiving handoff data for partition
479555224749202520035584085735030365824602865664
=ERROR REPORT 5-May-2010::13:05:48 ===
** Generic server <0.189.0> terminating
** Last message in was {tcp,#Port<0.2936>,
[0|<<84,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0>>]}
** When Server state == {state,#Port<0.2936>,undefined,undefined,0}
** Reason for termination ==
** {timeout,{gen_server2,call,
[riak_kv_vnode_master,
{get_vnode,479555224749202520035584085735030365824602865664},
6]}}
=INFO REPORT 5-May-2010::13:06:41 ===
alarm_handler: {set,{system_memory_high_watermark,[]}}
=ERROR REPORT 5-May-2010::13:07:41 ===
webmachine error:
path="/riak/blog_content_temp/1714432724f7f975610be47146fec6c7e74bf4bbccdbeea5208ac6e3540e6f4b"
[{webmachine_decision_core,'-decision/1-lc$^1/1-1-',
[{error,
{error,
{case_clause,{error,timeout}},
[{riak_kv_wm_raw,content_types_provided,2},
{webmachine_resource,resource_call,3},
{webmachine_resource,do,3},
{webmachine_decision_core,resource_call,1},
{webmachine_decision_core,decision,1},
{webmachine_decision_core,handle_request,2},
{webmachine_mochiweb,loop,1},
{mochiweb_http,headers,5}]}}]},
{webmachine_decision_core,decision,1},
{webmachine_decision_core,handle_request,2},
{webmachine_mochiweb,loop,1},
{mochiweb_http,headers,5},
{proc_lib,init_p_do_apply,3}]
=INFO REPORT 5-May-2010::13:16:54 ===
"dets:open_file failed"
=ERROR REPORT 5-May-2010::13:16:54 ===
** Generic server riak_kv_vnode_master terminating
** Last message in was {'$gen_cast',
{start_vnode,
616571003248974668617179538802181898917346541568}}
** When Server state == {state,12307,[]}
** Reason for termination ==
** {{badmatch,
{error,
{{badmatch,
{error,
{no_more_space_on_file,
"/reiser/riak/dets/616571003248974668617179538802181898917346541568.TMP"}}},
[{riak_kv_vnode,init,1},
{gen_fsm,init_it,6},
{proc_lib,init_p_do_apply,3}]}}},
[{riak_kv_vnode_master,get_vnode,2},
{riak_kv_vnode_master,handle_cast,2},
{gen_server,handle_msg,5},
Re: Riak crashed and crashed again when recovering
Germain,
It looks like you're filling up the dets tables -- which have a 2GB limit per
file, although Riak uses multiple files, one per vnode. Have you tried the
innostore backend? Also if you continue to use dets, try increasing the number
of partitions, which will make more, smaller files.
Sean Cribbs
Developer Advocate
Basho Technologies, Inc.
http://basho.com/
On May 5, 2010, at 7:55 AM, Germain Maurice wrote:
> I got other informations when I launched "riak console" on the both nodes, as
> you can see here.
> I hope this will be useful for you and then for me :)
>
> 10.0.0.40:$ riak console
> [...]
> =INFO REPORT 5-May-2010::13:04:48 ===
> Starting handoff of partition
> 479555224749202520035584085735030365824602865664 to 'r...@10.0.0.41'
> dets: file
> "/reiser/riak/dets/639406966332270026714112114313373821099470487552" not
> properly closed, repairing ...
>
> =INFO REPORT 5-May-2010::13:05:48 ===
> Dropping partition 479555224749202520035584085735030365824602865664
>
> =INFO REPORT 5-May-2010::13:08:47 ===
>alarm_handler: {set,{system_memory_high_watermark,[]}}
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> "dets:open_file failed"
>
> =ERROR REPORT 5-May-2010::13:19:32 ===
> ** Generic server riak_kv_vnode_master terminating
> ** Last message in was {'$gen_cast',
> {start_vnode,
>
> 639406966332270026714112114313373821099470487552}}
> ** When Server state == {state,12307,[]}
> ** Reason for termination ==
> ** {{badmatch,
>{error,
>{{badmatch,
> {error,
> {no_more_space_on_file,
>
> "/reiser/riak/dets/639406966332270026714112114313373821099470487552.TMP"}}},
> [{riak_kv_vnode,init,1},
> {gen_fsm,init_it,6},
> {proc_lib,init_p_do_apply,3}]}}},
>[{riak_kv_vnode_master,get_vnode,2},
> {riak_kv_vnode_master,handle_cast,2},
> {gen_server,handle_msg,5},
> {proc_lib,init_p_do_apply,3}]}
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> Spidermonkey VM host stopping (<0.117.0>)
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> Spidermonkey VM host stopping (<0.115.0>)
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> Spidermonkey VM host stopping (<0.119.0>)
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> Spidermonkey VM host stopping (<0.112.0>)
>
> =INFO REPORT 5-May-2010::13:19:32 ===
> Spidermonkey VM host stopping (<0.114.0>)
> Erlang has closed
>
> =INFO REPORT 5-May-2010::13:19:32 ===
>alarm_handler: {clear,system_memory_high_watermark}
> /usr/lib/riak/lib/os_mon-2.2.5/priv/bin/memsup: Erlang has closed.
>
>
>
> ==
>
> 10.0.0.41:$ riak console
> [...]
> =INFO REPORT 5-May-2010::13:03:41 ===
> Spidermonkey VM host starting (<0.120.0>)
> Eshell V5.7.5 (abort with ^G)
> (r...@10.0.0.41)1> dets: file
> "/reiser/riak/dets/616571003248974668617179538802181898917346541568" not
> properly closed, repairing ...
>
> =INFO REPORT 5-May-2010::13:04:48 ===
> Receiving handoff data for partition
> 479555224749202520035584085735030365824602865664
>
> =ERROR REPORT 5-May-2010::13:05:48 ===
> ** Generic server <0.189.0> terminating
> ** Last message in was {tcp,#Port<0.2936>,
>[0|<<84,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0>>]}
> ** When Server state == {state,#Port<0.2936>,undefined,undefined,0}
> ** Reason for termination ==
> ** {timeout,{gen_server2,call,
> [riak_kv_vnode_master,
>
> {get_vnode,479555224749202520035584085735030365824602865664},
> 6]}}
>
> =INFO REPORT 5-May-2010::13:06:41 ===
>alarm_handler: {set,{system_memory_high_watermark,[]}}
>
> =ERROR REPORT 5-May-2010::13:07:41 ===
> webmachine error:
> path="/riak/blog_content_temp/1714432724f7f975610be47146fec6c7e74bf4bbccdbeea5208ac6e3540e6f4b"
> [{webmachine_decision_core,'-decision/1-lc$^1/1-1-',
> [{error,
> {error,
> {case_clause,{error,timeout}},
> [{riak_kv_wm_raw,content_types_provided,2},
> {webmachine_resource,resource_call,3},
> {webmachine_resource,do,3},
> {webmachine_decision_core,resource_call,1},
> {webmachine_decision_core,decision,1},
> {webmachine_decision_core,handle_request,2},
> {webmachine_mochiweb,loop,1},
> {mochiweb_http,headers,5}]}}]},
> {webmachine_decision_core,decision,1},
> {webmachine_decision_core,handle_request,2},
> {webmachine_mochiweb,loop,1},
> {mochiweb_http,headers,5},
> {proc_lib,init_p_do_apply,3}]
>
> =INFO REPORT 5-May-2010::13:16:54 ===
> "dets:open_file failed"
>
> =ERROR REPORT 5-May-2010::13:16:54 ===
> ** Generic server riak_kv_vnode_master terminating
> ** Last message in was {'$gen_cast',
> {start_v
Riak Recap for 5/4
Morning, Afternoon, and Evening - A few orphaned questions from IRC, a new PHP sample app, Riak.js talking to Kiwi, and pointer a new Wiki feature for today's recap. Enjoy - Mark -- Community Manager wiki.basho.com twitter.com/pharkmillups -- Riak Recap for 5/4 1) Q --- The docs state in quite a few places that if I leave riak_web_ip or riak_web_port undefined, the web interface will not start This is partially true, in that riak does not start at all… Am I doing something wrong, or are the docs misguiding me? (from Will| via IRC) A --- You're not doing anything wrong. This is a bug, and it will soon be squashed. Thanks for finding this! The ticket can be seen here -- > https://issues.basho.com/show_bug.cgi?id=143 2) Q --- when doc/basic-client.txt talks about $PATH_TO_RIAK what is it talking about? There is no ebin dir in the riak root... (from Will| via IRC) A --- We took another look and it turns out that we could have been more clear here. Docs will be updated ASAP to fix this issue. The best way to do this would be to export ERL_LIBS and point this ENV variable to the location of the riak libraries and not use the -pa flag. If you are using a self-compiled install of Riak your ERL_LIBS path will be the apps directory: export ERL_LIBS=~/riak_install/apps If you are using a precompiled version of Riak your ERL_LIBS would be the following: /usr/lib/riak/lib 3) Grant Schofield (aka bingledac aka schofield) put together a small PHP app that shows the basic usage of the Riak PHP library. You can find it here -- > http://github.com/schofield/riak_php_app (it's also linked under the Recommended Resources section on wiki.basho.com) 4) @freshtonic put some time against getting riak.js working with Kiwi check it out here --> http://github.com/freshtonic/riak-js/commit/96a4ec11a09d37dc426c57e34c9f6f0e5e4c8df4 5) Yesterday we launched the Riak Fast Track which is an addition to the wiki that we are quite excited about. It's intended to get new users up to speed on what Riak is all about and how it works. There is an blog post covering it here -- > http://blog.basho.com/2010/05/04/introducing-the-riak-fast-track/ (hint - you will want to read it because there is swag involved) The Fast Track can be found on the wiki here: https://wiki.basho.com/display/RIAK/The+Riak+Fast+Track ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Hello, Bitcask!
Riak Users,
You might have noticed that we released a new local key/value store
recently: http://blog.basho.com/2010/04/27/hello,-bitcask/
As of just now, it is available as a storage engine ("backend") in the
tip of the Riak repository.
You can use it like any other backend just by setting the
storage_backend application variable in the riak_kv application to
riak_kv_bitcask_backend (in your "app.config") on a fresh node so that
it will use Bitcask for storage.
There is a new application in app.config, "bitcask", for more detailed
configuration of bitcask behavior. Some of the variables you can set
in there are:
data_root: string (required) - the directory for bitcask to use for
storage and metadata
merge_strategy: {hours, N} - perform a data file merge every N hours
sync_strategy: how to manage syncing of data files being written. choices:
none (default)- let the O/S decide
o_sync - use the O_SYNC flag to sync each write
{seconds, N} - call bitcask:sync/1 every N seconds
A couple of things aren't done yet, including more proactive
generation of hintfiles, faster startup time, smarter merge
strategies, more extensive testing on more platforms, documentation on
usage, and more. We are not yet recommending this as a primary
production backend, but we expect to very soon. Your feedback is
welcomed.
-Justin
p.s. -- it's not slow.
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Hello, Bitcask!
Hi,
As many of you know from twitter/irc I've put together a bare bones PHP client
for Bitcask:
http://github.com/videlalvaro/phpcask
If some guys/gals here think that this project might be helpful for someone
please let me know, so I can spend some more time on it.
To name an example where I can improve it is that now is just a PHP Class
wrapper around the bitcask API, with no error handling at all. Thinks like that
can be improved quite easily.
Regards and congratz to Basho for the good work.
Alvaro
On May 5, 2010, at 11:46 PM, Justin Sheehy wrote:
> Riak Users,
>
> You might have noticed that we released a new local key/value store
> recently: http://blog.basho.com/2010/04/27/hello,-bitcask/
>
> As of just now, it is available as a storage engine ("backend") in the
> tip of the Riak repository.
>
> You can use it like any other backend just by setting the
> storage_backend application variable in the riak_kv application to
> riak_kv_bitcask_backend (in your "app.config") on a fresh node so that
> it will use Bitcask for storage.
>
> There is a new application in app.config, "bitcask", for more detailed
> configuration of bitcask behavior. Some of the variables you can set
> in there are:
>
> data_root: string (required) - the directory for bitcask to use for
> storage and metadata
>
> merge_strategy: {hours, N} - perform a data file merge every N hours
>
> sync_strategy: how to manage syncing of data files being written. choices:
> none (default)- let the O/S decide
> o_sync - use the O_SYNC flag to sync each write
> {seconds, N} - call bitcask:sync/1 every N seconds
>
> A couple of things aren't done yet, including more proactive
> generation of hintfiles, faster startup time, smarter merge
> strategies, more extensive testing on more platforms, documentation on
> usage, and more. We are not yet recommending this as a primary
> production backend, but we expect to very soon. Your feedback is
> welcomed.
>
> -Justin
>
> p.s. -- it's not slow.
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Hello, Bitcask!
Great news! I am planning to try it out soon in development.
2010/5/5 Justin Sheehy :
> Riak Users,
>
> You might have noticed that we released a new local key/value store
> recently: http://blog.basho.com/2010/04/27/hello,-bitcask/
>
> As of just now, it is available as a storage engine ("backend") in the
> tip of the Riak repository.
>
> You can use it like any other backend just by setting the
> storage_backend application variable in the riak_kv application to
> riak_kv_bitcask_backend (in your "app.config") on a fresh node so that
> it will use Bitcask for storage.
>
> There is a new application in app.config, "bitcask", for more detailed
> configuration of bitcask behavior. Some of the variables you can set
> in there are:
>
> data_root: string (required) - the directory for bitcask to use for
> storage and metadata
>
> merge_strategy: {hours, N} - perform a data file merge every N hours
>
> sync_strategy: how to manage syncing of data files being written. choices:
> none (default) - let the O/S decide
> o_sync - use the O_SYNC flag to sync each write
> {seconds, N} - call bitcask:sync/1 every N seconds
>
> A couple of things aren't done yet, including more proactive
> generation of hintfiles, faster startup time, smarter merge
> strategies, more extensive testing on more platforms, documentation on
> usage, and more. We are not yet recommending this as a primary
> production backend, but we expect to very soon. Your feedback is
> welcomed.
>
> -Justin
>
> p.s. -- it's not slow.
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Riak crashed and crashed again when recovering
Sean, I apologize if this is readily available in the docs, faq, etc. (I obviously missed if it is). When a cluster is repartitioned, e.g. as a result of adding or removing vnodes, is one backend preferable to another? Does keeping node size down help/hurt in terms of performance, reliability, etc? Garrett On Wed, May 5, 2010 at 7:05 AM, Sean Cribbs wrote: > Germain, > > It looks like you're filling up the dets tables -- which have a 2GB limit per > file, although Riak uses multiple files, one per vnode. Have you tried the > innostore backend? Also if you continue to use dets, try increasing the > number of partitions, which will make more, smaller files. > > Sean Cribbs > Developer Advocate > Basho Technologies, Inc. > http://basho.com/ ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: Riak crashed and crashed again when recovering
We haven't often dealt with repartitioning clusters, which is why I recommended a complete backup and restore. The behavior when trying to dynamically change the partition quantity is undefined. Honestly I don't know how the backend would affect it at all. As always, however, adding nodes will increase performance and fault tolerance. If you intend to grow your cluster, a larger partition count will ease the transition and provide a more even spread. On Wednesday, May 5, 2010, Garrett Smith wrote: > Sean, > > I apologize if this is readily available in the docs, faq, etc. (I > obviously missed if it is). > > When a cluster is repartitioned, e.g. as a result of adding or > removing vnodes, is one backend preferable to another? Does keeping > node size down help/hurt in terms of performance, reliability, etc? > > Garrett > > On Wed, May 5, 2010 at 7:05 AM, Sean Cribbs wrote: >> Germain, >> >> It looks like you're filling up the dets tables -- which have a 2GB limit >> per file, although Riak uses multiple files, one per vnode. Have you tried >> the innostore backend? Also if you continue to use dets, try increasing the >> number of partitions, which will make more, smaller files. >> >> Sean Cribbs >> Developer Advocate >> Basho Technologies, Inc. >> http://basho.com/ > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
