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

Unsynchronized WriteAPIBlocking.Write* functions #208

Closed
vlastahajek opened this issue Oct 27, 2020 · 3 comments · Fixed by #209
Closed

Unsynchronized WriteAPIBlocking.Write* functions #208

vlastahajek opened this issue Oct 27, 2020 · 3 comments · Fixed by #209
Assignees
Labels
bug Something isn't working
Milestone

Comments

@vlastahajek
Copy link
Contributor

WriteAPIBlocking.WritePoint and WriteAPIBlocking.WriteRecord must ensure synchronized calling of write.Service.HandleWrite

@vlastahajek vlastahajek self-assigned this Oct 27, 2020
@vlastahajek vlastahajek added the bug Something isn't working label Oct 27, 2020
@vlastahajek vlastahajek added this to the v2.2.0 milestone Oct 27, 2020
@ridwankustanto
Copy link

I have problem with writing data to influxdb, there is no error anywhere, but I checked the bucket, the data not sent. Is it because of this bug? I tried with WriteAPIBlocking.WritePoint and WriteAPI.WritePoint but no luck.

@vlastahajek
Copy link
Contributor Author

@ridwankustanto, your problem is most probably somewhere else. The race condition here could happen in the specific condition when data is written by multiple goroutines and the server is overloaded and returns an error.

How do you check the data is written?
Do you write data with a timestamp?

@ridwankustanto
Copy link

Hi @vlastahajek, ohh I see. I checked the error with both ways (asynchronously and synchronously), I got nothing. But I guess I found the problem and I fixed it. It was my mistake with the timestamp. Thanks for reminding me about that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants