[
https://issues.apache.org/jira/browse/CASSANDRA-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16749:
-------------------------------------------
Fix Version/s: (was: 4.0.x)
(was: 4.x)
4.1
4.0.1
Source Control Link:
https://github.com/apache/cassandra/commit/6c8f6bd663fea4b909f0e5723dbf7f181dd70487
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[6c8f6bd663fea4b909f0e5723dbf7f181dd70487|https://github.com/apache/cassandra/commit/6c8f6bd663fea4b909f0e5723dbf7f181dd70487].
> DiagnosticEventService.publish logging logs events without an overridden
> toString causing less useful debug logs
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16749
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
> Reporter: David Capwell
> Assignee: Zoltan Ersek
> Priority: Low
> Fix For: 4.0.1, 4.1
>
> Attachments: 16749-trunk.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The DiagnosticEventService logs each publish (if the event is enabled) using
> a logger, but the different events do not override the toString; this leaves
> the following logs
> {code}
> Publishing: org.apache.cassandra.gms.GossiperEvent@3cadeef2
> Publishing: org.apache.cassandra.gms.GossiperEvent@6159419d
> Publishing:
> org.apache.cassandra.service.PendingRangeCalculatorServiceEvent@18e52b1
> Publishing: org.apache.cassandra.locator.TokenMetadataEvent@43a76a1a
> etc.
> {code}
> To make these logs more meaningful, we might want to consider matching the
> persistent logic and convert the event to a map and then logging the map
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
