[GitHub] ignite pull request #2281: ignite-5722 Cache entries stay in onheap after sc...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] ignite pull request #2281: ignite-5722 Cache entries stay in onheap after sc...

ascherbakoff
GitHub user agura opened a pull request:

    https://github.com/apache/ignite/pull/2281

    ignite-5722 Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/agura/incubator-ignite ignite-5722-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2281.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 #2281
   
----
commit b5ecd3e00d34a465d0fedeaedf7813722e1680b3
Author: agura <[hidden email]>
Date:   2017-07-11T13:24:54Z

    ignite-5722 Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] ignite pull request #2281: ignite-5722 Cache entries stay in onheap after sc...

ascherbakoff
Github user agura closed the pull request at:

    https://github.com/apache/ignite/pull/2281


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...