[ https://issues.apache.org/jira/browse/IGNITE-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028372#comment-16028372 ]
ASF GitHub Bot commented on IGNITE-5299: ---------------------------------------- GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/2026 IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5299 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2026.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2026 ---- commit 02ebe624a37379055345ae1409918ba96da1d3fc Author: Evgenii Zhuravlev <ezhurav...@gridgain.com> Date: 2017-05-29T13:46:11Z IGNITE-5299 Don't set IgniteLock as broken if lock is failoverSafe ---- > Don't set IgniteLock as broken if lock is failoverSafe > ------------------------------------------------------ > > Key: IGNITE-5299 > URL: https://issues.apache.org/jira/browse/IGNITE-5299 > Project: Ignite > Issue Type: Bug > Reporter: Evgenii Zhuravlev > Assignee: Evgenii Zhuravlev > > It's unnecessary to set isBroken flag to IgniteLock when failoverSafe=true, > because it's only used in case when failoverSafe=false -- This message was sent by Atlassian JIRA (v6.3.15#6346)