accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2351) Master memory leak
Date Thu, 13 Feb 2014 20:47:21 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines resolved ACCUMULO-2351.
----------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.6.0
                   1.5.1
         Assignee: John Vines

Description is mentioned in the ticket. 4 bytes sent to the master can easily bring it down.
Setting the MAX_BUFFER_SIZE in thrift limits how big the allocation can be. I will be opening
up a task to revisit these in a more thorough manner, but 2360 is a good interim fix.

> Master memory leak
> ------------------
>
>                 Key: ACCUMULO-2351
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2351
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.5.0
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.5.1, 1.6.0
>
>
> This has been seen a few times. Master with Xms1g and Xmx4g, which should be more than
enough. Most recent case, with 44 nodes, 1.74k tablets, and 22 tables including !METADATA.
There are NO conspicuous messages in the master (just DefaultLoadBalancer messages for each
table). Possible exception for an error of "received invalid frame size of -..., are you using
TTframeProtocol (can't remember exact message). But then the master out file has a message
about OoM received, kill -9. 
> I don't really know how to get more information out of it for when this does occur again.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message