[
https://issues.apache.org/jira/browse/UIMA-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624995#action_12624995
]
Burn Lewis commented on UIMA-1146:
----------------------------------
>> When used with Uima AS primitives, "scaleout" means to replicate instances
>> of analysis components. Overloading "scaleout" to refer to replicating some
>> threads in an aggregate will result in unnecessary confusion.
What we're discussing here is scaling out the work done by the aggregate
controller in dispatching CASes to its delegates ... probably the bulk of the
work of an async aggregate. But I agree it is confusing since in the sync case
the aggregate load is the aggregate of its delegates. So we would need to be
clear that we're scaling out the controller dispatch work, just as in the
proposal above we're scaling out work done when servicing the 3 types of queues.
>> Individual remote reply queues still need to be scaled (see UIMA-1130)
1130 solves the load problem when processing remote replies and has the nice
side-effect of providing a type of pre-fetch. As Eddie has pointed out my
suggestion of a single "fast" consumer of a remote queue would not be as good
since each reply would still be delayed by the handshaking with the broker.
Since the need for pre-fetch is somewhat separate from the load issue that
originally motivated 1130 one (ugly) solution would be to restore the
non-standard prefetch parameter, and implement it with multiple consumers on
WebSphere. But there goes my hope for fewer tuning parameters! Ugh.
> Setting the number of concurrent listeners of a reply queue for Co-located
> Delegates
> ------------------------------------------------------------------------------------
>
> Key: UIMA-1146
> URL: https://issues.apache.org/jira/browse/UIMA-1146
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.2.2AS
> Reporter: Tong Fin
> Assignee: Tong Fin
>
> JIRA-1130 has improved UIMA-AS to allow users to set the number of concurrent
> listeners of a reply queue for each "remote" delegate. The following is the
> syntax in the xml deployment descriptor (as an example):
> <analysisEngine async="true">
> <delegates>
> <remoteAnalysisEngine key="RoomNumber">
> <inputQueue brokerURL="tcp://localhost:61616"
> endpoint="RoomNumberAnnotatorQueue"/>
> <replyQueue concurrentConsumers="2" location="remote"/>
> ...
> </remoteAnalysisEngine>
> </delegates>
> ...
> </analysisEngine>
> This JIRA will do the similar thing by allowing users to set the number of
> concurrent listeners of a reply queue for "co-located" delegates inside the
> UIMA-AS aggregate.
> The following is the "proposed" syntax:
> <analysisEngine async="true"> <!-- Top aggregate -->
> <replyQueue concurrentConsumers="2">
> ...
> <delegates>
> <analysisEngine key="NamesAndPersonTitlesTAE" async="true"> <!--
> co-located aggregate -->
> <replyQueue concurrentConsumers="3">
> ...
> </analysisEngine>
> ...
> </delegates>
> ...
> </analysisEngine>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
