osprofiler

Need support multithreading

Bug #1818493 reported by Yang Youseok
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
osprofiler
Confirmed
Undecided
Unassigned

Bug Description

I'm not sure it's bug on the side of osprofiler though, the problem is directly related to this project so I report it here.

in osprofiler/profiler.py, there is a 'threading.local' to avoid race condition among threads. But the problem is that client side using osprofiler like openstacksdk has async API which use python threadpool.

In the openstacksdk, openstack/task_manager.py there is a 'concurrent.futures.ThreadPoolExecutor' which makes the python threads. If client uses this API such as 'network', the client does not append profiling header since profiler does not exist in the thread.

Since both side (openstacksdk, osprofiler) does not care about this inconsistency, it's good time to rethink about the feature.

Thanks.

See original description
Yang Youseok (ileixe)
summary: - Need support multiprocessing
+ Need support multithreading
description: updated
Revision history for this message
Ilya Shakhat (shakhat) wrote :

Related bug: https://storyboard.openstack.org/#!/story/2004580

Changed in osprofiler:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.