[
https://issues.apache.org/jira/browse/BOOKKEEPER-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542785#comment-13542785
]
Hadoop QA commented on BOOKKEEPER-472:
--------------------------------------
Testing JIRA BOOKKEEPER-472
Patch
[BOOKKEEPER-472-3.patch|https://issues.apache.org/jira/secure/attachment/12563035/BOOKKEEPER-472-3.patch]
downloaded at Thu Jan 3 07:31:13 UTC 2013
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:red}-1{color} the patch contains 14 line(s) with trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
120
. {color:green}+1{color} the patch does adds/modifies 5 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
. {color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
. Tests run: 760
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/191/
> Provide an option to start Autorecovery along with Bookie Servers
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-472
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-472
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-472-1.patch, BOOKKEEPER-472-2.patch,
> BOOKKEEPER-472-3.patch, BOOKKEEPER-472.patch
>
>
> We can also have an option to start the Autorecovery along with Bookie
> servers.
> If some users are not having too much load on the servers, they can even
> start them along the Bookie servers. If they feel, Auditor would disturb
> Bookie performance, they can anyway start as separate process.
> In another case, deployment overhead will reduce a bit as Monitoring process
> need not monitor one more process in their lifcycles etc.
> Thoughts?
--
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: http://www.atlassian.com/software/jira
