You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (Created) (JIRA)" <ji...@apache.org> on 2012/02/21 21:58:49 UTC

[jira] [Created] (ACCUMULO-423) Improve logger monitor page info

Improve logger monitor page info
--------------------------------

                 Key: ACCUMULO-423
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-423
             Project: Accumulo
          Issue Type: Improvement
            Reporter: John Vines
             Fix For: 1.5.0


Currently the loggers page just lists loggers. At the very least we should list the amount of disk used vs. available, or something along those lines so we can easily see loggers that are about to fail. We could include other information as well, but this info was what spurred this ticket.

--
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

        

Re: [jira] [Created] (ACCUMULO-423) Improve logger monitor page info

Posted by Keith Turner <ke...@deenlo.com>.
Yesterday we were discussing the issue of the accumulo garbage
collector not running.  The monitor page goes red, but users still do
not notice.  Eventually things fill up.  We were thinking Accumulo
should take more severe action when the GC is not running for long
periods, like go read only inorder to get the users attention before
the problem turns into a crisis.

On Wed, Feb 22, 2012 at 11:58 AM, Aaron Cordova <aa...@cordovas.org> wrote:
> I noticed a previous ticket saying that loggers should become readonly when they run out of space. It'd be awesome if Accumulo did this in general - i.e. if there is no more space in HDFS Accumulo stops trying merging compactions and goes into read only mode. Minor compactions could even fail as long as loggers have the data.
>
> On Feb 21, 2012, at 3:58 PM, John Vines (Created) (JIRA) wrote:
>
>> Improve logger monitor page info
>> --------------------------------
>>
>>                 Key: ACCUMULO-423
>>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-423
>>             Project: Accumulo
>>          Issue Type: Improvement
>>            Reporter: John Vines
>>             Fix For: 1.5.0
>>
>>
>> Currently the loggers page just lists loggers. At the very least we should list the amount of disk used vs. available, or something along those lines so we can easily see loggers that are about to fail. We could include other information as well, but this info was what spurred this ticket.
>>
>> --
>> 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
>>
>>
>

Re: [jira] [Created] (ACCUMULO-423) Improve logger monitor page info

Posted by Aaron Cordova <aa...@cordovas.org>.
I noticed a previous ticket saying that loggers should become readonly when they run out of space. It'd be awesome if Accumulo did this in general - i.e. if there is no more space in HDFS Accumulo stops trying merging compactions and goes into read only mode. Minor compactions could even fail as long as loggers have the data.

On Feb 21, 2012, at 3:58 PM, John Vines (Created) (JIRA) wrote:

> Improve logger monitor page info
> --------------------------------
> 
>                 Key: ACCUMULO-423
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-423
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>             Fix For: 1.5.0
> 
> 
> Currently the loggers page just lists loggers. At the very least we should list the amount of disk used vs. available, or something along those lines so we can easily see loggers that are about to fail. We could include other information as well, but this info was what spurred this ticket.
> 
> --
> 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
> 
>