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

Sporadically pyocf Queue will raise RuntimeException in test #660

Open
jfckm opened this issue Feb 17, 2022 · 1 comment
Open

Sporadically pyocf Queue will raise RuntimeException in test #660

jfckm opened this issue Feb 17, 2022 · 1 comment
Labels
bug Something isn't working P2-medium
Milestone

Comments

@jfckm
Copy link

jfckm commented Feb 17, 2022

Description

Sometimes in test logs there would be an exception raised by queue object serving the role of management queue. This exception is caused by calling .join() by thread on itself, which means that last ocf_queue_put is called from code executed on this queue which shouldn't happen. Most possibly it is an error with pyocf handling of queue lifetime.

@jfckm jfckm added bug Something isn't working P3-low and removed P3-low labels Feb 17, 2022
@jfckm jfckm added this to the 21.12 milestone Feb 24, 2022
@jfckm jfckm modified the milestones: 21.12, Future Feb 24, 2022
@arutk
Copy link
Contributor

arutk commented Mar 2, 2022

I assume the problem is with management queue.

OCF cache does not put management queue on stop. It is adapter responsibility to put management queue after cache is stopped. Typically this must not be done from outside of cache stop completion callback, as this might run in management queue context.

I don't understand what triggers the problematic queue_put(). This remains to be investigated.

@jfckm jfckm modified the milestones: Future, 22.9 Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2-medium
Projects
None yet
Development

No branches or pull requests

2 participants