[
https://issues.apache.org/jira/browse/USERGRID-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rod Simpson updated USERGRID-175:
---------------------------------
Description:
Distributed Job System
Need to research and develop a solid/simple distributed job system
Import/export features:
Currently Usergrid features only an export feature, and it has some serious
limitations:
- Not distributed
- No way to stop GIANT jobs
- Uses the current scheduler which is limiting how our export jobs gets run.
- No timeouts.
We should make import and export distributed by using an alternative scheduling
mechanism that supports distributed processing (e.g. Akka, RxJava, etc.).
was:
Currently Usergrid features only an export feature, and it has some serious
limitations:
- Not distributed
- No way to stop GIANT jobs
- Uses the current scheduler which is limiting how our export jobs gets run.
- No timeouts.
We should make import and export distributed by using an alternative scheduling
mechanism that supports distributed processing (e.g. Akka, RxJava, etc.).
> Distributed job system
> ----------------------
>
> Key: USERGRID-175
> URL: https://issues.apache.org/jira/browse/USERGRID-175
> Project: Usergrid
> Issue Type: Story
> Components: Stack
> Reporter: David Johnson
>
> Distributed Job System
> Need to research and develop a solid/simple distributed job system
> Import/export features:
> Currently Usergrid features only an export feature, and it has some serious
> limitations:
> - Not distributed
> - No way to stop GIANT jobs
> - Uses the current scheduler which is limiting how our export jobs gets run.
> - No timeouts.
> We should make import and export distributed by using an alternative
> scheduling mechanism that supports distributed processing (e.g. Akka, RxJava,
> etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
