I thought this might bring more awareness to the fact that the rolling_indexer should be running, and give more confirmation. An argument can be made that this is NOT useful. I didn't realize we had capistrano tasks for the rolling_indexer. Maybe everyone else knows that. Maybe this isn't a way to raise awareness.
Capistrano log in my terminal window AFTER
01 Restarting /opt/app/dor_indexer/dor_indexing_app/current (production)
β 01 dor_indexer@dor-indexing-app-qa-b.stanford.edu 0.310s
01:55 rolling_indexer:start
01 sudo systemctl start rolling-index
β 01 dor_indexer@dor-indexing-app-qa-a.stanford.edu 1.600s
02 sudo systemctl status rolling-index
02 β rolling-index.service - rolling-index
02 Loaded: loaded (/etc/systemd/system/rolling-index.service; enabled; vendor preset: enabled)
02 Active: active (running) since Mon 2024-01-08 12:21:57 PST; 171ms ago
02 Process: 2991935 ExecStart=/bin/bash -lc exec bin/rolling_index start (code=exited, status=0/SUCCESS)
02 Main PID: 2992029 (ruby)
02 Tasks: 2 (limit: 9475)
02 Memory: 102.1M
02 CGroup: /system.slice/rolling-index.service
02 ββ2992029 rolling_index
02
02 Jan 08 12:21:56 dor-indexing-app-qa-a.stanford.edu systemd[1]: Starting rolling-index...
02 Jan 08 12:21:57 dor-indexing-app-qa-a.stanford.edu bash[2991935]: [DEPRECATION] openapi_parser will default to strict reference validation from next version. Pass config `strict_reference_valiβ¦
02 Jan 08 12:21:57 dor-indexing-app-qa-a.stanford.edu bash[2991935]: rolling_index: process with pid 2992029 started.
02 Jan 08 12:21:57 dor-indexing-app-qa-a.stanford.edu systemd[1]: Started rolling-index.
β 02 dor_indexer@dor-indexing-app-qa-a.stanford.edu 0.194s
01:57 sneakers_systemd:start
01 sudo systemctl start sneakers
β‘ β If this change has cross service impact, run integration tests that exercise indexing (e.g. searches in Argo for newly created/updated items, access_indexing_spec) and/or test in [stage|qa] environment, in addition to specs. β‘
Why was this change made? π€
I thought this might bring more awareness to the fact that the rolling_indexer should be running, and give more confirmation. An argument can be made that this is NOT useful. I didn't realize we had capistrano tasks for the rolling_indexer. Maybe everyone else knows that. Maybe this isn't a way to raise awareness.
Capistrano log in my terminal window AFTER
Capistrano log in my terminal window BEFORE
How was this change tested? π€¨
β‘ β If this change has cross service impact, run integration tests that exercise indexing (e.g. searches in Argo for newly created/updated items, access_indexing_spec) and/or test in [stage|qa] environment, in addition to specs. β‘