Re: [PR] Fix a deadlock that can happen when mutliple stages execute parallelly in a worker (druid)

["asdf2014 (via GitHub)" <gi...@apache.org>]

asdf2014 commented on code in PR #16524:
URL: https://github.com/apache/druid/pull/16524#discussion_r1627360761


##########
processing/src/main/java/org/apache/druid/frame/processor/Bouncer.java:
##########
@@ -32,18 +32,45 @@
 
 /**
  * Limiter for access to some resource.
- *
- * Used by {@link FrameProcessorExecutor#runAllFully} to limit the number of outstanding processors.
+ * <p>
+ * The class performs the work of a "bouncer", limiting the number of threads that can concurrently access the guarded
+ * critical sections by the bouncer. The bouncer is initialized with the max number of threads that can enter the
+ * gaurded section(s) at a time.

Review Comment:
   ```suggestion
    * guarded section(s) at a time.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org