[
https://issues.apache.org/jira/browse/HBASE-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved HBASE-3795.
---------------------------------------
Resolution: Fixed
Assignee: Jean-Daniel Cryans
Release Note: The client will stop printing messages like "DEBUG
client.HConnectionManager$HConnectionImplementation: Cache hit for row..."
Hadoop Flags: [Reviewed]
Cleaned up and branch and trunk.
> Remove the "Cache hit for row" message
> --------------------------------------
>
> Key: HBASE-3795
> URL: https://issues.apache.org/jira/browse/HBASE-3795
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.2
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Trivial
> Fix For: 0.90.3
>
>
> I don't see any reason why we should keep this message:
> client.HConnectionManager$HConnectionImplementation: Cache hit for row
> <0003706355> in tableName TestTable: location server sv2borg176:60020,
> location region name
> TestTable,0003706355,1302908760305.7ac9fae7facc8a69330340f1c3977339.
> It happens only when we are looking for a region in the HCM cache and the row
> key we use is the start key of that region.
> I don't just find it useless, also it litters our thrift logs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
