[ 
https://issues.apache.org/jira/browse/ACCUMULO-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223749#comment-13223749
 ] 

Keith Turner commented on ACCUMULO-449:
---------------------------------------

Originally the logger had a max of 128m of heap.  I think I copied 
accumulo-env.sh.512MBBstandalone-native-example.  I upped the logger heap to 
512m max.
                
> Failed log copy is not restarted
> --------------------------------
>
>                 Key: ACCUMULO-449
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-449
>             Project: Accumulo
>          Issue Type: Bug
>          Components: logger, master
>            Reporter: Keith Turner
>            Assignee: Eric Newton
>              Labels: 14_qa_bug
>             Fix For: 1.4.0
>
>
> I shut a single node instance down uncleanly.  When I restarted it the logger 
> did not have enough memory to preform the log sort, it got an OOME and died.  
> I edited accumulo-env.sh and gave the logger process more memory.  I 
> restarted the logger process.  However, the log recovery never restarted.   
> The master was continually printing message like the following.
> {noformat}
> 06 17:07:16,609 [master.CoordinateRecoveryTask] DEBUG: Copying 
> 65c48045-88c1-48e4-93d3-4865a9a86050 from xxx.xxx.xxx.xxx:11224 (for 
> 1210.306000 seconds) 0.0
> {noformat}
> After 20m I restarted the master and then log recovery proceeded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to