ff3ceb981e
If a process is violently terminated, the associated file storage may get stuck in the ephemeral 'NEW' state, preventing future operations on the associated data. To remedy this without having to dig through the database, a button was added to reset the state. It's a band-aid, but the situation is rare enough that I think it's fine. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| readme.md | ||
Control Service
The control service provides an operator's user interface. By default this interface is exposed on port 8081. It does not offer any sort of access control or authentication.
The control service will itself execute tasks that affect the entire system, but delegate node-specific tasks to the corresponding executor-service via the executor-api.
Conceptually the application is broken into three parts:
- Application specific tasks relate to the high level abstractions such as blacklisting and API keys
- System tasks relate to low level abstractions such as the message queue and event log.
- Node tasks relate to index node specific tasks, such as crawling and indexing.
Central Classes
See Also
- processes
- libraries/message-queue - The Message Queue and Actor abstractions