You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: Conflict (409)
Please provide us with the following information:
This issue is for a: (mark with an x)
- [ X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
This doesn't happen consistently, but in some connections it won't close the connection on command. Instead it seems like the client is trying to reference something that already exists. The odd thing is that it does exist, because it should. I'm trying to close it.
NOTE that this happens when closing a connection after all queries have run successfully and returned valid actions.
The actual process is in upload_data which is found in the application here. The upload process works in repl, in some cases, but not others.
I'd love it if there was some way to handle this issue. Any ideas?
I think I may have figured it out. Redesigning and removing many edges seems to have prevented this from happening. However it's difficult to verify.
Is there any way that I can take that id 4fcdf946-a4ca-4232-b5c7-70cc55648438 and look it up somewhere? If there was some process where I can look up the ID and get the offending query that would be really awesome. Is there any way to do this in Azure Cosmos?
This would be especially helpful for large scale (cosmsose sized) operations where it will be difficult to track individual queries.
Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: Conflict (409)
This issue is for a: (mark with an
x
)similar in some ways to this SO issue
Minimal steps to reproduce
This doesn't happen consistently, but in some connections it won't close the connection on command. Instead it seems like the client is trying to reference something that already exists. The odd thing is that it does exist, because it should. I'm trying to close it.
NOTE that this happens when closing a connection after all queries have run successfully and returned valid actions.
Here is a short version of the process:
The actual process is in
upload_data
which is found in the application here. The upload process works in repl, in some cases, but not others.I'd love it if there was some way to handle this issue. Any ideas?
Any log messages given by the failure
Expected/desired behavior
Connection closes. No crash.
OS and Version?
Versions
tried on both:
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: