[
https://issues.apache.org/jira/browse/GEODE-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285329#comment-17285329
]
ASF GitHub Bot commented on GEODE-7245:
---------------------------------------
kamilla1201 opened a new pull request #6037:
URL: https://github.com/apache/geode/pull/6037
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, check Concourse for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to d...@geode.apache.org.
----------------------------------------------------------------
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
> Remove most uses of latestViewReadLock in GMSMembershipManager
> --------------------------------------------------------------
>
> Key: GEODE-7245
> URL: https://issues.apache.org/jira/browse/GEODE-7245
> Project: Geode
> Issue Type: Improvement
> Components: membership
> Reporter: Bruce J Schuchardt
> Priority: Major
>
> Changes for GEODE-7196 made the latestView immutable so there is no reason,
> in most cases, to use the latestViewReadlock when accessing the view. A
> simple volatile read of the field & storing the value in a method variable
> can replace most uses of the latestViewReadLock, especially those uses that
> are in the path of sending or receiving messages.
> Performance could be measured with our benchmarks to see if this change helps.
>
> latestViewReadLock is currently used in getCoordinator(), memberExists(),
> getMembersNotShuttingDown(), getAllMembers(), isShunnedOrNew(),
> isSurpriseMember(), doWithViewLocked().
> doWithViewLocked() is used to add membership listeners, and we don't want the
> view to change until this operation completes. Therefore, we should keep the
> lock in this method.
> getCoordinator(), memberExists(), getMembersNotShuttingDown(),
> getAllMembers() use latestViewReadLock to access latestView. In these methods
> we can replace the lock with a volatile read of the latestView and storing
> the value in a method variable.
> isShunnedOrNew() accesses latestView, and 2 ConcurrentHashMaps -
> shunnedMembers and surpriseMembers. Since the hashmaps are concurrent and
> latestView is unmodifiable, a volatile read could replace the lock. Same for
> isSurpriseMember(), which uses surpriseMembers hashmap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
