Hi JB
I saw the commit for the new default. Do you have a rough idea when you will have 1.5.0 released which includes the new commands to manage the scheduled tasks? One generic question, is there a reason why the properties of the OSGi services can't be managed via the shell and/or configuration files. If the bundle doesn't provide custom shell commands it's not possible. Initially I thought I could put the service properties just to the configuration file of the decanter feature. But for unknown reasons, it caused unregistering the service which indicates a correlation between the service and the configuration file. Thanks Oli ________________________________ Von: Jean-Baptiste Onofré <[email protected]> Gesendet: Samstag, 18. November 2017 07:51:00 An: [email protected] Betreff: Re: AW: AW: AW: Update Karaf Scheduler and custom Decanter Collector By the way, I created the following Jira to increase the scheduler.period: https://issues.apache.org/jira/browse/KARAF-5492 I gonna do the change, so, as another workaround, you would be able to use Decanter 1.5.0-SNAPSHOT soon. 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é <[email protected]> > *Gesendet:* Freitag, 17. November 2017 10:58:03 > *An:* [email protected] > *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é <[email protected]> >> *Gesendet:* Donnerstag, 16. November 2017 15:44:43 >> *An:* [email protected] >> *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 <[email protected]> >>> *Gesendet:* Mittwoch, 15. November 2017 16:52:29 >>> *An:* [email protected] >>> *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é <[email protected]> >>> *Gesendet:* Mittwoch, 15. November 2017 12:11:55 >>> *An:* [email protected] >>> *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é >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >> >> -- >> Jean-Baptiste Onofré >> [email protected] >> http://blog.nanthrax.net >> Talend - http://www.talend.com > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
