From issues-return-98146-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Tue Jun 2 11:43:03 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id DCBA2180665 for ; Tue, 2 Jun 2020 13:43:02 +0200 (CEST) Received: (qmail 53460 invoked by uid 500); 2 Jun 2020 11:43:02 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 53451 invoked by uid 99); 2 Jun 2020 11:43:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jun 2020 11:43:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E335CE2CF8 for ; Tue, 2 Jun 2020 11:43:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 1A957780254 for ; Tue, 2 Jun 2020 11:43:00 +0000 (UTC) Date: Tue, 2 Jun 2020 11:43:00 +0000 (UTC) From: "Christian Danner (Jira)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-7438) Controller Service UI hangs since controller service doesn't handle reconnections properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-7438?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D17123= 668#comment-17123668 ]=20 Christian Danner commented on NIFI-7438: ---------------------------------------- Thanks [~mattyb149], it seems it solved our issue. We didn't consider a query check but a "show databases" to query metastore = is good enough.=C2=A0 We have applied it to all Non-HA Databases and DEV Environments. The generall problem I described that we had for all controller services se= ems to be gone too.=C2=A0 For instance we had the AzureStorageCredential Controller and Lookup Servic= e that had also multiple entries and doesn't offer such functionality. Neve= rtheless since we have the query check in place, all controller services se= em to work just fine. > Controller Service UI hangs since controller service doesn't handle recon= nections properly > -------------------------------------------------------------------------= ----------------- > > Key: NIFI-7438 > URL: https://issues.apache.org/jira/browse/NIFI-7438 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration, Core Framework > Affects Versions: 1.11.1, 1.11.2, 1.11.3, 1.11.4 > Environment: RHEL 7.6 > NiFi on Docker > Reporter: Christian Danner > Priority: Major > Attachments: image-2020-05-11-13-38-30-457.png > > > We encounter Problems in showing and managing Controller Services on NiFi= Servers that run longer than connected systems we use to connect via Contr= oller Services. Viewing such Controller Services takes about 1 minute to op= en the view and then shows multiple instances of it (see screenshot). > e.g. A "DBCPConnectionPool 1.11.4" shows multiple "Supported Controller S= ervices" all the "DBCPService 1.11.4 from org.apache.nifi - nifi-standard-s= ervices-api-nar" (19 occurances) as well as shows multiple Groups of "Proce= ssors" {color:#172b4d}(19 occurances){color} with the same instances (9 pro= cessor instances). > =C2=A0 > In this specific case we have a connection to a database server that is s= hutdown during the night (DEV environment). NiFi Server continues to run wh= ile database is not reachable. > We suspect that when the database comes available again, it will load th= e controller service completely while not unloading old sessions. Disabling= and re-enabling the controller service doesn't solve the issue, only a com= plete NiFI Server restart fixes this issue. > All related processors also fail to execute defined "ExecuteSQL" Processo= rs until we restarted the Controller Services at least. We get a "SocketExc= eption" since it tries to make an attempt on the old connection which is no= t active anymore. For us it is important to have a "Infinite Connection" wh= ile interacting with the database ({color:#262626}Max Connection Lifetime{c= olor:#003000} =3D -1).{color}{color} -- This message was sent by Atlassian Jira (v8.3.4#803005)