You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/01/21 08:16:34 UTC
[jira] Created: (SLING-177) Improvements to event bundle
Improvements to event bundle
----------------------------
Key: SLING-177
URL: https://issues.apache.org/jira/browse/SLING-177
Project: Sling
Issue Type: Improvement
Components: Event
Reporter: Carsten Ziegeler
Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-177:
-----------------------------------
In addition a job could signal a retry frequency
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-177:
-----------------------------------
We could remove the need for locking by using the id as the node name and not allowing same name siblings.
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-177:
-----------------------------------
Remaining Estimate: 0h
Original Estimate: 0h
In addition we could make the following enhencements:
- Check if the locking could be simplified
- parallel job processing: it should be possible to process different job types in parallel, while jobs of the same type will be queued
- jobs should be marked to be only runnable on the instance they were created on
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-177.
----------------------------------
Resolution: Fixed
This has been implemented a while ago.
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-177:
-----------------------------------
In addition to a retry count we should add a retry delay after which a retry is performed.
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-177) Improvements to event bundle
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-177:
-----------------------------------
Assignee: Carsten Ziegeler
> Improvements to event bundle
> ----------------------------
>
> Key: SLING-177
> URL: https://issues.apache.org/jira/browse/SLING-177
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Currently the eventing does not store events immediately into the repository in order to quickly respond back to the event admin. (This is in order to not get blacklisted). The incoming event is put into a queue and picked up from there.
> It would be safer to have a separate write queue which is independent from the processing queue to write the event as soon into the repository as possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.