-
Notifications
You must be signed in to change notification settings - Fork 245
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
Question: mimic release support #61
Comments
Hi @nuqz. When you see operation not supported, is it only when running the tests? I've seen this too running tests on Mimic, but it was a minor issue that shouldn't affect applications using go-ceph. I have a large pending update that works with Mimic (and fixes those errors), and I'll be merging that soon. As for compatibility, I think you should be fine with the 10.x.y library. The current approach I'm taking is to fix all the outstanding issues with the current code base, which should work with Jewel to Mimic, but has some deprecation warnings with newer libraries. Once that is solid, we'll tag it or create a branch for fixes. Then move forward with breaking changes that would be nice to have. |
@noahdesu No, not only when running tests. I have a program, which works fine with The program is very simple:
Is there anything I should change? Upd: I have added some log messages to the program and now I know where the error occours -
I added these lines to the new Upd. 2: I have changed Upd. 3: Fixed |
Hi @nuqz thanks for this detailed update. just a quick clarification: are you running jewel / mimic mixed (e.g. jewel client mimic server?). it was a little unclear the relation between how you were using jewel and mimic at the beginning of the post. |
@noahdesu, sorry for a huge delay. I'm not sure what is the client in this case. My first cluster was powered by Jewel version inside the virtual machine (VirtualBox). I used After that, when I had new hardware, I deployed a cluster powered by the Mimic release, imported my pool data and updated the The program code remained the same. p.s. I also have a question about performance. There are several goroutines that write information to the pool. What would be better:
|
Hi @nuqz . The go-ceph project now has CI setup for mimic and luminous so we should see any issue now that arise between the two. If you are still running into any mimic issues I'd love to get unit tests created for those issues. Regarding performance, that is a good question. I haven't invested this at all. An io context is thread safe, and in general can be shared by many threads running in the same application assuming they are interacting with the same pool. However, I haven't thought much about how goroutines will effect correctness since they aren't real threads. This is something we need to look at! |
This issue is quite old and appears to be mostly resolved. Thus I am closing the issue to cut down on our backlog of items. Please feel free to reopen the issue or, preferably, open a new issue to discuss the performance topic more. |
Hi everyone. First of all I want to thank you for this useful package.
When I try to use it with mimic release, I get this error:
Operation not supported
. I want to know following things:The text was updated successfully, but these errors were encountered: