You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I managed to get makara working (at least it seems to be working so far) but I've got a pesky warning
DEPRECATION WARNING: new is deprecated and will be removed from Rails 7.2 (use ActiveRecord::ConnectionAdapters::SchemaReflection instead)
caused by this line lib/active_record/connection_adapters/makara_abstract_adapter.rb:193
I have no real idea how the makara magic works but I noticed there wasn't an issue opened with this problem, thanks for the hard work 🙏
Also out of curiosity, I can't seem to get automatic failover to master working in a specific case, I want to failover on ActiveRecord::RecordNotFound exception to take into account replication lag in jobs (I configured my jobs to not stick to primary so I could prioritize using the replica database as much as possible until they do a write but some jobs are enqueued right after a create to the database and for those I would like to be able to fallback to the primary database)
The text was updated successfully, but these errors were encountered:
I managed to get makara working (at least it seems to be working so far) but I've got a pesky warning
caused by this line
lib/active_record/connection_adapters/makara_abstract_adapter.rb:193
I have no real idea how the makara magic works but I noticed there wasn't an issue opened with this problem, thanks for the hard work 🙏
Also out of curiosity, I can't seem to get automatic failover to master working in a specific case, I want to failover on
ActiveRecord::RecordNotFound
exception to take into account replication lag in jobs (I configured my jobs to not stick to primary so I could prioritize using the replica database as much as possible until they do a write but some jobs are enqueued right after a create to the database and for those I would like to be able to fallback to the primary database)The text was updated successfully, but these errors were encountered: