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 676DC200D52 for ; Sat, 18 Nov 2017 06:24:54 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5F634160C0A; Sat, 18 Nov 2017 05:24:54 +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 7CDD7160BFB for ; Sat, 18 Nov 2017 06:24:53 +0100 (CET) Received: (qmail 51578 invoked by uid 500); 18 Nov 2017 05:24:52 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 51568 invoked by uid 99); 18 Nov 2017 05:24:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Nov 2017 05:24:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 7164E1A11EE for ; Sat, 18 Nov 2017 05:24:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.1 X-Spam-Level: * X-Spam-Status: No, score=1.1 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id fWkRgG8aaHHK for ; Sat, 18 Nov 2017 05:24:49 +0000 (UTC) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7A4255FDB9 for ; Sat, 18 Nov 2017 05:24:48 +0000 (UTC) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.109] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 818A6FB87E for ; Sat, 18 Nov 2017 06:24:41 +0100 (CET) Subject: Re: AW: AW: AW: Update Karaf Scheduler and custom Decanter Collector To: user@karaf.apache.org References: <29a1d49a-b909-8559-00fb-7fce7e63969d@nanthrax.net> <4bf3b1f7-dbe4-1306-8d6d-1c2208824242@nanthrax.net> <6e5d25d9-7d73-8542-e72a-8864db6bccf5@nanthrax.net> From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= Message-ID: <04e2fbef-a939-003e-0583-564fd67bb029@nanthrax.net> Date: Sat, 18 Nov 2017 06:24:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit archived-at: Sat, 18 Nov 2017 05:24:54 -0000 Probably the easiest way for now is to build your custom JMX collector with the period changed. Regards JB On 11/17/2017 09:21 PM, Oliver Wulff wrote: > Hi JB > > > Thanks. Can I do anything to update the period with the current version 1.4.0? > Unfortunately, the 10�seconds are�a blocker for�1.4.0. > > > Thanks > > Oli > > -------------------------------------------------------------------------------- > *Von:* Jean-Baptiste Onofr� > *Gesendet:* Freitag, 17. November 2017 10:58:03 > *An:* user@karaf.apache.org > *Betreff:* Re: AW: AW: Update Karaf Scheduler and custom Decanter Collector > Hi Oli, > > thanks for the report. > > I will do two things: > > 1. Increase the default scheduling period for the JMX collector (I agree that I > was a bit aggressive with 10 seconds ;)). > 2. As said (and I already created the Jira), I will improve the scheduler > commands (and MBeans). > > Regards > JB > > On 11/17/2017 10:41 AM, Oliver Wulff wrote: >> Hi JB >> >> >> When I have to change it via a command I need to know what the script was of the >> JMX Collector: >> >> >> karaf@karaf()> scheduler:list >> Name� � � � � � � � � � � �| Schedule >> ---------------------------------------------------------------------- >> decanter-collector-jmx.440 | at(2017-11-17T09:30:19.256+01:00, -1, 10) >> decanter-collector-jmx.437 | at(2017-11-17T09:30:19.224+01:00, -1, 10) >> decanter-collector-jmx.438 | at(2017-11-17T09:30:19.240+01:00, -1, 10) >> decanter-collector-jmx.439 | at(2017-11-17T09:30:19.256+01:00, -1, 10) >> >> karaf@karaf()> scheduler:schedule --period 60 --name decanter-collector-jmx.440 >> Error executing command scheduler:schedule: argument script is required >> >> The default of 10 seconds is way too often in our environment. From an >> operations point of view changing a file is quite easy to deploy but login to >> Karaf and executing commands is more complicated. The Decanter scheduler was >> easier to manage because you could configure the period in a file. >> >> >> But first, I must be able to update the period of the schedules registered by >> Decanter. >> >> >> Thanks >> >> Oli >> >> >> -------------------------------------------------------------------------------- >> *Von:* Jean-Baptiste Onofr� >> *Gesendet:* Donnerstag, 16. November 2017 15:44:43 >> *An:* user@karaf.apache.org >> *Betreff:* Re: AW: Update Karaf Scheduler and custom Decanter Collector >> I created the following Jira about that: >> >> https://issues.apache.org/jira/browse/KARAF-5486 >> >> Regards >> JB >> >> On 11/16/2017 03:40 PM, Oliver Wulff wrote: >>> Hi JB >>> >>> >>> I can update the annotation to a period of 60 seconds for my custom collector >>> but I can't for the jmx collector. At the moment, our elasticsearch cluster gets >>> 6�times more data from the jmx collector because I don't know how to update�the >>> scheduler period for it. >>> >>> >>> When I check the list, I also don't know what each scheduler is exactly doing: >>> >>> >>> karaf@karaf()> scheduler:list >>> Name� � � � � � � � � � � �| Schedule >>> ---------------------------------------------------------------------- >>> decanter-collector-jmx.801 | at(2017-11-13T15:06:57.138+01:00, -1, 10) >>> decanter-collector-jmx.803 | at(2017-11-13T15:06:57.154+01:00, -1, 10) >>> decanter-collector-jmx.804 | at(2017-11-13T15:06:57.154+01:00, -1, 10) >>> decanter-collector-jmx.802 | at(2017-11-13T15:06:57.154+01:00, -1, 10) >>> >>> Thanks >>> >>> Oli >>> >>> -------------------------------------------------------------------------------- >>> *Von:* Oliver Wulff >>> *Gesendet:* Mittwoch, 15. November 2017 16:52:29 >>> *An:* user@karaf.apache.org >>> *Betreff:* AW: Update Karaf Scheduler and custom Decanter Collector >>> >>> Hi JB >>> >>> >>> Yes, I meant the user guide. >>> >>> >>> If I want to manage the scheduler I have to pass a script. What kind of script >>> shall I use? Right now, I just see the name "decanter-collector-sl.474" where >>> the prefix is used from the configured scheduler name�(annotation). >>> >>> >>> But I'd like to manage the interval via configuration and thought this should work: >>> >>> config:edit org.myown.karaf.decanter.collector.sl >>> config:property-set decanter.collector.name serviceLocator >>> config:property-set scheduler.period 60 >>> config:property-set scheduler.concurrent false >>> config:property-set scheduler.name decanter-collector-sl >>> config:update >>> >>> >>> But the above commands disable the scheduler and I don't know why. >>> >>> >>> How can I update the period either via scheduler command and via configuration file? >>> >>> >>> Thanks >>> >>> Oli >>> >>> -------------------------------------------------------------------------------- >>> *Von:* Jean-Baptiste Onofr� >>> *Gesendet:* Mittwoch, 15. November 2017 12:11:55 >>> *An:* user@karaf.apache.org >>> *Betreff:* Re: Update Karaf Scheduler and custom Decanter Collector >>> By the way, that's service properties for the config. You can change using the >>> scheduler command too. >>> >>> I will update the user guide about that. >>> >>> Regards >>> JB >>> >>> On 11/15/2017 12:01 PM, Oliver Wulff wrote: >>>> Hi all >>>> >>>> >>>> Similar to the JMX Collector I've created my own collector but wanted to update >>>> the default intervall from 10seconds to 60 seconds. >>>> >>>> >>>> As soon as I�create the configuration with the matching >>>> PID�(org.myown.karaf.decanter.collector.sl), the scheduler is removed and not >>>> shown in "scheduler:list" anymore. >>>> >>>> >>>> @Component( >>>> //name = "org.myown.karaf.decanter.collector.sl", >>>>� � � immediate = true, >>>>� � � property = { "decanter.collector.name=serviceLocator", >>>>� � � � � � � "scheduler.period:Long=10", >>>>� � � � � � � "scheduler.concurrent:Boolean=false", >>>>� � � � � � � "scheduler.name=decanter-collector-sl"} >>>> ) >>>> public class ServiceLocatorCollector implements Runnable { >>>> >>>> config:edit org.myown.karaf.decanter.collector.sl >>>> >>>> config:property-set decanter.collector.name serviceLocator >>>> config:property-set scheduler.period 60 >>>> config:property-set scheduler.concurrent false >>>> config:property-set scheduler.name decanter-collector-sl >>>> config:update >>>> >>>> >>>> Unfortunately, the wiki page is not yet updated how to manage scheduling in >>>> Decanter. >>>> >>>> >>>> What am I doing wrong? >>>> >>>> >>>> Thanks >>>> >>>> Oli >>>> >>>> >>> >>> -- >>> Jean-Baptiste Onofr� >>> jbonofre@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >> >> -- >> Jean-Baptiste Onofr� >> jbonofre@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com > > -- > Jean-Baptiste Onofr� > jbonofre@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com -- Jean-Baptiste Onofr� jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com