MissionControl seems to be using production.rb's queue database instead of development

[gczh]

I'm trying to figure out if there is any way to determine the database that MissionControl is connected to. At the moment, what seems to be the case is this:

When running SolidQueue::Job.connection.raw_connection in rails console, it seems to be using the local database configured in database.yml

development:
  primary:
    <<: *default
    database: rails_app_development
  external:
    url: <%= ENV["EXTERNAL_DATABASE_URL"] %>
    database_tasks: false
    replica: true
  queue:
    <<: *default
    database: rails_app_development_queue
    migrations_paths: db/queue_migrate
    
production:
  primary:
    <<: *default
    database: rails_app_production
    url: <%= ENV["DATABASE_URL"] %>
  external:
    url: <%= ENV["EXTERNAL_DATABASE_URL"] %>
    database_tasks: false
    replica: true
  queue:
    <<: *default
    url: <%= ENV["QUEUE_DATABASE_URL"] %>
    database: rails_app_production_queue
    migrations_paths: db/queue_migrate

However, when I look at website.com/jobs and localhost:3000/jobs, it seems that the number of jobs completed is exactly the same. This leads me to believe that the MissionControl on localhost is actually pointing to the QUEUE_DATABASE_URL in database.yml

However, even after commenting out that in .env, it still seems to be connecting to the remote queue database.

Other notes

Looks like if I were to comment out the queue database configuration for production in database.yml, MissionControl would then point to development's database correctly.

I undid the comments after restarting the server, and it's still pointing to the local db, which is the correct and expected behaviour. This makes me wonder if MissionControl is caching database connections somehow?

[rosa]

Huh, no, this is very strange. Mission Control doesn't do anything with DB connections, it relies solely on Solid Queue's connections, so it uses whatever Solid Queue is using. I haven't seen anything like this before. Are you manually configuring Mission Control's applications or relying on the default configuration?

[gczh]

Huh, no, this is very strange. Mission Control doesn't do anything with DB connections, it relies solely on Solid Queue's connections, so it uses whatever Solid Queue is using. I haven't seen anything like this before. Are you manually configuring Mission Control's applications or relying on the default configuration?

Ahhh, gotcha! This is what it looks like for me in development.rb

  config.active_job.queue_adapter = :solid_queue
  config.solid_queue.connects_to = { database: { writing: :queue, reading: :queue } }
  config.solid_queue.logger = ActiveSupport::Logger.new(STDOUT, level: :debug)
  config.log_level = :debug

[rosa]

Hey @gczh, did you figure out what you were seeing here?

[MyklClason]

I'm seeing something similar, though may not be the same issue. I set up solid queue and mission control jobs a while back, and they seemed to be fine, but when I set it up this time, my dev environment only showed 2 tabs (Queues and Failed jobs) with no change occurring when processing jobs (though they do process just fine). However, when I push to Heroku, it shows all the expected tabs and seems to be showing progress as expected.

[rosa]

when I set it up this time, my dev environmentnt only showed 2 tabs (Queues and Failed jobs) with no change occurring when processing jobs (though they do process just fine)

Oh, this sounds like you didn't configure Solid Queue in development, but the async adapter, that can't really work with Mission Control because jobs are run in memory 🤔