[
https://issues.apache.org/jira/browse/IGNITE-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480589#comment-16480589
]
ASF GitHub Bot commented on IGNITE-7818:
----------------------------------------
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/4024
IGNITE-7818
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite IGNITE-7818
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4024.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 #4024
----
commit bd5fce8c99477abaabe5d3242d5a95c5b7988920
Author: Fedotov <vanen31@...>
Date: 2018-05-08T09:21:05Z
change javaDoc in IgniteDataStreamer
commit 833a468aa5a05c478bf1231f313692d496f879c1
Author: Fedotov <vanen31@...>
Date: 2018-05-18T12:18:24Z
remove assertion
----
> Incorrect assertion in PDS page eviction method
> -----------------------------------------------
>
> Key: IGNITE-7818
> URL: https://issues.apache.org/jira/browse/IGNITE-7818
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Aleksey Plekhanov
> Assignee: Ivan Fedotov
> Priority: Major
>
> There is an assertion in the method
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.Segment#removePageForReplacement:
>
> {code:java}
> assert relRmvAddr != INVALID_REL_PTR;{code}
> Which seems potentially dangerous. In some rare cases, when count of
> interations more then 40% of allocated pages and all processed pages are
> aquired, the {{relRmvAddr}} variable will be uninitialized and
> {{AssertionException}} will be thrown. But it's a correct case and page to
> evict can be found later in the method {{tryToFindSequentially.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
