[
https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619006#action_12619006
]
Marshall Schor commented on UIMA-1130:
--------------------------------------
Good points, Adam, to consider.
Here are a couple of others (from reading our docs): are there use cases where
the remote delegate would be able to get requests from the remote broker, but
possibly not be able to send it replies? (e.g., due to firewall issues?)
Would it be possible to set the prefetch value for reply queues to be some
fixed number (e.g., 1 or 10 or ... ?) There should only ever be one listener
pulling messages off of the reply queue. Is there a penalty for setting up the
prefetch value to something high?
> Deployment Descriptor should allow setting the number of concurrent listeners
> for a reply queue
> -----------------------------------------------------------------------------------------------
>
> Key: UIMA-1130
> URL: https://issues.apache.org/jira/browse/UIMA-1130
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Adam Lally
>
> The Spring XML allows setting a concurrentConsumers property for a reply
> queue (either an aggregate's collocated reply queue or a remote reply queue):
> <property name="concurrentConsumers" value="1"/>
> The deployment descriptor should allow setting this property. In some
> deployments where remote delegates are scaled out many times, the bottleneck
> can become the aggregate deserializing CASes from the reply queue. If the
> aggregate is running on a multicore machine it helps to increase the number
> of threads that can process the reply queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
