lablup / lablup/backend.ai

Add explicit `ipc-base-path` config to the agent watcher

Open
#1,640 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
17h 7m
Merged PRs (30d)
358

Description

Although we are planning to implement a separate watcher framework, until then, we need to live with [the single-module agent watcher](https://github.com/lablup/backend.ai/blob/main/src/ai/backend/agent/watcher.py).

It currently uses a hard-coded ipc-base-path `/tmp/backend.ai/ipc`, which is the default for other service daemons like storage-proxy, manager, etc.

The problem is that, after #1246, there are cases that agent + agent watcher runs together with storage-proxy, and if storage-proxy's `ipc-base-path` option is left as the default, storage-proxy may fail to initialize the logger socket when the agent watcher starts earlier and creates the ipc directory as the root privilege.

We need to teach the agent watcher to use a separate `ipc-base-path` configuration.In the meanwhile, we could explicitly configure storage-proxy's `ipc-base-path` to other than the default to workaround the issue.

JIRA Issue: BA-185

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.