ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-17618) Fix ConcurrentModificationException in Resource.Type
Date Fri, 08 Jul 2016 19:32:11 GMT


Hadoop QA commented on AMBARI-17618:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:


Test results:
Console output:

This message is automatically generated.

> Fix ConcurrentModificationException in Resource.Type
> ----------------------------------------------------
>                 Key: AMBARI-17618
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.4.0
>         Attachments: AMBARI-17618.patch
> Resource.Type is not thread-safe, sometimes ConcurrentModificationException may occur
when for. ex Ambari is extracting a new view and adding a new view resource type call Resource.Type.setType()),
meanwhile on a separate incoming request processing thread iterating through resource types
calling Resource.type.values().

This message was sent by Atlassian JIRA

View raw message