[
https://issues.apache.org/jira/browse/GEODE-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298313#comment-17298313
]
ASF GitHub Bot commented on GEODE-8943:
---------------------------------------
pivotal-eshu commented on pull request #6075:
URL: https://github.com/apache/geode/pull/6075#issuecomment-794397010
There is a behavior change in transaction with register interest. (From my
understanding this behavior exists from start of the tx implementation).
Now register interest will block transaction commit during the period of
register interest -- esp. on the node performing the register interest from
client.
The performance hit shifts from calculating filterRoutingInfo again on
remote node to no transactions allowed to commit when register interest is
under way.
Also I worry about potential performance hit and even deadlock as the remote
node processing register interest message can be blocked for a while (trying to
get the write lock) while there are concurrent transactions.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Filterrs (Interest and CQ) is processed multiple times with transactional
> operation on PR
> -----------------------------------------------------------------------------------------
>
> Key: GEODE-8943
> URL: https://issues.apache.org/jira/browse/GEODE-8943
> Project: Geode
> Issue Type: Bug
> Components: cq, regions
> Affects Versions: 1.14.0
> Reporter: Anilkumar Gingade
> Assignee: Eric Shu
> Priority: Major
> Labels: blocks-1.14.0, pull-request-available
>
> The Filters (interest and CQ) could be getting processed multiple times when
> transactional operation is performed.
> By design on PR the filters are processed on primary bucket where the data is
> applied/changed and adjunct message with interested clients are sent to
> remote servers (where the subscription queues are hosted) and replicas; thus
> performing filter processing once and sending the message to remote servers
> only if the filters are satisfied; it looks like currently the filter
> processing is happening both at the primary and secondary buckets for TX
> operation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
