Skip to content

Conversation

@imeoer
Copy link
Collaborator

@imeoer imeoer commented Nov 3, 2025

When the model CSI driver is deployed as a DaemonSet pod, newly created pod may delete the sock file that the old pod was listening on. If the new pod hasn't started properly yet, this causes a period of service unavailability.

This change adds a check to verify if the sock file exists and is listening, if it is, the new pod will exit with an error.

@gemini-code-assist
Copy link

Summary of Changes

Hello @imeoer, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the robustness of CSI driver upgrades, particularly when deployed as a DaemonSet. It addresses a potential service unavailability issue that could arise if a newly created pod prematurely deletes the active socket of an old pod. By implementing a pre-startup check for an already listening CSI socket, the changes ensure that a new pod will not start and disrupt an active service, thereby facilitating smoother and more reliable upgrades.

Highlights

  • New isSockListening function: Introduced a utility function isSockListening in pkg/server/server.go that checks if a given Unix socket path exists and is actively listening for connections within a specified timeout.
  • Pre-startup CSI Socket Check: Modified the Server.Run method to include a check for an already listening CSI socket. If the server is in node mode and an active CSI socket is detected at the configured endpoint, the new server instance will exit with an error, preventing it from interfering with an existing, active CSI driver.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a check to prevent service disruption during upgrades of the CSI driver. A new function isSockListening is added to verify if a Unix socket is already in use. This check is integrated into the server's startup sequence to exit early if another pod is already listening on the CSI socket. The overall approach is sound and addresses the problem described. I've added a couple of comments with suggestions to improve code clarity and robustness by handling a potential error and removing a magic number.

When the model CSI driver is deployed as a DaemonSet pod, newly created
pod may delete the sock file that the old pod was listening on. If the
new pod hasn't started properly yet, this causes a period of service
unavailability.

This change adds a check to verify if the sock file exists and is
listening, if it is, the new pod will exit with an error.

Signed-off-by: imeoer <[email protected]>
@imeoer imeoer force-pushed the feature-check-csi-sock branch from cc3f989 to 1072882 Compare November 3, 2025 03:00
Copy link

@aftersnow aftersnow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Member

@chlins chlins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@imeoer imeoer merged commit 7d62a09 into modelpack:main Nov 3, 2025
6 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants