Hi Dan, Thanks for the suggestion but it doesn't solve it. I found some errors from riak log files.
=ERROR REPORT==== 7-Dec-2010::16:11:06 === ** Node '[email protected].***' not responding ** ** Removing (timedout) connection ** That's the only errors exist in the log files. Please advise. - Abe On 7 December 2010 12:41, Dan Reverri <[email protected]> wrote: > Yes, please try increasing to 2048. > > Daniel Reverri > Developer Advocate > Basho Technologies, Inc. > [email protected] > > > On Mon, Dec 6, 2010 at 8:34 PM, Abeming Sf <[email protected]> wrote: > >> Hi Dan, >> >> There is no error messages in my riak log files during that node error >> occurred. Ulimit already set to 1024, should I increase to 2048? >> >> Thanks, >> Abe >> >> >> On 7 December 2010 12:12, Dan Reverri <[email protected]> wrote: >> >>> Hi Abeming, >>> >>> Are there any error messages in your riak log files? Also, you may want >>> to try bumping up ulimit. >>> >>> Thanks, >>> Dan >>> >>> Daniel Reverri >>> Developer Advocate >>> Basho Technologies, Inc. >>> [email protected] >>> >>> >>> On Mon, Dec 6, 2010 at 8:03 PM, Abeming Sf <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I often encounter {error,{could_not_reach_node,'[email protected].***'} >>>> when there are many concurrent connection being made to riak node. How >>>> should I avoid this problem?Should I increase the number of concurrent >>>> connection?how?I use riak with default configuration and ulimit -n set to >>>> 1024. Should I increase async threads in vm.args? >>>> >>>> Thanks in advance. >>>> >>>> - Abe >>>> >>>> _______________________________________________ >>>> 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
