Great! ... Thank you very much, Tejas. (01)
Regards. =ppy
-- (02)
On Sun, Feb 21, 2010 at 9:21 PM, Tejas Parikh <tejas@xxxxxxxxxxxxxxx> wrote:
> Peter,
>
> I have disabled OBO pull scheduler for now.
>
> # OBO Pull Scheduler properties
> # Enable/Disable scheduler service flag
> obo.pull.scheduler.enabled=false
>
> Admin user can manually execute the pull (through admin UI) whenever needed.
>
> Thanks,
> --Tejas (03)
> On Sun, Feb 21, 2010 at 11:09 PM, Peter Yim <peter.yim@xxxxxxxx> wrote:
>>
>> Thank you very much for the prompt response, Jim.
>>
>> Paul, could you please tell us what exactly need to be done to
>>
>> (a) modify the schedule, and
>>
>> (b) completely disable OBO pull,
>>
>> ... and on Paul's instructions, would Tejas please help do (a) above,
>> and do it once a week (at least for now, say at 4am PST every
>> Saturday) and then rebuild and redeploy into tomcat, .... assume that
>> will leave the existing ontologies (including those already pulled
>> from the OBO Foundry) intact.
>>
>>
>> Thanks & regards. =ppy
>> -- (04)
>> On Sun, Feb 21, 2010 at 7:52 PM, <jchatign@xxxxxxx> wrote:
>> > Peter,
>> >
>> > I checked the logs on my local (BBN) machine and can confirm that the
>> > federation is only running every four hours. Each run is completing in
>> > just
>> > a few seconds because it isn't finding any *new* ontologies on the
>> > OOR-sandbox. And you are right that federation is a pure "download"
>> > operation as far as OOR-sandbox is concerned.
>> >
>> > I believe the "OBO pull" operation does a complete checkout (cvs or svn)
>> > of
>> > the OBO repository each time it runs. So that could account for the
>> > traffic
>> > you're seeing if it has been configured to run hourly.
>> >
>> > To change an operation's schedule (or disable it completely) you need to
>> > modify the bioportal core's build.properties file, rebuild and redeploy
>> > into
>> > tomcat.
>> >
>> > In any case, having a look at bioportal.log (or catalina.out) on the
>> > OOR-sandbox machine would likely tell the full story.
>> >
>> > Jim (05)
>> >> -----Original Message-----
>> >> From: Peter Yim [mailto:peter.yim@xxxxxxxx]
>> >> Sent: Sunday, February 21, 2010 4:21 PM
>> >> To: Paul R Alexander; Jim Chatigny; Tejas Parikh; Shinya Yamada
>> >> Cc: OpenOntologyRepository-development; [cwe-imp]
>> >> Subject: Heavy "upload" traffic to the OOR-sandbox
>> >>
>> >>
>> >> Paul / Jim / Tejas / Shinya,
>> >>
>> >>
>> >> I am seeing some irregular traffic pattern in the OOR-sandbox.
>> >>
>> >> See:
>> >> http://ontolog.cim3.net/file/work/OOR/oor-dev/issue/oor-01_eth
>> >> 0-traffic_2010-02-21_172029.jpg
>> >> ... where I have shown the traffic into eth-0 of the <oor-01> vm.
>> >>
>> >> [ ... Started about mid-day Fri 2010.02.12, we are seeing
>> >> uploads that goes into the OOR-sandbox every hour (starting
>> >> about 15 min. past the hour, and lasting anywhere from 10 to
>> >> 30 minutes or so) and peeks at rates of up to ~10mbps. ]
>> >>
>> >> Ref. Jim's explanations last Friday
>> >> (http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_20
>> >> 10_02_19#nid28PL),
>> >> I suspect this traffic could be the result of:
>> >>
>> >> (a) the BioPortal "OBO-pull" traffic - something BioPortal
>> >> would do to periodically check the Open Biomedical Ontologies
>> >> (OBO) Foundry, and pull over any updates into the BioPortal.
>> >> Assuming the OOR-sandbox has not been customized in this
>> >> respect (to "not" behave like BioPortal) then this probably
>> >> could be it ... although, I am somewhat surprised that there
>> >> is *so much traffic* needed to sync up with the OBO Foundry ... or,
>> >>
>> >> (b) Jim's federation traffic ... although this is less
>> >> likely, because Jim claims that he has been "downloading"
>> >> from the OOR-sandbox to his instance of the repository, and
>> >> this traffic, presumably, is traffic going "into" the
>> >> OOR-sandbox and not "out of" it.
>> >>
>> >>
>> >> Questions:
>> >>
>> >> 1. Does the above explain the situation adequately, or am I
>> >> missing something (somewhere else)?
>> >>
>> >> 2. if above (a) is really the case, can it be stopped by the
>> >> OOR-sandbox admin (or does it have to be modified at the
>> >> configuration, or the code somewhere). [I can only see an
>> >> option to invoke the "OBO Pull - Run" (and don't seem to see
>> >> a "OBO Pull - Stop") at the Admin GUI.
>> >>
>> >> 3. Corrective action suggestions and plans ... anyone?
>> >>
>> >>
>> >> Thanks & regards. =ppy
>> >> -- (06)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-dev/
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-dev/
Shared Files: http://ontolog.cim3.net/file/work/OOR/dev/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (07)
|