There are various options you can use to tune the HikariCP, but they aren't useful until you investigate what's causing the problem.
So I suggest first attaching a profiler and investigating (looking at CPU HotSpots, memory, stack traces etc) where the problem actually lies. Once you've identified the place, we can go from there.
At start, we creating some indices.
For each entry in the indices, he ask the database, if the node is still present or not.
He is doing this one by one.
Is there any possibility to do this parallel?
i talked today with our chief architekt and he investigated this issue.
We identified an unused index, which ask every "nt:base"-nodes, that's stupid as hell.
So we deleted this index and restarted the modeshape-server. Now he is indexing again.
Looks like the problem is solved.
glad you sorted it out.
In general, you can control the reindexing behavior via a "reindexing" section in the configuration. See Query and search - ModeShape 5 - Project Documentation Editor for more details.