accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1357) Make debugging MiniAccumuloCluster easier
Date Thu, 09 May 2013 16:41:16 GMT


Keith Turner commented on ACCUMULO-1357:

[~sonixbp]. I committed patch #2.  I made some subsequent change in commit 1480705.  Can you
take a look at those?  I noticed the methods relating to getting bytes were not public.  When
changing them to public, I thought that making them return a long would be more consistent
with the setters than returning a string.  I also change them names of the memory related
getters and setters to make them more consistent.

I was thinking the setDebug() and isDebug() names should be named somethng different.  Something
more specific that distiguishes from other types of debugging, like log4j debug level.   Maybe
something like setJDWPEnabled() and isJDWPEnabled(), those are much more precise, but kinda

> Make debugging MiniAccumuloCluster easier
> -----------------------------------------
>                 Key: ACCUMULO-1357
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Corey J. Nolet
>             Fix For: 1.6.0
>         Attachments: ACCUMULO-1357.1.patch, ACCUMULO-1357.2.patch
> When a problem occurs with MiniAccumuloCluster it can be difficult to debug.  Something
that may make this easier.
>  * The ability to easily access log files. (maybe have a method users could call to copy
log files to a target dir).
>  * Starting Accumulo server processes with remote JVM debugging enabled.  (this could
be a statup option, could have method users could call to get the debug ports)
> It would be nice if a unit test fails in a maven run if the MiniAcc logs files would
end up the target dir that contains info about test failures.  Make it as easy as possible
to do this from junit test.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message