Skip to content
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

add separate server info file paths for services on client side #1494

Merged
merged 50 commits into from
Feb 21, 2024
Merged

add separate server info file paths for services on client side #1494

merged 50 commits into from
Feb 21, 2024

Conversation

ayildirim21
Copy link
Member

Implement #1456 on client side

@ayildirim21 ayildirim21 marked this pull request as draft February 8, 2024 02:14
@KeranYang
Copy link
Member

@a3hadi , with this change, the platform stops supporting all the old UDF images (hence all e2e fail.). Users have to re-build UDF/Source/Sink images using the latest SDKs. Since server info hasn't been widely used, let's see if we can update on the platform side in a way that when a server info file is not found because of incompatible file path, the platform numa container can decide to ignore it and continue processing.

@KeranYang
Copy link
Member

@a3hadi , could you also look into why the udsource e2e succeeded? Thanks!

@ayildirim21
Copy link
Member Author

@a3hadi , with this change, the platform stops supporting all the old UDF images (hence all e2e fail.). Users have to re-build UDF/Source/Sink images using the latest SDKs. Since server info hasn't been widely used, let's see if we can update on the platform side in a way that when a server info file is not found because of incompatible file path, the platform numa container can decide to ignore it and continue processing.

I think ignoring incompatible server info path, with a message to remind to upgrade sdk is a good idea (since using the new server info paths isn't mission critical to continue processing anyways). I will focus on getting the current tests to pass first and then look into this.

@ayildirim21
Copy link
Member Author

After discussing with Keran, I think the best course of action for the "error handling" is simply, if the server info file path is not found, set it to the default path of /var/run/numaflow/server-info. This is because, the server info file will always be created. However there are two possible paths that it can have. If an old sdk version is being used it will be the aforementioned default path, if the sdk version is up to date it will be using the new isolated paths for each service. Thus falling back to the default path when the server info file path is not found will accommodate older sdk versions.

@ayildirim21 ayildirim21 marked this pull request as ready for review February 14, 2024 15:49
@ayildirim21 ayildirim21 marked this pull request as draft February 14, 2024 15:54
@ayildirim21 ayildirim21 marked this pull request as ready for review February 20, 2024 16:24
pkg/sdkclient/mapper/client.go Outdated Show resolved Hide resolved
pkg/sdkclient/options.go Outdated Show resolved Hide resolved
test/diamond-e2e/testdata/join-on-reduce-pipeline.yaml Outdated Show resolved Hide resolved
Copy link
Member

@KeranYang KeranYang left a comment

Choose a reason for hiding this comment

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

LGTM. Please add back the interface check and then we can merge this in.

pkg/sdkclient/sinker/client.go Show resolved Hide resolved
pkg/sdkclient/source/client.go Show resolved Hide resolved
@KeranYang KeranYang merged commit 37a9d5d into numaproj:main Feb 21, 2024
20 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.

2 participants