[ 
https://issues.apache.org/jira/browse/HADOOP-17752?focusedWorklogId=609661&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-609661
 ]

ASF GitHub Bot logged work on HADOOP-17752:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Jun/21 11:49
            Start Date: 10/Jun/21 11:49
    Worklog Time Spent: 10m 
      Work Description: liangxs commented on pull request #3085:
URL: https://github.com/apache/hadoop/pull/3085#issuecomment-858553624


   >  ...
   > I think this is ok, because configurations are not very frequently 
reloaded.
   > 
   
   For newly created conf, `Configuration#properties` is null, which will 
trigger reload operation when access. So I think it is
    not a problem.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 609661)
    Time Spent: 1h 10m  (was: 1h)

> Remove lock contention in REGISTRY of Configuration
> ---------------------------------------------------
>
>                 Key: HADOOP-17752
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17752
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: common
>            Reporter: Xuesen Liang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Every Configuration instance is put into *Configuration#REGISTRY* by its 
> constructor. This operation is guard by Configuration.class.
> REGISTRY is a *WeakHashMap*, which should be replaced by *ConcurrentHashMap*.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to