-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add safe logging arguments to StorageService #604
base: palantir-cassandra-2.2.18
Are you sure you want to change the base?
Add safe logging arguments to StorageService #604
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left some small nits, otherwise LGTM
logger.warn("Some data streaming failed. Use nodetool to check bootstrap state and resume. For more, see `nodetool help bootstrap`. {}", | ||
SafeArg.of("", SystemKeyspace.getBootstrapState())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
arg name here?
logger.info("Combining new repair request with in-progress (identical) repair command #{}", cmd); | ||
logger.info("Combining new repair request with in-progress (identical) repair command #{}", UnsafeArg.of("command", cmd)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cmd is an int, so this is probably safe, right?
InetAddress preferred = SystemKeyspace.getPreferredIP(address); | ||
streamPlan.requestRanges(address, preferred, keyspace, workMap.get(address)); | ||
} | ||
|
||
logger.debug("Keyspace {}: work map {}.", keyspace, workMap); | ||
// This log line seems unnecessary given the above loop... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe, but I do think in grafana it's easier to analyze a single log line instead of combining multiple, especially when multiple nodes are reporting the logs simultaneously
No description provided.