On 6/13/2013 8:19 AM, Furkan KAMACI wrote:
17:16:56.560 [tion(localhost:9983)] DEBUG ClientCnxn - Got ping response
for sessionid: 0x13f3c94662c0026 after 0ms
17:16:59.897 [tion(localhost:9983)] DEBUG ClientCnxn - Got ping response
for sessionid: 0x13f3c94662c0026 after 0ms
17:17:03.232 [tion(localhost:9983)] DEBUG ClientCnxn - Got ping response
for sessionid: 0x13f3c94662c0026 after 0ms
it is too often. Is it usual?
This logging comes from Zookeeper -- google ClientCnxn to verify. It's
only pinging once every three seconds. That's not very often. It is
not happening every millisecond.
You really shouldn't run with all logs at DEBUG. It's a huge amount of
information, just logging it can cause performance issues, and it will
show you things like the above that might seem bad, but aren't.
INFO logging is as detailed as most people should ever need to go,
unless they are trying to modify the source code.
If you are trying to debug something in particular, you should leave the
default logging in the log4j config file at INFO or WARN, then turn up
the logging on specific Solr classes using the admin UI. If the
specific class you want to debug isn't in the UI, you can add any class
you want to the logging config file.
Thanks,
Shawn
