Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1C8F6200BA7 for ; Fri, 21 Oct 2016 20:06:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1B1EB160AE8; Fri, 21 Oct 2016 18:06:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 63A66160ADE for ; Fri, 21 Oct 2016 20:05:59 +0200 (CEST) Received: (qmail 41042 invoked by uid 500); 21 Oct 2016 18:05:58 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 41013 invoked by uid 99); 21 Oct 2016 18:05:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2016 18:05:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 685A32C2A67 for ; Fri, 21 Oct 2016 18:05:58 +0000 (UTC) Date: Fri, 21 Oct 2016 18:05:58 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-18652) Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 21 Oct 2016 18:06:00 -0000 [ https://issues.apache.org/jira/browse/AMBARI-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595874#comment-15595874 ] Hudson commented on AMBARI-18652: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5844 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5844/]) AMBARI-18652 - Alert Targets Cannot Be Updated Due To Transaction / (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66259872fede7645be5c49391a3aa8bf13f4c8bf]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertDispatchDAO.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/services/AlertNoticeDispatchServiceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertGroupEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertNoticeEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertTargetResourceProviderTest.java > Alert Targets Cannot Be Updated Due To Transaction / Cache Timing Issues > ------------------------------------------------------------------------ > > Key: AMBARI-18652 > URL: https://issues.apache.org/jira/browse/AMBARI-18652 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18652.patch > > > There is a JPA timing issue WRT to updating alert targets where lazy loaded lists outside of a transaction cause the data set on the {{AlertTargetEnity}} to be refreshed from the database. > While maintaining the bi-directional relationship between {{AlertTargetEntity}} and {{AlertGroupEntity}}, and {{IndirectSet}} from JPA causes JPA to detect a stale entity from another transaction. > STR: > It's more likely to happen when there are active alerts. > - Create a new alert target for _just_ HDFS > - Shut down HDFS > - Try to edit the name of the alert target > It will return a 200 return code, but the data will not have changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)