[
https://issues.apache.org/jira/browse/SENTRY-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049293#comment-16049293
]
Brian Towles commented on SENTRY-1798:
--------------------------------------
This is a easy quick one to do.
My thoughts are to put in a simple thread naming structure like
sentry-service-1
hms-follower-1
store-cleaner-1
As well making use of the *guava* _ThreadFactoryBuilder_ in order to provide
the dynamic numbering of the thread name instead of the anonymous classes or
lambdas.
Currently the main Sentry Service thread uses an anonymous class to provide the
naming and numbering. Im thinking making all of these a uniform implementation
is the best plan.
Additionally the HDFS FullUpdateInitializer needs to have a custom thread name
implemented. Allowing us to explicitly identify sentry threads running in HDFS
processes.
> Provide names for HMSFollower and cleaner threads
> -------------------------------------------------
>
> Key: SENTRY-1798
> URL: https://issues.apache.org/jira/browse/SENTRY-1798
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Brian Towles
> Labels: bite-sized, newbie
> Fix For: sentry-ha-redesign
>
>
> We have several important thread executors which use default names - we
> should use custom names instead.
> At least we should do it for HMSFollower, cleaner thread and main service
> thread.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
