Error 500 loading status of Geo primary node when replication lag is high
When loading the Geo node status page, I am seeing:
The production.log shows this;
Processing by Admin::GeoNodesController#status as JSON
Parameters: {"id"=>"1"}
Completed 500 Internal Server Error in 50ms (ActiveRecord: 10.6ms | Elasticsearch: 0.0ms)
Sending event a8ddf4845a6b4c68a0a6d76b4452f46f to Sentry
RangeError (637056843872 is out of range for ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Integer with limit 4):
config/initializers/active_record_locking.rb:12:in `_create_record'
lib/gitlab/i18n.rb:47:in `with_locale'
lib/gitlab/i18n.rb:53:in `with_user_locale'
app/controllers/application_controller.rb:334:in `set_locale'
lib/gitlab/middleware/multipart.rb:95:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:18:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only.rb:31:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
Sentry: https://sentry.gitlap.com/gitlab/gitlab-geo-internal-develop-is/issues/119352/
Edited by Stan Hu