hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10293) Master and RS GC logs can conflict when run on same host
Date Wed, 08 Jan 2014 19:02:53 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865755#comment-13865755
] 

Enis Soztutar commented on HBASE-10293:
---------------------------------------

I guess we can do a similar thing to the log4j logs, where we will append the username and
daemon name to the gc log. 

> Master and RS GC logs can conflict when run on same host
> --------------------------------------------------------
>
>                 Key: HBASE-10293
>                 URL: https://issues.apache.org/jira/browse/HBASE-10293
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.96.1.1
>            Reporter: Nick Dimiduk
>
> My issue manifests when I uncomment the line {{export SERVER_GC_OPTS=...}} in hbase-env.sh
and start HBase. It's a single node in distributed mode, so both a Master and RegionServer
are started on that host. Both start commands are run in the same minute, so only one gc.log-`date`
file is created. `lsof` indicates two processes are writing to that file and the output of
`ps` confirms they both received the same {{-Xloggc:/grid/0/var/log/hbase/gc.log-201401071515}}
argument.
> Presumably, the same will happen for folks running the thrift and rest gateways on the
same box (any java process itemized in the server_cmds array in bin/hbase).
> Related (the reason I discovered this issue in the first place), stopping the master
process results in its gc.log being truncated.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message