[GitHub] ignite pull request #2674: Ignite 5136 GridLogThrottle memory leak

2017-09-15 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2674 Ignite 5136 GridLogThrottle memory leak You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-5136-li Alternatively you

[GitHub] ignite pull request #2557: Ignite 4756 Print info about partition distributi...

2017-08-31 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2557 Ignite 4756 Print info about partition distribution to log You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756-1

[GitHub] ignite pull request #2551: Ignite 4756 Print info about partition distributi...

2017-08-30 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2551 Ignite 4756 Print info about partition distribution to log You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756

[GitHub] ignite pull request #2503: Ignite 4756 Print info about partition distributi...

2017-08-30 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2503 --- 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

[GitHub] ignite pull request #2503: Ignite 4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2503 Ignite 4756 Print info about partition distribution to log. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756

[GitHub] ignite pull request #2502: Ignite-4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2502 --- 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

[GitHub] ignite pull request #2500: Ignite 4756 updated

2017-08-23 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2500 --- 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

[GitHub] ignite pull request #2502: Ignite-4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2502 Ignite-4756 Print info about partition distribution to log. Added tests, printDistribution method, IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD system property. You can merge this pull request

[GitHub] ignite pull request #2500: Ignite 4756 updated

2017-08-23 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2500 Ignite 4756 updated You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756-updated Alternatively you can review and

[GitHub] ignite pull request #2499: Ignite 4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2499 --- 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

[GitHub] ignite pull request #2499: Ignite 4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2499 Ignite 4756 Print info about partition distribution to log You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756

[GitHub] ignite pull request #2435: Ignite 4756 Print info about partition distributi...

2017-08-23 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2435 --- 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

[GitHub] ignite pull request #2435: Ignite 4756

2017-08-11 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2435 Ignite 4756 Added printDistribution method and AbstractAffinityFunctionSelfTest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski

[GitHub] ignite pull request #2427: Ignite 4756

2017-08-11 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2427 --- 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

[GitHub] ignite pull request #2427: Ignite 4756

2017-08-10 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2427 Ignite 4756 Added calculate printDistribution method and AffinityDistributionPrintLogTest. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #2413: Ignite 4756 m

2017-08-08 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/2413 --- 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

[GitHub] ignite pull request #2413: Ignite 4756 m

2017-08-08 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2413 Ignite 4756 m You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4756-m Alternatively you can review and apply these

[GitHub] ignite pull request #2165: Ignite 3142

2017-06-20 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2165 Ignite 3142 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-3142 Alternatively you can review and apply these

Re: [DISCUSS] Webinar for Ignite Persistent Store walk-through

2017-06-13 Thread vadopolski
+ 1 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Webinar-for-Ignite-Persistent-Store-walk-through-tp18677p18767.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #2003: Ignite 4447 3

2017-05-25 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/2003 Ignite 4447 3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4447-3 Alternatively you can review and apply these

[GitHub] ignite pull request #1983: Ignite 4447 2

2017-05-23 Thread vadopolski
GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1983 Ignite 4447 2 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #1983: Ignite 4447 2

2017-05-23 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1983 --- 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

[GitHub] ignite pull request #1983: Ignite 4447 2

2017-05-22 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1983 Ignite 4447 2 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #1952: IGNITE-4447

2017-05-16 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1952 IGNITE-4447 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski

[GitHub] ignite pull request #1950: IGNITE-4447

2017-05-16 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1950 --- 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

[GitHub] ignite pull request #1950: IGNITE-4447

2017-05-16 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1950 IGNITE-4447 Removed IgniteCache150ClientsTest.java to IgniteCacheTestSuite.java. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski

[GitHub] ignite pull request #1841: Ignite 4760#1084

2017-04-20 Thread vadopolski
GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1841 Ignite 4760#1084 - added AccessType parameter in 'threadLocalForCache' - merge HibernateL2CacheNonStrictReadWriteSelfTest and HibernateL2CacheReadWriteS

[GitHub] ignite pull request #1841: Ignite 4760#1084

2017-04-20 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1841 --- 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

[GitHub] ignite pull request #1768: Ignite 4760

2017-04-20 Thread vadopolski
GitHub user vadopolski reopened a pull request: https://github.com/apache/ignite/pull/1768 Ignite 4760 Added failed test with adding, updating cache. Fixed method threadLocalForCache per-cache thread local. You can merge this pull request into a Git repository by running

[GitHub] ignite pull request #1768: Ignite 4760

2017-04-20 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1768 --- 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

[GitHub] ignite pull request #1841: Ignite 4760#1084

2017-04-20 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1841 Ignite 4760#1084 - added AccessType parameter in 'threadLocalForCache' - merge HibernateL2CacheNonStrictReadWriteSelfTest and HibernateL2CacheReadWriteS

[GitHub] ignite pull request #1828: Ignite 1084

2017-04-19 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1828 Ignite 1084 Added utility to reload the entire L2 cache. It is used before validating the failed test case. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1783: Ignite 4052

2017-04-12 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1783 Ignite 4052 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4052 Alternatively you can review and apply these

[GitHub] ignite pull request #1768: Ignite 4760

2017-04-10 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1768 Ignite 4760 Added failed test with adding, updating cache. Fixed method threadLocalForCache per-cache thread local. You can merge this pull request into a Git repository by running

Re: issue with Hibernate 2L cache region factory ignite-1.8

2017-04-05 Thread vadopolski
Hello everybody! Cameron write please. How did you recreated mistake that the wrong regions/caches were being updated? I tried to do it in HibernateL2CacheConfigurationSelfTest.java - testEntityCacheNonStrictFails. After: e2forUpdate.setName("XXX"); session.update(e2forUpdate); Both reg

[GitHub] ignite pull request #1700: Ignite 4760

2017-03-30 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1700 --- 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

[GitHub] ignite pull request #1700: Ignite 4760

2017-03-30 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1700 Ignite 4760 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4760 Alternatively you can review and apply these

[GitHub] ignite pull request #1699: Ignite 4760

2017-03-30 Thread vadopolski
Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1699 --- 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

[GitHub] ignite pull request #1699: Ignite 4760

2017-03-30 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1699 Ignite 4760 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4760 Alternatively you can review and apply these

[GitHub] ignite pull request #1662: IGNITE-4052

2017-03-22 Thread vadopolski
GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1662 IGNITE-4052 Protos.FrameworkInfoSetup.SetUser added getting MESOS_USER option. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski