[
https://issues.apache.org/jira/browse/SLING-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated SLING-10528:
-----------------------------------
Description:
Journal distribution serialise content packages in binary less mode only. When
doing "deep" distribution, the package can still become so large that the
importing side can't ingest it. When this happens, Apache Oak does a session
save that never seem to return and can easily take 8 hours to terminate.
I suggest to detect those large packages, based on the package size and simply
reject packages above a configurable limit size. The limit should take in
consideration the mean import throughput for a single Oak session on cloud
segment tar and should keep the save operation below, say 15 minutes.
With this approach, we can ensure that Oak always return when importing a
package and we can fail fast for larger packages. Journal distribution will
also handle the errors nicely and allow to remove the blocking item from the
usual set of tools.
was:
Journal distribution serialise content packages in binary less mode only. When
doing "deep" distribution, the package can still become so large that the
importing side can't ingest it. When this happens, Apache Oak does a session
save that never seem to return and can easily take 8 hours to terminate.
I suggest to detect those large packages, based on the package size and simply
reject packages above a configurable limit size. The limit should take in
consideration the mean import throughput for a single Oak session on cloud
segment tar and should keep the save operation below, say 15 minutes.
> Reject large packages
> ---------------------
>
> Key: SLING-10528
> URL: https://issues.apache.org/jira/browse/SLING-10528
> Project: Sling
> Issue Type: Bug
> Components: Content Distribution
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Priority: Major
> Fix For: Content Distribution Journal Core 0.1.18
>
>
> Journal distribution serialise content packages in binary less mode only.
> When doing "deep" distribution, the package can still become so large that
> the importing side can't ingest it. When this happens, Apache Oak does a
> session save that never seem to return and can easily take 8 hours to
> terminate.
> I suggest to detect those large packages, based on the package size and
> simply reject packages above a configurable limit size. The limit should
> take in consideration the mean import throughput for a single Oak session on
> cloud segment tar and should keep the save operation below, say 15 minutes.
> With this approach, we can ensure that Oak always return when importing a
> package and we can fail fast for larger packages. Journal distribution will
> also handle the errors nicely and allow to remove the blocking item from the
> usual set of tools.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
