Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7F66F10550 for ; Wed, 26 Mar 2014 18:04:55 +0000 (UTC) Received: (qmail 93069 invoked by uid 500); 26 Mar 2014 18:04:54 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 93043 invoked by uid 500); 26 Mar 2014 18:04:53 -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 Received: (qmail 93032 invoked by uid 99); 26 Mar 2014 18:04:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 18:04:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eaepstein@gmail.com designates 209.85.128.182 as permitted sender) Received: from [209.85.128.182] (HELO mail-ve0-f182.google.com) (209.85.128.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 18:04:48 +0000 Received: by mail-ve0-f182.google.com with SMTP id jw12so2835603veb.27 for ; Wed, 26 Mar 2014 11:04:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0v5bOVNM82ODL5U0XTTsf88ScD6ZTwPIL9/zZKBEMl0=; b=DoIgDlTrkPT7iXPRkbrDEokHJLAZuLFL4LMgFn302ahyiSS4P1sGOlBKKV7gSwwTLU dxVYKKIuVFTN5CcRi7fWVyUTWbJYnbmNe+36fYvGQp49D4CuhCXtUufKxaaapRdLeSrh nU9ctQQr2N6XNweuDLWhw6g/ERw7DXMV4zFRh4eXDfQ40TU08Llx13TU4j3/wjJyMry0 h/8Yi+iVH75bPeim7QacbLW7jdMYMiiYCXiT9g0uZcaBBKxj4bl+zzpXfbsGE7teBIoI e1wV1u3Lkt/7VeeMio3Po6c083nPoN9+dKrcT39jEugQ+W0nUTdjE19UTtnyAu6+Z+x4 mDYQ== MIME-Version: 1.0 X-Received: by 10.52.240.207 with SMTP id wc15mr53278636vdc.14.1395857067177; Wed, 26 Mar 2014 11:04:27 -0700 (PDT) Received: by 10.52.97.130 with HTTP; Wed, 26 Mar 2014 11:04:27 -0700 (PDT) In-Reply-To: <5332DAB3.6030808@orkash.com> References: <532BD841.2010705@orkash.com> <5332A701.6070301@orkash.com> <5332DAB3.6030808@orkash.com> Date: Wed, 26 Mar 2014 14:04:27 -0400 Message-ID: Subject: Re: Ducc Problems From: Eddie Epstein To: user@uima.apache.org Content-Type: multipart/alternative; boundary=20cf307ac141a57b8f04f5864cec X-Virus-Checked: Checked by ClamAV on apache.org --20cf307ac141a57b8f04f5864cec Content-Type: text/plain; charset=ISO-8859-1 Hi Reshu, The collectionProcessingComplete() method in UIMA-AS has a limitation: a Collection Processing Complete request sent to the UIMA-AS Analysis Service is cascaded down to all delegates; however, if a particular delegate is scaled-out, only one of the instances of the delegate will get this call. Since DUCC is using UIMA-AS to scale out the Job processes, it has no way to deliver a CPC to all instances. The applications we have been running on DUCC have used the Work Item CAS as a signal to CAS consumers to do CPC level processing. That is discussed in the first reference above, in the paragraph "Flushing Cached Data". Eddie On Wed, Mar 26, 2014 at 9:48 AM, reshu.agarwal wrote: > On 03/26/2014 06:43 PM, Eddie Epstein wrote: > >> Are you using standard UIMA interface code to Solr? If so, which Cas >> Consumer? >> >> Taking at quick look at the source code for SolrCASConsumer, the batch and >> collection process complete methods appear to do nothing. >> >> Thanks, >> Eddie >> >> >> On Wed, Mar 26, 2014 at 6:08 AM, reshu.agarwal >> wrote: >> >> On 03/21/2014 11:42 AM, reshu.agarwal wrote: >>> >>> Hence we can not attempt batch processing in cas consumer and it >>>> increases our process timing. Is there any other option for that or is >>>> it a >>>> bug in DUCC? >>>> >>>> Please reply on this problem as if I am sending document in solr one by >>> one by cas consumer without using batch process and committing solr. It >>> is >>> not optimum way to use this. Why ducc is not calling collection Process >>> Complete method of Cas Consumer? And If I want to do that then What is >>> the >>> way to do this? >>> >>> I am not able to find any thing about this in DUCC book. >>> >>> Thanks in Advanced. >>> >>> -- >>> Thanks, >>> Reshu Agarwal >>> >>> >>> Hi Eddie, > > I am not using standard UIMA interface code to Solr. I create my own Cas > Consumer. I will take a look on that too. But the problem is not for > particularly to use solr, I can use any source to store my output. I want > to do batch processing and want to use collectionProcessComplete. Why DUCC > is not calling it? I check it with UIMA AS also and my cas consumer is > working fine with it and also performing batch processing. > > -- > Thanks, > Reshu Agarwal > > --20cf307ac141a57b8f04f5864cec--