[
https://issues.apache.org/jira/browse/AMBARI-22633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298757#comment-16298757
]
Olivér Szabó edited comment on AMBARI-22633 at 12/20/17 5:09 PM:
-----------------------------------------------------------------
committed to branch-2.6:
{code:java}
commit ab71b5a4153c10936aacdbf581a8481ad7929432
Author: Jungtaek Lim <[email protected]>
Date: Tue Dec 12 14:50:39 2017 +0100
AMBARI-22633. MapDate provides the date incorrectly when Filter is cloned
and used in multi-threads (Jungtaek Lim via oleewere)
{code}
[~kabhwan], now you can submit the review request
was (Author: oleewere):
committed to trunk:
{code:java}
commit ab71b5a4153c10936aacdbf581a8481ad7929432
Author: Jungtaek Lim <[email protected]>
Date: Tue Dec 12 14:50:39 2017 +0100
AMBARI-22633. MapDate provides the date incorrectly when Filter is cloned
and used in multi-threads (Jungtaek Lim via oleewere)
{code}
[~kabhwan], now you can submit the review request
> 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
> Fix For: 2.6.2
>
> 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)
