Santhosh, Bitcask has crash-proof design and so, unlike Inno, it will not read the entire keyspace and try to correct it at startup time. It will simply load the existing hint files and then scan the files it doesn't have hints for to discover the extant keys. This takes milliseconds or less per partition; you will hardly notice it.
Sean Cribbs <[email protected]> Developer Advocate Basho Technologies, Inc. http://basho.com/ On Apr 1, 2011, at 2:49 AM, santhosh venkat wrote: > Hi , > I am trying to experiment with the recovery time of a riak node using > bitcask storage after a crash . > > I was able to find some information about that in this page (which is > for Innodb though) > > http://wiki.basho.com/Recovering-a-failed-node.html which is more > about Innodb . > > Upon Reading bitcask paper i found it uses hint file to constructs in > memory mapping , so it should not ideally take more than few mins to > reconstruct data after crash . Please throw some light on this . > > I got this thread dump when i tried the steps outlined in the above link. > > =INFO REPORT==== 1-Apr-2011::12:06:50 === > [{alarm_handler,{set,{{disk_almost_full,"/var/lib/mysql"},[]}}}] > =INFO REPORT==== 1-Apr-2011::12:06:50 === > [{alarm_handler,{set,{{disk_almost_full,"/var/lib/riak"},[]}}}]** Found 0 > name clashes in code paths > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.141.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.142.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.143.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.144.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.145.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.146.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.147.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_map) > host starting (<0.148.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) > host starting (<0.150.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) > host starting (<0.151.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) > host starting (<0.152.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) > host starting (<0.153.0>) > > =INFO REPORT==== 1-Apr-2011::12:06:51 === > Spidermonkey VM (thread stack: 16MB, max heap: 8MB, pool: riak_kv_js_reduce) > host starting (<0.154.0>) > > Please help . > > -- > Santhosh > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
