[
https://issues.apache.org/jira/browse/GEODE-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488914#comment-17488914
]
ASF subversion and git services commented on GEODE-10016:
---------------------------------------------------------
Commit f60277dee9a33502a8fe832f5db54a8f9543eb32 in geode-native's branch
refs/heads/develop from Michael Martell
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=f60277d ]
GEODE-10016: Add map of threadId to threadName (#918)
* Save threadName to thread_local storage
* Per review, get/setThreadName doesn't need tid
* Add threadName in parens after tid
* Update gnmsg for threadName
* Move accessors to Log class
* Inline threadNames instead of constants
* Remove getThreadName()
> Use Thread Name In Log Messages
> -------------------------------
>
> Key: GEODE-10016
> URL: https://issues.apache.org/jira/browse/GEODE-10016
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Michael Martell
> Priority: Minor
> Labels: pull-request-available
>
> The native client logging system currently prints the threadId in all log
> messages. Since all internally created native client threads are named, we
> should print the threadName instead of threadId. This will be extremely
> helpful to understanding the flow of messages since there are many background
> threads in the native client.
> Note: Lots of log messages are running on an application thread which was not
> created internally by the native client. Messages running on these threads
> should continue to print the threadId.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
