debian-mirror-gitlab/app/models/postgresql/replication_slot.rb

44 lines
1.5 KiB
Ruby
Raw Normal View History

2018-11-18 11:00:15 +05:30
# frozen_string_literal: true
module Postgresql
2019-07-07 11:18:12 +05:30
class ReplicationSlot < ApplicationRecord
2018-11-18 11:00:15 +05:30
self.table_name = 'pg_replication_slots'
2018-12-13 13:39:08 +05:30
# Returns true if there are any replication slots in use.
# PostgreSQL-compatible databases such as Aurora don't support
# replication slots, so this will return false as well.
def self.in_use?
transaction { exists? }
rescue ActiveRecord::StatementInvalid
false
end
2018-11-18 11:00:15 +05:30
# Returns true if the lag observed across all replication slots exceeds a
# given threshold.
#
# max - The maximum replication lag size, in bytes. Based on GitLab.com
# statistics it takes between 1 and 5 seconds to replicate around
# 100 MB of data.
def self.lag_too_great?(max = 100.megabytes)
2018-12-13 13:39:08 +05:30
return false unless in_use?
2018-11-18 11:00:15 +05:30
lag_function = "#{Gitlab::Database.pg_wal_lsn_diff}" \
"(#{Gitlab::Database.pg_current_wal_insert_lsn}(), restart_lsn)::bigint"
# We force the use of a transaction here so the query always goes to the
# primary, even when using the EE DB load balancer.
sizes = transaction { pluck(lag_function) }
2019-09-30 21:07:59 +05:30
too_great = sizes.compact.count { |size| size >= max }
2018-11-18 11:00:15 +05:30
# If too many replicas are falling behind too much, the availability of a
# GitLab instance might suffer. To prevent this from happening we require
# at least 1 replica to have data recent enough.
if sizes.any? && too_great.positive?
(sizes.length - too_great) <= 1
else
false
end
end
end
end