[BUG] HikariDataSource HikariDataSource (HikariPool-1) has been closed about jobrunr

[rdehuyss]

You can find everything when you create an issue (it's the text before the fields)

[dilipdhankecha2530]

@rdehuyss I'm setting up the scenario in our local environment, trying to replicate it. Once everything's ready, I'll keep you posted on the progress.

[rdehuyss]

In case of such an exception, the dashboard allows you to create automatically a github issue so we can diagnose the root cause. See the video at https://www.jobrunr.io/en/blog/2021-02-07-v1.3. Without that, I'm afraid we cannot help.

Also, the Orphaned job means either a server died or a stop the world garbage collection happens for a long period. Also this is mentioned on the Dashboard page.

We test JobRunr regularly with 10 million jobs and Thread.sleep and that works without any problems.

[rdehuyss]

@dilipdhankecha2530 - although I also saw this issue in the last weeks, we just tried to reproduce it but are unable to do so (we created a long running job and hikari waits until the server has shutdown correctly).

Can you reproduce it easily?

[dilipdhankecha2530]

@rdehuyss
We can't seem to replicate this issue locally. It seems to occur only on the server where we deploy the application with k8s, with specific configurations: 3Gi memory max and 1 core CPU.
This issue we faced after introduce the Jobrunr.

[rdehuyss]

Without a way to reproduce it, is going to be hard to fix....

[rdehuyss]

Please also update your GitHub profile like requested in the JobRunr community guidelines...

[dilipdhankecha2530]

@rdehuyss Could you please provide suggestion what i have to do for the Github profile?

[rdehuyss]

Cool, thx for updating your profile. Any luck on a way to reproduce it? We can not reproduce it in K8S either.

[dilipdhankecha2530]

@rdehuyss During the testing i faced another issue.

This issue occurred during the processing of the large amount. So we have 100k records to process and we use multi threading here. During the processing we use the 10 seconds Thread sleep.
It's cause the issue during the processing. I assume jobrunr is not able to manage the thread properly but i am also not sure.

[rdehuyss]

Which DB are you using?

[dilipdhankecha2530]

Postgres DB

[dilipdhankecha2530]

I'm attempting to replicate the issue with my application setup in Kubernetes, but I'm still unable to do so.

[uben01]

It also happens to use, like every week for the last month or so.

We've no longer got any logs about it, but if it occurs again, I'll let you know. I assumed it was because of the CloudSQL maintenance but I might be wrong here.

[rdehuyss]

Indeed, this looks more related to your database / Hikari timing out then to JobRunr.

We also are still looking but were not able to reproduce it...