-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] make system core_pattern
more smarter for container
#178
Comments
core_pattern
more smarter for containercore_pattern
more smarter for container
|
core_pattern
more smarter for containercore_pattern
more smarter for container
请问为什么 “系统和容器只能共享一个 core_pattern 一个配置”呢 |
系统和容器只能共享一个 core_pattern,这是因为 core_pattern 是一个内核参数,它决定了当进程崩溃时,系统如何生成和存储 core 文件。core_pattern 是一个全局的设置,它不能被每个容器单独配置,而是由宿主机统一管理。如果容器中的进程崩溃,它会使用宿主机的 core_pattern 来生成 core 文件,并且将其存储在宿主机的文件系统中 |
Hello, I am a student from Hunan University. My major is Software Engineering. I am familiar with C++ and Golang, and I am very interested in cloud-native and storage systems. My technical strengths include C++ server development and kernel virtualization techniques. I chose this issue because I have some understanding of curveadm and want to gain a deeper understanding of curveadm through the process of completing the issue. I am confident in completing this topic, and I have previously submitted two PRs to the community: |
welcome! |
core 文件是排查问题的重要依据来源,目前我们可以在配置文件中配置
core_dir
将容器内存储 core 文件的目录映射到宿主机上。但是目前存在的问题是:core_pattern
一个配置,如果系统所设置的 core_pattern 在容器内没有对应的目录,会导致无法生成 core 文件core_pattern
设置为/core/xxx
,并且在容器内提前创建了 /core 目录由于以上的限制,导致我们的 core 设置生成变得有些麻烦,常常因为用户没有设置 core_pattern 为
/core
的前缀导致 core 生成失败。我们希望你能帮助我们改进这个机制,用户只需要配置
core_dir
配置,curveadm 帮助自动适配系统目前的 core_pattern 以生成 core 文件。这也许有些挑战,但是这对我们帮助很大 :)Registration procedure
Step 1. Add a comment when you sign up.The purpose of comments is for us to understand you and determine whether you have the basic ability to complete this issue.
Step 2. Use WeChat to add the Curve community assistant "Curve" as a WeChat friend, tell your GitHub ID, and send the Issue link of your choice. The assistant will invite you to communicate with the mentor by WeChat.
Step 3. In order to better complete each development task, the mentor will select the developer who best matches the issue based on everyone's comment on GitHub and communication status by WeChat. If you are not selected, please select another issue.
Tips
The text was updated successfully, but these errors were encountered: