You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "zhuyaogai (Jira)" <ji...@apache.org> on 2022/08/03 03:09:00 UTC
[jira] [Updated] (HBASE-27268) In trace log mode, the client does not print callId/startTime and the server does not print receiveTime
[ https://issues.apache.org/jira/browse/HBASE-27268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhuyaogai updated HBASE-27268:
------------------------------
Description:
Question:
In some scenarios in the production environment, users find that the request latancy is high on the client side, but it is not high on the server side (all through the internal monitor system). In this inconsistent scenario, we want to know if there is a problem with the client or the current network. Therefore, we want to know the time when the server receives the request. However, in Trace mode, no relevant information is printed.
A possible solution is that the client prints
was:
Question:
In some scenarios in the production environment, users find that the request latancy is high on the client side, but it is not high on the server side (all through the internal monitor system). In this inconsistent scenario, we want to know if there is a problem with the client or the current network. Therefore, we want to know the time when the server receives the request. However, in Trace mode, no relevant information is printed.
A possible solution is that the
> In trace log mode, the client does not print callId/startTime and the server does not print receiveTime
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-27268
> URL: https://issues.apache.org/jira/browse/HBASE-27268
> Project: HBase
> Issue Type: Improvement
> Components: tracing
> Affects Versions: 2.5.0, 3.0.0-alpha-3
> Reporter: zhuyaogai
> Assignee: zhuyaogai
> Priority: Minor
>
> Question:
> In some scenarios in the production environment, users find that the request latancy is high on the client side, but it is not high on the server side (all through the internal monitor system). In this inconsistent scenario, we want to know if there is a problem with the client or the current network. Therefore, we want to know the time when the server receives the request. However, in Trace mode, no relevant information is printed.
>
> A possible solution is that the client prints
--
This message was sent by Atlassian Jira
(v8.20.10#820010)