[
https://issues.apache.org/jira/browse/SLING-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936387#comment-17936387
]
Christian Schneider commented on SLING-12690:
---------------------------------------------
I discussed that with Jörg. He thinks we can not see a hanging import from the
stack trace.
Still we are working on some automatism to analyze stack traces but we are not
yet sure in what situations they will be helpful.
So indeed I think we can only work with a very large timeout. I thought about a
default of around 3 hours. In any case the feature toggle to skip as well as
the timeout will be a configuration. So we can change the behavior without
further code changes.
> Skip package if import is stuck for too long
> --------------------------------------------
>
> Key: SLING-12690
> URL: https://issues.apache.org/jira/browse/SLING-12690
> Project: Sling
> Issue Type: Improvement
> Components: Content Distribution
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Major
> Fix For: Content Distribution Journal Core 0.5.2
>
>
> When importing a content package we call filevault to import the package into
> oak.
> This is a synchronous call that blocks until the import is finished.
> We have cases where this import takes much longer than expected and causes
> unavailability of replication for other authors.
> We should introduce a maximum time after which we consider the import to be
> failed and mark the package as skipped.
> So if an import takes longer than this defined time we must:
> * Send out a status message to skip the package. So other pods also skip the
> package
> * Mark the offset of the package as processed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
