[
https://issues.apache.org/jira/browse/HADOOP-17874?focusedWorklogId=645206&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-645206
]
ASF GitHub Bot logged work on HADOOP-17874:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Sep/21 10:35
Start Date: 01/Sep/21 10:35
Worklog Time Spent: 10m
Work Description: virajjasani commented on pull request #3343:
URL: https://github.com/apache/hadoop/pull/3343#issuecomment-910156097
@steveloughran I have just pushed an addendum to get rid of creating entire
map and reassigning the newly created map to volatile instance, and rather
simplified it by using CHM provided concurrent KeySet.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 645206)
Time Spent: 50m (was: 40m)
> ExceptionsHandler to add terse/suppressed Exceptions in thread-safe manner
> --------------------------------------------------------------------------
>
> Key: HADOOP-17874
> URL: https://issues.apache.org/jira/browse/HADOOP-17874
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Even though we have explicit comments stating that we have thread-safe
> replacement of terseExceptions and suppressedExceptions, in reality we don't
> have it. As we can't guarantee only non-concurrent addition of Exceptions at
> a time from any Server implementation, we should make this thread-safe.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
