ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Mahadevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22633) MapDate provides the date incorrectly when Filter is cloned and used in multi-threads
Date Tue, 12 Dec 2017 17:44:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-22633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287961#comment-16287961
] 

Arun Mahadevan commented on AMBARI-22633:
-----------------------------------------

cc [~ggolani], it will be good if we can get this in 2.6.1.

> MapDate provides the date incorrectly when Filter is cloned and used in multi-threads
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22633
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22633
>             Project: Ambari
>          Issue Type: Bug
>          Components: logsearch
>    Affects Versions: 2.6.1
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>            Priority: Critical
>         Attachments: AMBARI-22633-branch-2.6.patch
>
>
> In AMBARI-22600, we cloned the Filter instance to assign the instance per child thread,
which also clones the map of Mapper. Other Mapper implements only have String(s) type of fields
hence thread-safe, but MapperDate has SimpleDateFormat type of fields which is known as non
thread-safe, so cloning the Filter which has one or more MapperDate and using them concurrently
makes multi-threads issue.
> For example I'm seeing the logdate improperly stored.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message