You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2017/12/12 09:34:01 UTC
[jira] [Updated] (AMBARI-22633) MapDate provides the date
incorrectly when Filter is cloned and used in multi-threads
[ https://issues.apache.org/jira/browse/AMBARI-22633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim updated AMBARI-22633:
----------------------------------
Attachment: AMBARI-22633-branch-2.6.patch
Attaching patch for branch-2.6.
> 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)