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

[exporter/datasetexporter]: Call the currect function on shutdown #9

Merged

Conversation

martin-majlis-s1
Copy link
Collaborator

@martin-majlis-s1 martin-majlis-s1 commented Jul 13, 2023

Description: When exporter is shutting down, we have to call the correct shutdown function.

We have introduced new function that should be called during the shutdown but we haven't updated the datasetexporter code.

Link to tracking Issue: open-telemetry#24253

Testing:

Documentation:
see also https://github.com/scalyr/dataset-go/pull/30/files

Copy link
Collaborator

@tomaz-s1 tomaz-s1 left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Do we have corresponding end to end tests for that / we plan to add it now, have a separate JIRA ticket for it or similar?

@martin-majlis-s1
Copy link
Collaborator Author

This is the following task - https://sentinelone.atlassian.net/browse/DSET-4050 and I am planning to verify it. For now I do not know, how to verify it, that it's work as expected, that would really convince me. So I will do some best effort.

@tomaz-s1
Copy link
Collaborator

@martin-majlis-s1 One easy quick manual way could be to test it with the helm chart / Kubernetes.

Create new helm chart deployment, send some data, stop sending data, run helm upgrade to upgrade the app.

This will result in new app roll out (old pod will be and new one created). If the change is working correctly, old pod should stop fast (since no data is flowing in) and Kubernetes shouldn't need wait up to 60 seconds / configured grace period before killing the pod.

Keep in mind though that this only covers simple "no data is flowing in" path. It would still be nice to also test data is flowing in and new data is being rejected flow.

@tomaz-s1
Copy link
Collaborator

I actually assume you wanted to create this branch against datasetexporter-latest branch and not the main one, or?

@martin-majlis-s1 martin-majlis-s1 changed the base branch from main to datasetexporter-latest July 14, 2023 08:01
@martin-majlis-s1 martin-majlis-s1 merged commit 0bf4013 into datasetexporter-latest Jul 17, 2023
86 of 88 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