[
https://issues.apache.org/jira/browse/AMBARI-22633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297773#comment-16297773
]
Olivér Szabó commented on AMBARI-22633:
---------------------------------------
[~kabhwan] [~arunmahadevan], i still did not see commits for branch-2.6, as it
will change be I will merge these (from here:
https://github.com/apache/ambari/tree/branch-2.6-logfeeder-fixes)
actually the ambar 2.6.1 rpm contains these changes (but branch-2.6 was locked
so thats why the 2 fixes are still open
> 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)
