Cannot expire connection, it is not currently leased

[bharathiraja-mallow]

Steps to reproduce

Recently, we have added apartment gem for our multiple schema usecase in postgres. It was working smoothly for some days. Usually we receive a high traffic in our sidekiq server on month end. In that time, things are started getting break and facing the below error on ActiveJobs

ActiveRecord::ActiveRecordError: Cannot expire connection, it is not currently leased.

Once this error is raised, that particular job is moved to retry set in sidekiq and reprocessed again. However, it isn't complete. It reaches the maximum retry count and gets shifted to dead state

Can anyone from this community share your thoughts on this? Would help a lot to us

• Database: Postgresql 13.15

• Apartment version: 2.9.0

• Apartment config (in config/initializers/apartment.rb or so):

  • use_schemas: (true)

• Rails (or ActiveRecord) version: 5.0.3

• Ruby version: 2.4.10

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.