[GitHub] ignite pull request #4981: Ignite-2.5.1-p141-pme
GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/4981 Ignite-2.5.1-p141-pme You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p141-pme Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4981.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 #4981 commit fff8a4cc48ae7d8a47f8911763a71d0d59042d87 Author: Andrey Kuznetsov Date: 2018-06-06T12:02:35Z IGNITE-8642 Added thread dumping to FailureProcessor Signed-off-by: Andrey Gura commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf Author: Dmitriy Sorokin Date: 2018-06-06T11:34:04Z IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE Signed-off-by: Andrey Gura commit bad52d3843925d831e6d357a4382731751ae6bb7 Author: Ilya Lantukh Date: 2018-06-04T14:07:52Z GG-13862 : Disabled fast eviction. (cherry picked from commit 786633d) commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d Author: Pavel Kovalenko Date: 2018-06-06T12:24:39Z IGNITE-8482 Skip 2-phase partition release wait in case of activation or dynamic caches start - Fixes #4078. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7c565d2) commit d777c76eadd0a2ccc50f1031c42626b135da5906 Author: Dmitriy Govorukhin Date: 2018-06-06T14:20:18Z IGNITE-8685 Fixed switch segment record size - Fixes #4130. Signed-off-by: Alexey Goncharuk (cherry picked from commit 2a048bd) commit ef4782d8a60eea870b43933480f2c9695c9fc55d Author: Alexey Goncharuk Date: 2018-06-07T11:55:13Z IGNITE-8706 Fixed testMemoryUsageMultipleNodes commit 6902383e01ee69d7efff9613a68f3fc419152305 Author: Pavel Kovalenko Date: 2018-05-14T10:14:52Z IGNITE-8422 Tests fix for Zookeeper discovery split brain detection shouldn't consider client nodes - Fixes #3975. Signed-off-by: dpavlov (cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a) commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d Author: Sergey Chugunov Date: 2018-05-14T17:09:33Z IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994. Signed-off-by: dpavlov (cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38) commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd Author: Anton Kalashnikov Date: 2018-06-08T15:24:09Z IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor reservation - Fixes #4148. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7021651) commit 45953256ef0f09fd5450f6f6c6967a539c5cd395 Author: Pavel Kovalenko Date: 2018-05-03T14:01:20Z IGNITE-8226 Improved logging - Fixes #3796. Signed-off-by: Alexey Goncharuk (cherry picked from commit 8dd9c5d61c86c831b490134c3cd21f2ed47758d2) commit 77d089d857876f1901ade5a017a92c9835e2976a Author: Sergey Kosarev Date: 2018-06-13T14:24:42Z IGNITE-8736 Add transaction label to CU.txString() method output - Fixes #4152. Signed-off-by: Alexey Goncharuk commit c3c80439945134867e28e8d2c6db5ef9295141b6 Author: Andrey Gura Date: 2018-06-09T13:37:49Z IGNITE-8751 Failure handler accordingly to segmentation policy should be invoked on node segmentation instead of configured failure handler commit d33fe100bc9fdbcb66754d43ec0199e44233190b Author: Andrey Gura Date: 2018-06-13T14:30:18Z IGNITE-8781 GridNioServer accepter threads should have different names commit d2c304ca415919f0933461dde92fdf354539529b Author: Aleksey Plekhanov Date: 2018-06-14T17:41:31Z IGNITE-8763 java.nio.file.AccessDeniedException is not handled with default failure handler Signed-off-by: Andrey Gura commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7 Author: Sergey Chugunov Date: 2018-06-15T08:31:33Z IGNITE-8657 Simultaneous start of multiple clients may lead to client start hang when exchange history size is too short - Fixes #4102. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21) commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2 Author: Pavel Kovalenko Date: 2018-06-15T09:48:24Z IGNITE-8610 Fixed checkpoint record search for WAL delta rebalancing - Fixes #4090. Signed-off-by: Alexey Goncharuk (cherry picked from commit 10aa02a) commit 1a8e9fcafa3a6d53ab01901be798cc8957252fe6 Author: EdShangGG Date: 2018-06-15T16:35:00Z IGNITE-8610 Fix compilation (cherry picked from commit 55af7d1) commit 298ca37aea710e098d033fcc5750e408b4a07c24 Author: Ilya Lantukh Date: 2018-05-23T15:02:23Z IGNITE-7809 fixed stable failures of IgniteWalFlushDefaultSelfTest in Ignite PDS 2
[GitHub] ignite pull request #4982: Ignite-2.5.1-p141-fix
GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/4982 Ignite-2.5.1-p141-fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p141-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4982.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 #4982 commit af026c7840101e2c57c7dd882baabddb6df2fa82 Author: Ilya Lantukh Date: 2018-06-04T22:24:37Z IGNITE-8693 SQL JOIN between PARTITIONED and REPLICATED cache fails - Fixes #4120. Signed-off-by: Ivan Rakov (cherry picked from commit bc35ce0) commit a84538a9df8ace432411736289ec8371dee215e2 Author: Sergey Kosarev Date: 2018-06-06T09:59:28Z IGNITE-8696 control.sh utility does not show atomicity mode - Fixes #4127. Signed-off-by: Ivan Rakov (cherry picked from commit 78e5d970be74c04b01857123b1a623038aa18440) commit fff8a4cc48ae7d8a47f8911763a71d0d59042d87 Author: Andrey Kuznetsov Date: 2018-06-06T12:02:35Z IGNITE-8642 Added thread dumping to FailureProcessor Signed-off-by: Andrey Gura commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf Author: Dmitriy Sorokin Date: 2018-06-06T11:34:04Z IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE Signed-off-by: Andrey Gura commit bad52d3843925d831e6d357a4382731751ae6bb7 Author: Ilya Lantukh Date: 2018-06-04T14:07:52Z GG-13862 : Disabled fast eviction. (cherry picked from commit 786633d) commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d Author: Pavel Kovalenko Date: 2018-06-06T12:24:39Z IGNITE-8482 Skip 2-phase partition release wait in case of activation or dynamic caches start - Fixes #4078. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7c565d2) commit d777c76eadd0a2ccc50f1031c42626b135da5906 Author: Dmitriy Govorukhin Date: 2018-06-06T14:20:18Z IGNITE-8685 Fixed switch segment record size - Fixes #4130. Signed-off-by: Alexey Goncharuk (cherry picked from commit 2a048bd) commit ef4782d8a60eea870b43933480f2c9695c9fc55d Author: Alexey Goncharuk Date: 2018-06-07T11:55:13Z IGNITE-8706 Fixed testMemoryUsageMultipleNodes commit 6902383e01ee69d7efff9613a68f3fc419152305 Author: Pavel Kovalenko Date: 2018-05-14T10:14:52Z IGNITE-8422 Tests fix for Zookeeper discovery split brain detection shouldn't consider client nodes - Fixes #3975. Signed-off-by: dpavlov (cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a) commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d Author: Sergey Chugunov Date: 2018-05-14T17:09:33Z IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994. Signed-off-by: dpavlov (cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38) commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd Author: Anton Kalashnikov Date: 2018-06-08T15:24:09Z IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor reservation - Fixes #4148. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7021651) commit 45953256ef0f09fd5450f6f6c6967a539c5cd395 Author: Pavel Kovalenko Date: 2018-05-03T14:01:20Z IGNITE-8226 Improved logging - Fixes #3796. Signed-off-by: Alexey Goncharuk (cherry picked from commit 8dd9c5d61c86c831b490134c3cd21f2ed47758d2) commit 77d089d857876f1901ade5a017a92c9835e2976a Author: Sergey Kosarev Date: 2018-06-13T14:24:42Z IGNITE-8736 Add transaction label to CU.txString() method output - Fixes #4152. Signed-off-by: Alexey Goncharuk commit c3c80439945134867e28e8d2c6db5ef9295141b6 Author: Andrey Gura Date: 2018-06-09T13:37:49Z IGNITE-8751 Failure handler accordingly to segmentation policy should be invoked on node segmentation instead of configured failure handler commit d33fe100bc9fdbcb66754d43ec0199e44233190b Author: Andrey Gura Date: 2018-06-13T14:30:18Z IGNITE-8781 GridNioServer accepter threads should have different names commit d2c304ca415919f0933461dde92fdf354539529b Author: Aleksey Plekhanov Date: 2018-06-14T17:41:31Z IGNITE-8763 java.nio.file.AccessDeniedException is not handled with default failure handler Signed-off-by: Andrey Gura commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7 Author: Sergey Chugunov Date: 2018-06-15T08:31:33Z IGNITE-8657 Simultaneous start of multiple clients may lead to client start hang when exchange history size is too short - Fixes #4102. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21) commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2 Author: Pavel Kovalenko Date:
[jira] [Created] (IGNITE-9875) GridDhtPartitionsStateValidator speedup proposal.
Stanilovsky Evgeny created IGNITE-9875: -- Summary: GridDhtPartitionsStateValidator speedup proposal. Key: IGNITE-9875 URL: https://issues.apache.org/jira/browse/IGNITE-9875 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.6 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny I check validatePartitionsUpdateCounters and validatePartitionsSizes code implementations and looks like we can speed up some parts of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4983: IGNITE-9875 GridDhtPartitionsStateValidator speed...
GitHub user zstan opened a pull request: https://github.com/apache/ignite/pull/4983 IGNITE-9875 GridDhtPartitionsStateValidator speedup proposal. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9875 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4983.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 #4983 commit f73da8a1271f53d842826d73dcd2d62c265813b0 Author: zstan Date: 2018-10-14T07:32:21Z IGNITE-9875 GridDhtPartitionsStateValidator speedup proposal. ---
[jira] [Created] (IGNITE-9876) .NET: Thin Client: Implement Best Effort Affinity
Pavel Tupitsyn created IGNITE-9876: -- Summary: .NET: Thin Client: Implement Best Effort Affinity Key: IGNITE-9876 URL: https://issues.apache.org/jira/browse/IGNITE-9876 Project: Ignite Issue Type: New Feature Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4984: IGNITE-9292 MVCC SQL: Unexpected state exception ...
GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/4984 IGNITE-9292 MVCC SQL: Unexpected state exception when updating backup You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9292 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4984.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 #4984 commit ad85ac874292a68746c23e8db6c62a11e226523a Author: Igor Seliverstov Date: 2018-10-14T19:46:34Z IGNITE-9292 MVCC SQL: Unexpected state exception when updating backup ---
[jira] [Created] (IGNITE-9877) .NET: AmbiguousMatchException under .NET Core 2.1
Pavel Tupitsyn created IGNITE-9877: -- Summary: .NET: AmbiguousMatchException under .NET Core 2.1 Key: IGNITE-9877 URL: https://issues.apache.org/jira/browse/IGNITE-9877 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.8 One of the string methods is causing an exception: {code} Unhandled Exception: System.TypeInitializationException: The type initializer for 'Apache.Ignite.Linq.Impl.MethodVisitor' threw an exception. ---> System.Reflection.AmbiguousMatchException: Ambiguous match found. at System.RuntimeType.GetMethodImplCommon(String name, Int32 genericParameterCount, BindingFlags bindingAttr, Binder binder, CallingConventions callConv, Type[] types, ParameterModifier[] modifiers) at System.RuntimeType.GetMethodImpl(String name, BindingFlags bindingAttr, Binder binder, CallingConventions callConv, Type[] types, ParameterModifier[] modifiers) at System.Type.GetMethod(String name, BindingFlags bindingAttr) at Apache.Ignite.Linq.Impl.MethodVisitor.GetMethod(Type type, String name, Type[] argTypes, VisitMethodDelegate del) at Apache.Ignite.Linq.Impl.MethodVisitor.GetStringMethod(String name, Type[] argTypes, VisitMethodDelegate del) at Apache.Ignite.Linq.Impl.MethodVisitor..cctor() {code} We should clarify the signature of all string methods to avoid this in future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[MTCGA]: new failures in builds [2063682] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New stable failure of a flaky test in master HadoopMapReduceErrorResilienceTest.testRecoveryAfterAnError0_Error https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=2414028243453692891&branch=%3Cdefault%3E&tab=testDetails Changes may lead to failure were done by - jokserfn http://ci.ignite.apache.org/viewModification.html?modId=834843&personal=false - aplatonovv http://ci.ignite.apache.org/viewModification.html?modId=834837&personal=false - kondakov87 http://ci.ignite.apache.org/viewModification.html?modId=834798&personal=false - mr.weider http://ci.ignite.apache.org/viewModification.html?modId=834773&personal=false - tledkov http://ci.ignite.apache.org/viewModification.html?modId=834768&personal=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 03:25:42 15-10-2018
[GitHub] ignite pull request #4966: IGNITE-9862 Web Console: Add support for "date", ...
Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/4966 ---
[GitHub] ignite pull request #4972: IGNITE-9809 Web console: more minor fixes
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4972 ---
[jira] [Created] (IGNITE-9878) Failed to start near cache after second call of getOrCreateCache
Roman Guseinov created IGNITE-9878: -- Summary: Failed to start near cache after second call of getOrCreateCache Key: IGNITE-9878 URL: https://issues.apache.org/jira/browse/IGNITE-9878 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Roman Guseinov Assignee: Roman Guseinov Attachments: NearCacheIssueReproducer.java Repeated call of `Ignite.getOrCreateCache(CacheConfiguration cacheCfg, NearCacheConfiguration nearCfg)` lead the following exception: {code:java} javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to start near cache (local node is an affinity node for cache): ignite-test-near-rep at org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1300) at org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2872) at org.apache.ignite.examples.NearCacheIssueReproducer.testIgniteNearCacheReplicated(NearCacheIssueReproducer.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start near cache (local node is an affinity node for cache): ignite-test-near-rep at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheChangeRequest(GridCacheProcessor.java:4302) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2877) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:2816) at org.apache.ignite.internal.IgniteKernal.getOrCreateCache(IgniteKernal.java:2860) ... 23 more {code} The test is attached [^NearCacheIssueReproducer.java]. The workaround is to put near cache config into cache configuration `CacheConfiguration.setNearConfiguration`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)