Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 11 Apr 2017 20:14:41 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12999039.1471904686000.259539.1491941681850@Atlassian.JIRA>
In-Reply-To: <JIRA.12999039.1471904686000@Atlassian.JIRA>
References: <JIRA.12999039.1471904686000@Atlassian.JIRA> <JIRA.12999039.1471904686333@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-16469) Several log
 refactoring/improvement suggestions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 11 Apr 2017 20:14:47 -0000


    [ https://issues.apache.org/jira/browse/HBASE-16469?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D159=
64898#comment-15964898 ]=20

Sean Busbey commented on HBASE-16469:
-------------------------------------

Pushed to master and branch-1. Thanks for the contribution [~chenfsd]!

One thing for next time, please leave patches attached to the issue and jus=
t increment the patch number as you update things (e.g. HBASE-16469.master.=
002.patch, etc). It makes it much easier to both see how things have evolve=
d and figure out if earlier feedback is still relevant.

> Several log refactoring/improvement suggestions
> -----------------------------------------------
>
>                 Key: HBASE-16469
>                 URL: https://issues.apache.org/jira/browse/HBASE-16469
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>    Affects Versions: 1.2.5
>            Reporter: Nemo Chen
>            Assignee: Nemo Chen
>              Labels: easyfix, easytest
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16469.master.001.patch
>
>
> *method invocation replaced by variable*
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/C=
loseRegionHandler.java
> {code}String name =3D regionInfo.getRegionNameAsString();{code}
> {code}LOG.warn("Can't close region: was already closed during close(): " =
+
>             regionInfo.getRegionNameAsString()); {code}
> In the above two examples, the method invocations are assigned to the var=
iables before the logging code. These method invocations should be replaced=
 by variables in case of simplicity and readability
> ----
> *method invocation in return statement*
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.j=
ava
> {code}
> public String toString() {
>     return getRegionInfo().getRegionNameAsString();
>   }
> {code}
> {code}
> LOG.debug("Region " + getRegionInfo().getRegionNameAsString()
>           + " is not mergeable because it is closing or closed");
> {code}
> {code}
> LOG.debug("Region " + getRegionInfo().getRegionNameAsString()
>           + " is not mergeable because it has references");
> {code}
> {code}=20
> LOG.info("Running close preflush of " + getRegionInfo().getRegionNameAsSt=
ring());
> {code}
> In these above examples, the "getRegionInfo().getRegionNameAsString())" i=
s the return statement of method "toString" in the same class. They should =
be replaced with =E2=80=9Cthis=E2=80=9D   in case of simplicity and readabi=
lity.
> ----
> *check the logged variable if it is null*
> hbase-it/src/test/java/org/apache/hadoop/hbase/HBaseClusterManager.java
> {code}
> if ((sshUserName !=3D null && sshUserName.length() > 0) ||
>         (sshOptions !=3D null && sshOptions.length() > 0)) {
>       LOG.info("Running with SSH user [" + sshUserName + "] and options [=
" + sshOptions + "]");
>     }
> {code}
> hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManag=
er.java
> {code}
> if ((regionState =3D=3D null && latestState !=3D null)
>           || (regionState !=3D null && latestState =3D=3D null)
>           || (regionState !=3D null && latestState !=3D null
>             && latestState.getState() !=3D regionState.getState())) {
>         LOG.warn("Region state changed from " + regionState + " to "
>           + latestState + ", while acquiring lock");
>       }
> {code}
> In the above example, the logging variable could null at run time. It is =
a bad  practice to include null variables inside logs.
> ----
> *variable in byte printed directly*
> hbase-server/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedUpda=
ter.java
> {code}
> byte[] rowKey =3D dataGenerator.getDeterministicUniqueKey(rowKeyBase);
> {code}
> {code}
> LOG.error("Failed to update the row with key =3D [" + rowKey
>       + "], since we could not get the original row");
> {code}
> rowKey should be printed as Bytes.toString(rowKey).
> ----=20
> *object toString contain mi*
> The toString method returns getServerName(), so the "server.getServerName=
()" should be replaced with "server" in case of simplicity and readability.
> hbase-client/src/main/java/org/apache/hadoop/hbase/client/PreemptiveFastF=
ailInterceptor.java
> {code}
> LOG.info("Clearing out PFFE for server " + server.getServerName());
> return getServerName();
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)