[
https://issues.apache.org/jira/browse/ZOOKEEPER-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005895#comment-13005895
]
Hadoop QA commented on ZOOKEEPER-1012:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12473443/ZOOKEEPER-1012.patch
against trunk revision 1074995.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://hudson.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/183//console
This message is automatically generated.
> support distinct JVMFLAGS for zookeeper server in zkServer.sh and zookeeper
> client in zkCli.sh
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1012
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1012
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: Eugene Koontz
> Assignee: Eugene Koontz
> Priority: Trivial
> Attachments: ZOOKEEPER-1012.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> 1. Sometimes you might want to run zkServer.sh with different JVMFLAGS than
> for a client. Make zkServer.sh consult the SERVER_JVMFLAGS variable and, if
> it exists, add it to the beginning of the existing JVMFLAGS setting.
> 2. Sometimes you might want to run zkCli.sh with different JVMFLAGS than for
> a client. Make zkServer.sh consult the CLIENT_JVMFLAGS variable and, if it
> exists, add it to the beginning of the existing JVMFLAGS setting.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
