oneapi-src / oneapi-src/oneAPI-samples
Modin fail on CORE (GEN13 i9)
还没有人认领这个 Issue。
- 主要语言
- C++
- 星标
- 1.2k
- 派生
- 745
- PR 合并指标
- 30 天内没有已合并 PR
描述
Summary
When I try to installed oneAPI base toolkit and test the MODIN sample apps:
https://github.com/oneapi-src/oneAPI-samples/tree/master/AI-and-Analytics/Getting-Started-Samples/IntelModin_GettingStarted
Then detected error below:
(raylet) [2023-10-10 22:04:54,885 E 21639 21688] (raylet) agent_manager.cc:135: The raylet exited immediately because the Ray agent failed. The raylet fate shares with the agent. This can happen because the Ray agent was unexpectedly killed or failed. Agent can fail when
(raylet) - The version of grpcio doesn't follow Ray's requirement. Agent can segfault with the incorrect grpcio version. Check the grpcio version pip freeze | grep grpcio.
(raylet) - The agent failed to start because of unexpected error or port conflict. Read the log cat /tmp/ray/session_latest/dashboard_agent.log. You can find the log file structure here https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure.
(raylet) - The agent is killed by the OS (e.g., out of memory).
Version
oneAPI toolkit version: 2023.2.0
Environment
OS is Linux uBuntu 22.04.2 LTS
CPU: 13th Gen Intel(R) Core(TM) i9-13900
RAM: 32GB
Steps to reproduce
Using the conda running the MODIN sample apps that released by oneAPI:
https://github.com/oneapi-src/oneAPI-samples/tree/master/AI-and-Analytics/Getting-Started-Samples/IntelModin_GettingStarted
Observed behavior
Detected the raylet fail like below log:
(raylet) [2023-10-10 22:04:54,885 E 21639 21688] (raylet) agent_manager.cc:135: The raylet exited immediately because the Ray agent failed. The raylet fate shares with the agent. This can happen because the Ray agent was unexpectedly killed or failed. Agent can fail when
(raylet) - The version of grpcio doesn't follow Ray's requirement. Agent can segfault with the incorrect grpcio version. Check the grpcio version pip freeze | grep grpcio.
(raylet) - The agent failed to start because of unexpected error or port conflict. Read the log cat /tmp/ray/session_latest/dashboard_agent.log. You can find the log file structure here https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure.
(raylet) - The agent is killed by the OS (e.g., out of memory).
Expected behavior
I tested on XEON is working, but CORE product not working as same setup.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先从 AI-and-Analytics/Getting-Started-Samples/IntelModin_GettingStarted 中的 conda 环境和示例开始,然后在列出的 Ubuntu 和 Core i9 配置上复现 Raylet 故障。检查报告的 grpcio 版本和 /tmp/ray/session_latest/dashboard_agent.log,并将结果与正常工作的 Xeon 配置进行比较;当示例能够在 Core 系统上运行,或不兼容性已得到明确记录时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- data
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100