[BOOKKEEPER-1090] Use LOG.isDebugEnabled() to avoid unexpected allocations

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.5.0
• Assignee: Matteo Merli
• Reporter: Matteo Merli
• Created: 01/Jun/17 21:05
• Updated: 22/Jun/17 00:11
• Resolved: 22/Jun/17 00:11

Description

Using LOG.debug(...) can lead to multiple unexpected memory allocation, even when the logger it's turned off.

For example, int and long parameter are boxed into Integer and Long objects and the var-arg parameters are using an Object[] to hold
them.

We should guard all usages of LOG.debug() with the if (LOG.isDebugEnabled() guard.

Issue Links

• links to: GitHub Pull Request #179