[GitHub] ignite pull request #4029: Ignite 1.9.11 extra debug features
GitHub user Mikhail1988 opened a pull request: https://github.com/apache/ignite/pull/4029 Ignite 1.9.11 extra debug features You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.11-wd Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4029.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 #4029 commit 05fac7e8a0bf9e08cd758bed7bd35ec85b914592 Author: Evgenii ZhuravlevDate: 2017-04-19T11:01:21Z Backported IGNITE-4925 Fix IgniteCacheBinaryObjectsScanSelfTest.testScanNoClasses - Fixes #1750. (cherry picked from commit b47f29d) commit ef0a874ceb5c8bfa53e16337f6fd1699afaf2a39 Author: nikolay_tikhonov Date: 2017-06-30T17:39:01Z Fixed CacheSerializableTransactionsTest#testTxConflictRemoveWithOldValue test. Signed-off-by: nikolay_tikhonov commit 4dce965ea86374cba7265cb5d22e975aeac7d480 Author: nikolay_tikhonov Date: 2017-06-30T18:36:02Z Fixed org.jsr107.tck.PutTest tests. Signed-off-by: nikolay_tikhonov commit 32f1e394c222a6f4a2c111d6b6284c8626442b68 Author: Andrey V. Mashenkov Date: 2017-07-03T09:28:12Z Merge branch 'ignite-1.8.8' into ignite-1.9.4 commit 50887fed508e03a8b7df32569afb6d84ab3eb670 Author: Igor Sapego Date: 2017-07-04T17:01:01Z IGNITE-5663: ODBC: Closing cursor do not reset prepared statement anymore commit da290cee855ef45a90ad539515e039f2826a6c00 Author: Igor Sapego Date: 2017-07-05T10:21:12Z IGNITE-5663: Fix for test commit 024a01d6bf91b4f301c4aee7f4a747e810a9a30b Author: nikolay_tikhonov Date: 2017-07-05T15:58:00Z Merged 1.7.12 into 1.8.9 Signed-off-by: nikolay_tikhonov commit 3536a58982e4c264bb72b2ccc1953049d2b5c67f Author: Alexey Kukushkin Date: 2017-07-05T16:36:41Z IGNITE-4901 Decrease logging level for DataStremer retry commit 6d3a3ff2d99697882232070e715928336a9180cd Author: Alexey Kukushkin Date: 2017-07-05T17:05:02Z Fixed merge conflicts commit aedc6aa8b17a39a6460c4b7f69255cd07d635bfb Author: nikolay_tikhonov Date: 2017-07-05T17:42:15Z Merge branch 'ignite-1.7.12' into ignite-1.9.4 Signed-off-by: nikolay_tikhonov commit acfc400b22738fa46397d392f88d49614e687969 Author: nikolay_tikhonov Date: 2017-07-05T17:42:48Z Merge branch 'ignite-1.7.12' into ignite-1.9.4 Signed-off-by: nikolay_tikhonov commit 8dea19ba41bb9eda16f47933b2c46a081116d5f7 Author: Andrey V. Mashenkov Date: 2017-07-06T09:02:07Z Minor fix. commit f208f434f944196d531a1b51066dfe8d6394d739 Author: Andrey V. Mashenkov Date: 2017-07-06T12:17:50Z Test fixed "IGNITE-5390: Bug in IgniteCacheTxStoreSessionWriteBehindCoalescingTest." commit 355a5283559c885f57c4557bba2c6d9170a9b5fc Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 92aa7c6e3c0d9b5cc68002433861b175d54f9421 Author: agura Date: 2017-07-04T13:56:40Z ignite-5685 JDBC prepared statement shouldn't clear parameters after execution commit 9165a0f93b5173b543cc6b4fad5fde37bd215f91 Author: Slava Koptilin Date: 2017-07-07T12:35:33Z ignite-5562: assert statements were changed to the 'if' blocks commit d9fc20a61d5ac0a6e63b26faa7fa0af753b2fa06 Author: Dmitriy Govorukhin Date: 2017-04-07T11:28:22Z IGNITE-4889 - Changed Hibernate integration to use custom keys (cherry picked from commit 6b62a20) commit 16067300c9124b79bfee42139eb881ae585c0914 Author: Dmitriy Govorukhin Date: 2017-04-07T11:28:22Z IGNITE-4889 - Changed Hibernate integration to use custom keys (cherry picked from commit 6b62a20) commit c82e25d67a2f6825a27d26933199a436f6eabba2 Author: Dmitriy Govorukhin Date: 2017-04-07T11:28:22Z IGNITE-4889 - Changed Hibernate integration to use custom keys (cherry picked from commit 6b62a20) commit a352951d91edde9c0029a8bf435d61b4a7cd8c11 Author: Andrey V. Mashenkov Date: 2017-07-04T17:24:52Z IGNITE-4831: Add an option to disable MBeans. commit e4d141e97ab4ec34b5fe6a7bc599413223944438 Author: dkarachentsev Date: 2017-07-14T11:40:02Z IGNITE-5103 - Server drops client node from cluster when no heartbeat messages received in interval heartBeatsFrequency * maxMissedClientHeartBeats. commit
[GitHub] ignite pull request #4028: Ignite 5883
GitHub user andrewmed opened a pull request: https://github.com/apache/ignite/pull/4028 Ignite 5883 For tests Do NOT merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrewmed/ignite ignite-5883 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4028.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 #4028 commit 6147652dc382860a4798998820e4445ab2aea3f5 Author: AMedvedevDate: 2018-05-16T12:40:05Z IGNITE-5883 Only for testing. Add random dir to debug flacky tests in TC commit 2cd224934e538e5701050ebb6a9bb9b7e9f27575 Author: AMedvedev Date: 2018-05-16T14:41:56Z Revert "IGNITE-5883 Only for testing. Add random dir to debug flacky tests in TC" This reverts commit 6147652dc382860a4798998820e4445ab2aea3f5. commit 75dbec7dbea7f481e026e8bba68998802190c3e7 Author: AMedvedev Date: 2018-05-19T18:18:25Z IGNITE-5883: debug flaky ---
[jira] [Created] (IGNITE-8532) GA Grid: Implement Roulette Wheel Selection
Turik Campbell created IGNITE-8532: -- Summary: GA Grid: Implement Roulette Wheel Selection Key: IGNITE-8532 URL: https://issues.apache.org/jira/browse/IGNITE-8532 Project: Ignite Issue Type: New Feature Components: ml Reporter: Turik Campbell Assignee: Turik Campbell Fix For: 2.6 Roulette Wheel Selection Method is a type of selection used for selecting potentially useful solutions for recombination. This selection method gives more chances of selection to the better performing chromosomes. IE: https://en.wikipedia.org/wiki/Fitness_proportionate_selection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Request for contributors permissions
The ELB discovery currently supports classic load balancers only. What I want to add is ELB discovery for Application load balancers too. For difference between classic and application load balancers you can refer these links: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/introduction.html https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html On Sat, May 19, 2018 at 12:19 AM Denis Magdawrote: > Hello Uday and welcome! > > I've added you to the contributors' list in JIRA. > > Speaking about ELB Target Group based discovery, is it the same as this > type of ELB discovery already supported by Ignite? > > https://apacheignite-mix.readme.io/docs/amazon-aws#amazon-elb-based-discovery > > > > On Fri, May 18, 2018 at 8:48 AM, uday kale wrote: > > > Hi, > > > > My name is Uday Kale. Username: *uday*. I want to add support for Node > > discovery through AWS Application ELB Target Group. > > > > Best Regards, > > Uday > > >