Ah, I see now, got myself fooled. This was added maybe after we clones the RpcMetrics into HBaseRpcMetrics. So all we have to do is add it to be back up to parity (and then some).
On Wed, May 18, 2011 at 6:58 PM, Lars George <[email protected]> wrote: > I am not sure how though. I checked and they seem to be registered > correctly. Even if they are not set, JMX should show them. But nada, > zip, zero, zilch. > > Couldn't be bothered (yet) compiling a LOG.debug() version of > hadoop-core to check where they went up shits creek. > > On Wed, May 18, 2011 at 4:42 PM, Stack <[email protected]> wrote: >> MIA I'd say. They look useful. >> St.Ack >> >> On Wed, May 18, 2011 at 6:34 AM, Lars George <[email protected]> wrote: >>> Hi, >>> >>> Did anyone else notice that the RPCMetrics are supposed to export four >>> internal values: >>> >>> public MetricsTimeVaryingRate rpcQueueTime = >>> new MetricsTimeVaryingRate("RpcQueueTime", registry); >>> public MetricsTimeVaryingRate rpcProcessingTime = >>> new MetricsTimeVaryingRate("RpcProcessingTime", registry); >>> public MetricsIntValue numOpenConnections = >>> new MetricsIntValue("NumOpenConnections", registry); >>> public MetricsIntValue callQueueLen = >>> new MetricsIntValue("callQueueLen", registry); >>> >>> The first two show just fine on JMX and Context based output, but the >>> latter two don't. Nowhere. >>> >>> Anyone having a clue where they went MIA? >>> >>> Lars >>> >> >
