[
https://issues.apache.org/jira/browse/AMBARI-22633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288035#comment-16288035
]
Hadoop QA commented on AMBARI-22633:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901640/AMBARI-22633-branch-2.6.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12834//console
This message is automatically generated.
> 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)
