why timeout

The job was aborted – it is processed by server ec2amaz-7rmrqt0:15752:7e172ca1-13f9-450a-a397-a80fc1c9cdd6 which is not in the [active servers](http://localhost:7886/job/servers) list for now. It will be retried automatically after invisibility timeout, but you can also re-queue or delete it manually.

Aborted servers will be removed automatically
Some of the servers don't have heartbeat reported within the last minute and may be aborted. If they don't report heartbeat in the near future, they will be removed automatically after timeout is exceeded, no manual action is required. Incomplete background jobs running on those servers will be re-queued automatically, but you can speed up the process by checking the [Processing Jobs](http://localhost:7886/job/jobs/processing) page.


Start with the Processing Jobs page and the active servers list described in the report, then trace how heartbeat loss, server removal, and invisibility-timeout retries relate. The issue names no source files or tests and does not state a requested change; done would require defining the suspected timeout behavior and adding a reproducible regression test or clarified documentation.

Written by the indexing model from the issue text.