From user-return-7989-archive-asf-public=cust-asf.ponee.io@uima.apache.org Thu Oct 11 11:26:11 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B17F518064A for ; Thu, 11 Oct 2018 11:26:10 +0200 (CEST) Received: (qmail 71327 invoked by uid 500); 11 Oct 2018 09:26:09 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Delivered-To: moderator for user@uima.apache.org Received: (qmail 5524 invoked by uid 99); 11 Oct 2018 08:53:10 -0000 X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.002 X-Spam-Level: X-Spam-Status: No, score=-3.002 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled From: "Huy, Patrick" To: "user@uima.apache.org" Subject: UIMA-AS on Kubernetes Thread-Topic: UIMA-AS on Kubernetes Thread-Index: AdRhPp3tQcxrLiMOQty++sgXswU3Iw== Date: Thu, 11 Oct 2018 08:52:56 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.4.150.129] Content-Type: multipart/alternative; boundary="_000_dbe1363b070e4c968eb6c42c9e9e44e5sapcom_" MIME-Version: 1.0 --_000_dbe1363b070e4c968eb6c42c9e9e44e5sapcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, we are running UIMA-AS on Kubernetes and we are facing some issues: when th= e endpoint a BaseUIMAAsynchronousEngine_impl is connected to goes missing (= because it's being restarted by Kubernetes) while a CAS is being processed = it seems like the AsynchronousEngine never recovers and becomes unusable fr= om that point (it seems that the CAS is "gone"), currently we are using the= "failover" activemq protocol but it does not seem to always help with the = situation. When the components processing a CAS go down while a CAS is being processed= we are currently unable to detect whether the process is just taking long = or whether the component failed - we are currently waiting on processing Ti= meouts to catch this state but something better/faster (like healthiness pi= ngs or something) would be more desirable. Also it seems like our component using the BaseUIMAAsynchronousEngines req= uires a very high amount of RAM to hold the CASes for each CAS Pool (around= 5MB per CAS) is there anything that can be done to optimize this? Thanks in advance! Patrick --_000_dbe1363b070e4c968eb6c42c9e9e44e5sapcom_--