[
https://issues.apache.org/jira/browse/OAK-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933357#comment-17933357
]
Daniel Iancu edited comment on OAK-11564 at 3/7/25 3:27 PM:
------------------------------------------------------------
I have fixed the issue and tested _--entireRepo_ with and without _--continuous_
Also tested _--path_ ... with/without _--continuous_
When _--continous_ is not present, oak-run will finish and not hang forever
was (Author: diancu):
I have fixed the issue and tested _--entireRepo_ with and without _--continuous_
Also tested _--path ..._ with _--continuous_
> oak-run FullGC leaves background threads running
> ------------------------------------------------
>
> Key: OAK-11564
> URL: https://issues.apache.org/jira/browse/OAK-11564
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Daniel Iancu
> Priority: Major
>
> If we run with --continuous argument, it will run _forever_ like inside a
> normal author pod it would (which could be what we want). Without
> --continuous it seems to run just one iteration and then stop
>
> It seems after doing one iteration (and then the process should stop) it
> doesn't, it doesn't dispose entirely the connection to DocumentNodeStore and
> leaves a background thread node still running forever, instead of terminating
> the process
>
> I think there is a bit of overlap between --entireRepo and --continuous
> arguments, and probably doesn't make sense to run --entireRepo without
> --continuous.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
