Hey Stack, I think I have a patch somewhere that reduces that logging to TRACE level. It is not related to replicas, but for the patch https://issues.apache.org/jira/browse/HBASE-10357, we've made the Scan code paths for replicas and regular scans the same (that is why it is named ScannerCallableWithReplica) so that the code is a bit better organized.
Let me put that patch in jira. Enis On Mon, Sep 8, 2014 at 11:55 AM, Stack <[email protected]> wrote: > I'm doing some basic testing of branch-1 to see if can catch any ugly stuff > before we cut our first 0.99. > > Can someone help me w/ following debug-level messages: > > 2014-09-08 11:24:13,739 DEBUG [TestClient-43] > client.ScannerCallableWithReplicas: Setting current scanner as -1 > associated with 0 > 2014-09-08 11:24:13,739 DEBUG [TestClient-76] > client.ScannerCallableWithReplicas: Setting current scanner as -1 > associated with 0 > 2014-09-08 11:24:13,739 DEBUG [TestClient-93] > client.ScannerCallableWithReplicas: Setting current scanner as -1 > associated with 0 > 2014-09-08 11:24:13,748 DEBUG [TestClient-10] > client.ScannerCallableWithReplicas: Setting current scanner as -1 > associated with 0 > > The -1 is the scanner id it seems but I'd think a -1 id is 'bad'... least > that is what I think when I see it. I'm at DEBUG level so not so bad but > there is a lot of replica logging going on. Should this logging be > switched? i.e. only log when we are doing replicas? Is there a config. to > check? > > Thanks, > St.Ack >
