[
https://issues.apache.org/jira/browse/HBASE-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642575#comment-13642575
]
stack commented on HBASE-8271:
------------------------------
[[email protected]] When I try to apply the patch to trunk:
{code}
durruti:trunk stack$ patch -p1 < HBASE-7817.patch.1
patching file bin/hbase-config.sh
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file bin/hbase-config.sh.rej
patching file bin/hbase-daemon.sh
Hunk #1 FAILED at 153.
1 out of 1 hunk FAILED -- saving rejects to file bin/hbase-daemon.sh.rej
patching file conf/hbase-env.sh
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file conf/hbase-env.sh.rej
{code}
... because it has already been applied.
Looks like it was applied here:
{code}
0 r1464736 | jyates | 2013-04-04 13:45:25 -0700 (Thu, 04 Apr 2013) | 1 line
1
2 HBASE-7817: Suggested JDWP debug options in hbase-env.sh are wrong (Vasu
Mariyala)
{code}
> Book updates for changes to GC options in shell scripts
> -------------------------------------------------------
>
> Key: HBASE-8271
> URL: https://issues.apache.org/jira/browse/HBASE-8271
> Project: HBase
> Issue Type: Improvement
> Components: documentation
> Reporter: Jesse Yates
> Priority: Minor
> Fix For: 0.94.8
>
> Attachments: HBASE-7817.patch
>
>
> http://hbase.apache.org/book/trouble.log.html is a bit out of date as the
> 'right' way to do GC logging is via the GC_OPTS, rather than going through
> the general HBASE_OPTS.
> Follow up to HBASE-7817
--
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
