HADOOP-16700. Track response time separately in Server.Call to avoid negative RpcQueueTime values. Contributed by xuzq.
This commit is contained in:
parent
1415ad3800
commit
be77231452
|
@ -751,8 +751,8 @@ public abstract class Server {
|
|||
private volatile String detailedMetricsName = "";
|
||||
final int callId; // the client's call id
|
||||
final int retryCount; // the retry count of the call
|
||||
long timestampNanos; // time received when response is null
|
||||
// time served when response is not null
|
||||
long timestampNanos; // time the call was received
|
||||
long responseTimestampNanos; // time the call was served
|
||||
private AtomicInteger responseWaitCount = new AtomicInteger(1);
|
||||
final RPC.RpcKind rpcKind;
|
||||
final byte[] clientId;
|
||||
|
@ -789,6 +789,7 @@ public abstract class Server {
|
|||
this.callId = id;
|
||||
this.retryCount = retryCount;
|
||||
this.timestampNanos = Time.monotonicNowNanos();
|
||||
this.responseTimestampNanos = timestampNanos;
|
||||
this.rpcKind = kind;
|
||||
this.clientId = clientId;
|
||||
this.traceScope = traceScope;
|
||||
|
@ -1591,7 +1592,7 @@ public abstract class Server {
|
|||
Iterator<RpcCall> iter = responseQueue.listIterator(0);
|
||||
while (iter.hasNext()) {
|
||||
call = iter.next();
|
||||
if (now > call.timestampNanos + PURGE_INTERVAL_NANOS) {
|
||||
if (now > call.responseTimestampNanos + PURGE_INTERVAL_NANOS) {
|
||||
closeConnection(call.connection);
|
||||
break;
|
||||
}
|
||||
|
@ -1655,7 +1656,7 @@ public abstract class Server {
|
|||
|
||||
if (inHandler) {
|
||||
// set the serve time when the response has to be sent later
|
||||
call.timestampNanos = Time.monotonicNowNanos();
|
||||
call.responseTimestampNanos = Time.monotonicNowNanos();
|
||||
|
||||
incPending();
|
||||
try {
|
||||
|
|
Loading…
Reference in New Issue