hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-701) Showing bytes in log when should be String
Date Mon, 23 Jun 2008 15:18:45 GMT

     [ https://issues.apache.org/jira/browse/HBASE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-701.
-------------------------

    Resolution: Fixed
      Assignee: stack

Committed.

> Showing bytes in log when should be String
> ------------------------------------------
>
>                 Key: HBASE-701
>                 URL: https://issues.apache.org/jira/browse/HBASE-701
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.2.0
>
>
> From Michaela Buergle up on the hbase-dev:
> While searching around in my logfiles, I noted some bytes ending up
> there instead of a human readable version of getRegionName():
> {code}
> master.ChangeTableState l.129 [adding region " + i.getRegionName() + "
> to kill list"]
> master.ProcessRegionClose.toString() l.54 ["ProcessRegionClose of " +
> this.regionInfo.getRegionName()]
> master.ProcessRegionClose.process() l.63 ["region closed: " +
> regionInfo.getRegionName())]
> master.ColumnOperation.updateRegionInfo() l.57 ["updated columns in row:
> " + i.getRegionName()]
> master.ChangeTableState.postProcessMeta() l.87 ["updating columns in
> row: " + i.getRegionName()], l.96 ["updated columns in row: " +
> i.getRegionName()]
> master.RegionManager.unassignSomeRegions() l.426 ["Going to close region
> " + currentRegion.getRegionName()]
> micha
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message