Hi all, is anyone using Jeeves schedule manager [1] which could be configured in config.xml [2] ? It’s a pretty old feature to schedule harvesters by XML configuration I think but I’ve never seen user using it and the usage is not documented as far as know.
So, I would like to propose to remove it for 2 main reasons:
- in some setup in multinodes config, the app consumes lots of threads (mainly related to Quartz schedulers and workers) - so removing this feature decrease the number of threads required
- cleaning the codebase
What do you think ?
Francois
[1] https://github.com/geonetwork/core-geonetwork/blob/develop/jeeves/src/main/java/jeeves/server/ScheduleManager.java
[2] https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/config.xml#L123
On Mon, Jul 28, 2014 at 11:14 AM, Francois Prunayre <fx.prunayre@anonymised.com>
wrote:
Hi all, is anyone using Jeeves schedule manager [1] which could be
configured in config.xml [2] ? It's a pretty old feature to schedule
harvesters by XML configuration I think but I've never seen user using it
and the usage is not documented as far as know.
So, I would like to propose to remove it for 2 main reasons:
1) in some setup in multinodes config, the app consumes lots of threads
(mainly related to Quartz schedulers and workers) - so removing this
feature decrease the number of threads required
2) cleaning the codebase
What do you think ?
Francois
[1]
https://github.com/geonetwork/core-geonetwork/blob/develop/jeeves/src/main/java/jeeves/server/ScheduleManager.java
[2]
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/config.xml#L123
Hi,
From my part, you can remove it. If we need to configure harvesters by
configuration files in the future, I am sure we can find a more optimized
way to do this.
María.
2014-07-28 11:20 GMT+02:00 María Arias de Reyna <delawen@anonymised.com>:
On Mon, Jul 28, 2014 at 11:14 AM, Francois Prunayre <fx.prunayre@anonymised.com
> wrote:
Hi all, is anyone using Jeeves schedule manager [1] which could be
configured in config.xml [2] ? It's a pretty old feature to schedule
harvesters by XML configuration I think but I've never seen user using it
and the usage is not documented as far as know.
So, I would like to propose to remove it for 2 main reasons:
1) in some setup in multinodes config, the app consumes lots of threads
(mainly related to Quartz schedulers and workers) - so removing this
feature decrease the number of threads required
2) cleaning the codebase
What do you think ?
Francois
[1]
https://github.com/geonetwork/core-geonetwork/blob/develop/jeeves/src/main/java/jeeves/server/ScheduleManager.java
[2]
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/config.xml#L123
Hi,
From my part, you can remove it. If we need to configure harvesters by
configuration files in the future, I am sure we can find a more optimized
way to do this.
Yep, i agree. It could be nice to be able to copy/paste harvester
configuration from one node to another so users can exchange configs (and
also provide config when reporting bug).
Thanks for your feedback Maria.
Francois
María.
I do use it but I think it is ok to remove because I can easily do the scheduling with spring.
···
On Mon, Jul 28, 2014 at 11:24 AM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
2014-07-28 11:20 GMT+02:00 María Arias de Reyna <delawen@anonymised.com>:
Yep, i agree. It could be nice to be able to copy/paste harvester configuration from one node to another so users can exchange configs (and also provide config when reporting bug).
Thanks for your feedback Maria.
Francois
On Mon, Jul 28, 2014 at 11:14 AM, Francois Prunayre <fx.prunayre@anonymised.com> wrote:
Hi all, is anyone using Jeeves schedule manager [1] which could be configured in config.xml [2] ? It’s a pretty old feature to schedule harvesters by XML configuration I think but I’ve never seen user using it and the usage is not documented as far as know.
So, I would like to propose to remove it for 2 main reasons:
- in some setup in multinodes config, the app consumes lots of threads (mainly related to Quartz schedulers and workers) - so removing this feature decrease the number of threads required
- cleaning the codebase
What do you think ?
Francois
[1] https://github.com/geonetwork/core-geonetwork/blob/develop/jeeves/src/main/java/jeeves/server/ScheduleManager.java
[2] https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/config.xml#L123
Hi,
From my part, you can remove it. If we need to configure harvesters by configuration files in the future, I am sure we can find a more optimized way to do this.
María.
2014-07-28 11:56 GMT+02:00 Jesse Eichar <jesse.eichar@anonymised.com>:
I do use it but I think it is ok to remove because I can easily do the
scheduling with spring.
Ok so we can keep it. I'll only turn it off in my multinode setup.
Thanks.
Francois
On Mon, Jul 28, 2014 at 11:24 AM, Francois Prunayre <fx.prunayre@anonymised.com
> wrote:
2014-07-28 11:20 GMT+02:00 María Arias de Reyna <delawen@anonymised.com>:
On Mon, Jul 28, 2014 at 11:14 AM, Francois Prunayre <
fx.prunayre@anonymised.com> wrote:
Hi all, is anyone using Jeeves schedule manager [1] which could be
configured in config.xml [2] ? It's a pretty old feature to schedule
harvesters by XML configuration I think but I've never seen user using it
and the usage is not documented as far as know.
So, I would like to propose to remove it for 2 main reasons:
1) in some setup in multinodes config, the app consumes lots of threads
(mainly related to Quartz schedulers and workers) - so removing this
feature decrease the number of threads required
2) cleaning the codebase
What do you think ?
Francois
[1]
https://github.com/geonetwork/core-geonetwork/blob/develop/jeeves/src/main/java/jeeves/server/ScheduleManager.java
[2]
https://github.com/geonetwork/core-geonetwork/blob/develop/web/src/main/webapp/WEB-INF/config.xml#L123
Hi,
From my part, you can remove it. If we need to configure harvesters by
configuration files in the future, I am sure we can find a more optimized
way to do this.
Yep, i agree. It could be nice to be able to copy/paste harvester
configuration from one node to another so users can exchange configs (and
also provide config when reporting bug).
Thanks for your feedback Maria.
Francois
María.
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork