[jira] [Closed] (IGNITE-5835) Implement highlight item in non-multiple dropdown
[ https://issues.apache.org/jira/browse/IGNITE-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-5835. -- Assignee: Alexey Kuznetsov (was: Andrey Novikov) > Implement highlight item in non-multiple dropdown > - > > Key: IGNITE-5835 > URL: https://issues.apache.org/jira/browse/IGNITE-5835 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Affects Versions: 2.2 >Reporter: Dmitriy Shabalin >Assignee: Alexey Kuznetsov > > 1) Hide checkboxes in single dropdown > 2) Add highlight to selected item in single dropdown -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types
[
https://issues.apache.org/jira/browse/IGNITE-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-5767:
-
Assignee: Andrey Novikov (was: Vasiliy Sisko)
> Web console: use byte array type instead of java.lang.Object for binary JDBC
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Schema importer should use {{[B}} query entity field type instead of
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}}
> and {{LONGVARBINARY}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types
[
https://issues.apache.org/jira/browse/IGNITE-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102614#comment-16102614
]
Vasiliy Sisko commented on IGNITE-5767:
---
Implemented test for loading of BINARY column into byte array field.
> Web console: use byte array type instead of java.lang.Object for binary JDBC
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Vasiliy Sisko
> Fix For: 2.2
>
>
> Schema importer should use {{[B}} query entity field type instead of
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}}
> and {{LONGVARBINARY}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5690) JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5690:
---
Labels: MakeTeamcityGreenAgain test-fail (was: test-fail)
> JavaEmbeddedIgniteRDDSelfTest sometimes hangs on TC
> ---
>
> Key: IGNITE-5690
> URL: https://issues.apache.org/jira/browse/IGNITE-5690
> Project: Ignite
> Issue Type: Bug
> Components: spark
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
> Labels: MakeTeamcityGreenAgain, test-fail
> Attachments: Ignite_2.0_Tests_Ignite_RDD_436.log
>
>
> Test hangs when IgniteContext.close(...) is called:
> {noformat}
> [12:20:47]W: [org.apache.ignite:ignite-spark] Thread
> [name="test-runner-#1%spark.JavaEmbeddedIgniteRDDSelfTest%", id=77,
> state=WAITING, blockCnt=59, waitCnt=10012]
> [12:20:47]W: [org.apache.ignite:ignite-spark] Lock
> [object=scala.concurrent.impl.Promise$CompletionLatch@77d938ab,
> ownerName=null, ownerId=-1]
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> sun.misc.Unsafe.park(Native Method)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> scala.concurrent.impl.Promise$DefaultPromise.tryAwait(Promise.scala:202)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:218)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:153)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:619)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1918)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1931)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1944)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1958)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:925)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1.apply(RDD.scala:923)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDD.withScope(RDD.scala:362)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> org.apache.spark.rdd.RDD.foreachPartition(RDD.scala:923)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> o.a.i.spark.IgniteContext.close(IgniteContext.scala:168)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> o.a.i.spark.JavaIgniteContext.close(JavaIgniteContext.scala:68)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> o.a.i.spark.JavaEmbeddedIgniteRDDSelfTest.testReadDataFromIgnite(JavaEmbeddedIgniteRDDSelfTest.java:181)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [12:20:47]W: [org.apache.ignite:ignite-spark] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [12:20:47]W: [org.apache.ignite:ignite-spark]
[jira] [Updated] (IGNITE-5689) IgniteCommunicationBalanceTest hangs on Windows
[
https://issues.apache.org/jira/browse/IGNITE-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5689:
---
Labels: MakeTeamcityGreenAgain test-fail (was: test-fail)
> IgniteCommunicationBalanceTest hangs on Windows
> ---
>
> Key: IGNITE-5689
> URL: https://issues.apache.org/jira/browse/IGNITE-5689
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
>
> Test runner is waiting for ComputeTask to finish:
> {noformat}
> "test-runner-#40602%communication.IgniteCommunicationBalanceMultipleConnectionsTest%"
> prio=6 tid=0x766d6000 nid=0x7934 waiting on condition
> [0xeacfe000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at
> org.apache.ignite.internal.AsyncSupportAdapter.saveOrGet(AsyncSupportAdapter.java:112)
> at
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
> at
> org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest$1.apply(IgniteCommunicationBalanceTest.java:158)
> at
> org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1603)
> at
> org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest.testBalance1(IgniteCommunicationBalanceTest.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> While thread that tried to send job result got stuck in
> IgniteUtils.reachable(...):
> {noformat}
> "pub-#40657%communication.IgniteCommunicationBalanceMultipleConnectionsTest5%"
> prio=6 tid=0x11b8 nid=0x3868 runnable [0xeecfe000]
>java.lang.Thread.State: RUNNABLE
> at java.net.Inet4AddressImpl.isReachable0(Native Method)
> at java.net.Inet4AddressImpl.isReachable(Inet4AddressImpl.java:70)
> at java.net.InetAddress.isReachable(InetAddress.java:475)
> at java.net.InetAddress.isReachable(InetAddress.java:434)
> at
> org.apache.ignite.internal.util.IgniteUtils.reachable(IgniteUtils.java:2113)
> at
> org.apache.ignite.internal.util.IgniteUtils.filterReachable(IgniteUtils.java:1877)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2955)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2763)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2655)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2516)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2480)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1643)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1715)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:928)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:773)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:625)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
[jira] [Updated] (IGNITE-5691) IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
[
https://issues.apache.org/jira/browse/IGNITE-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5691:
---
Labels: MakeTeamcityGreenAgain Muted_test test-fail (was: Muted_test
test-fail)
> IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
> --
>
> Key: IGNITE-5691
> URL: https://issues.apache.org/jira/browse/IGNITE-5691
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Attachments: Ignite_2.0_Tests_Ignite_IGFS_Linux_and_MacOS_444.log.zip
>
>
> Hangs when output stream is closed:
> {noformat}
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] Thread
> [name="test-runner-#15168%grid%", id=24808, state=WAITING, blockCnt=0,
> waitCnt=3]
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.misc.Unsafe.park(Native Method)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutProc.closeStream(HadoopIgfsOutProc.java:446)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutputStream.close(HadoopIgfsOutputStream.java:142)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:70)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:103)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.i.processors.hadoop.impl.igfs.IgniteHadoopFileSystemAbstractSelfTest.testDeleteSuccessfulIfPathIsOpenedToRead(IgniteHadoopFileSystemAbstractSelfTest.java:752)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> [12:38:39]W: [org.apache.ignite:ignite-hadoop] at
> java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (IGNITE-5743) .NET: PageMemory and PersistentStore documentation
[ https://issues.apache.org/jira/browse/IGNITE-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-5743. --- Reviewed. > .NET: PageMemory and PersistentStore documentation > -- > > Key: IGNITE-5743 > URL: https://issues.apache.org/jira/browse/IGNITE-5743 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 2.1 >Reporter: Pavel Tupitsyn >Assignee: Prachi Garg > Labels: .NET > Fix For: 2.1 > > > Add documentation on https://apacheignite-net.readme.io/docs. > It should mostly refer to Java pages, but we need configuration examples in > C# and app.config XML. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5678) Need to document and test supported and unsupported SQL features
[ https://issues.apache.org/jira/browse/IGNITE-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102173#comment-16102173 ] Denis Magda commented on IGNITE-5678: - In addition, we need to check that all the commonly used types are supported. For instance, it's not clear how well and broad is our support of BigDecimal and BigInteger. > Need to document and test supported and unsupported SQL features > > > Key: IGNITE-5678 > URL: https://issues.apache.org/jira/browse/IGNITE-5678 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Dmitriy Setrakyan >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 2.2 > > > We should provide supported and unsupported feature documentation, similar to > PostgreSQL: https://www.postgresql.org/docs/devel/static/features.html > We can do the following: > * Have a very detailed documented list of all the supported/unsupported > features in Ignite SQL engine. > * Once the list is created, ensure that we have sufficient test coverage for > all the supported features. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5158) Merge and rework SQL schema and DDL documentations
[ https://issues.apache.org/jira/browse/IGNITE-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-5158: Fix Version/s: (was: 2.1) 2.2 > Merge and rework SQL schema and DDL documentations > -- > > Key: IGNITE-5158 > URL: https://issues.apache.org/jira/browse/IGNITE-5158 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 2.2 > > > Presently, SQL schema/indexes and DDL documentations are documented > separately: > https://apacheignite.readme.io/docs/distributed-ddl > https://apacheignite.readme.io/docs/indexes > Need to rework and merge them somehow emphasizing that DDL is becoming a main > tool for the schema definition. > Don't forget to update ODBC and JDBC, .NET and C++ docs showing DDL usage > there. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5382) SQL: frequent switch between schemas cause severe slowdown
[
https://issues.apache.org/jira/browse/IGNITE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102093#comment-16102093
]
Alexander Paschenko commented on IGNITE-5382:
-
[~skalashnikov]
my comments:
- please see my changes (removed weak map, made {{H2ConnectionWrapper}}
immutable)
- refactor duplicate code in {{IgniteH2Indexing}} (added a TODO on this)
- add javadocs to {{H2ConnectionCache}}
- please refactor {{IgniteH2Indexing}} to bind statements cache and its
corresponding connection together in the thread scope. Currently we drop all
thread's cached statements when we change a schema and I don't think it's
right. I believe we better store thread local maps of following structure
schema name -> [connection; statement cache] and clean them up by timeout like
it's done now for statement caches.
> SQL: frequent switch between schemas cause severe slowdown
> --
>
> Key: IGNITE-5382
> URL: https://issues.apache.org/jira/browse/IGNITE-5382
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Labels: important, performance
> Fix For: 2.2
>
>
> We have thread-bound cached connection to H2 database which is bound to
> specific schema. See {{IgniteH2Indexing.connectionForThread}}.
> When query with different schema is executed, we call {{SET SCHEMA}} command,
> which is rather expensive and may cause slowdown when queries form different
> caches are executed.
> To avoid this we should maintain thread-local map of such connections. Be
> careful with concurrency and resource leaks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5769) Abstract away .NET->Java calls
[
https://issues.apache.org/jira/browse/IGNITE-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102061#comment-16102061
]
Pavel Tupitsyn commented on IGNITE-5769:
{{IPlatformTarget}} should be extended with {{IPlatformTargetInternal}} where
stream-based methods are placed (streams are internal).
> Abstract away .NET->Java calls
> --
>
> Key: IGNITE-5769
> URL: https://issues.apache.org/jira/browse/IGNITE-5769
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
>
> All JNI interaction goes through static {{UnmanagedUtils}} calls. This should
> be refactored so that unmanaged call mechanism can be replaced with something
> else for each particular node.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator
[
https://issues.apache.org/jira/browse/IGNITE-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5741:
---
Labels: MakeTeamcityGreenAgain Muted_test (was: MakeTeamcityGreenAgain)
> Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator
> -
>
> Key: IGNITE-5741
> URL: https://issues.apache.org/jira/browse/IGNITE-5741
> Project: Ignite
> Issue Type: Task
> Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>Assignee: Ilya Lantukh
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.2
>
>
> In current implementation we can get OOM during iterate on wal records,
> because some wal record may be very large (more that 64Mb). We read using
> HeapByteBuffer, FileChannel reserve buffer same size as our HeapByteBuffer,
> but by default FileChannel can not allocate buffer more that 64Mb. (maxMemory
> = VM.maxDirectMemory())
> java-7-oracle
> {code}
> [16:07:54]W: [org.apache.ignite:ignite-core] [2017-07-12
> 13:07:54,809][ERROR][exchange-worker-#55966%node0-primary%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=3,
> minorTopVer=1], nodeId=105056d5, evt=DISCOVERY_CUSTOM_EVT]
> [16:07:54]W: [org.apache.ignite:ignite-core]
> java.lang.OutOfMemoryError: Direct buffer memory
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.Bits.reserveMemory(Bits.java:658)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:306)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:174)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.IOUtil.read(IOUtil.java:195)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:149)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:62)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:116)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:303)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:376)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:385)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:697)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:673)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:243)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.advanceSegment(FileWriteAheadLogManager.java:2452)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:149)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2352)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2290)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.replay(FileWriteAheadLogManager.java:553)
> [
[jira] [Commented] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
[
https://issues.apache.org/jira/browse/IGNITE-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102040#comment-16102040
]
Dmitriy Pavlov commented on IGNITE-5682:
[~sboikov], I've updated PR according latest changes in master.
Could you please review this change?
> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration.
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map
> update
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
> cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], locNode=TcpDiscoveryNode
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2,
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:,
> isClient=false]]
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
> 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:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5838) The IgniteCache.loadCacheAsync method is not executed asynchronously.
[
https://issues.apache.org/jira/browse/IGNITE-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102005#comment-16102005
]
Valentin Kulichenko commented on IGNITE-5838:
-
[~liyuj]
I reproduced the behavior, but I really doubt this is blocker, so I lowered the
priority.
First of all, there is always an easy workaround - just call synchronous method
in a separate thread to get pure async behavior. Second of all, this happens
only for a scenario when {{loadCache}} is called on a server node. If you call
it from the client, it will not wait for any network operations.
Having said that, this is driven by current semantics of asynchronous internal
operations. However, I agree that it makes sense to change this behavior for
cache loading, as it's generally a long process. If it's important for you,
feel free to assign ticket to yourself and contribute. If you have any question
- welcome to the dev mailing list.
> The IgniteCache.loadCacheAsync method is not executed asynchronously.
> -
>
> Key: IGNITE-5838
> URL: https://issues.apache.org/jira/browse/IGNITE-5838
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Yujue Li
> Fix For: 2.2
>
>
> The IgniteCache.loadCacheAsync method is not executed asynchronously.
> for example,in the
> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/spring/CacheSpringStoreExample.java:
> line 129:
> If modified to:
> cache.loadCacheAsync(null, ENTRY_COUNT);
> We will find that the cache is not loaded asynchronously.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5218) Decision trees
[ https://issues.apache.org/jira/browse/IGNITE-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101992#comment-16101992 ] ASF GitHub Bot commented on IGNITE-5218: GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/2350 IGNITE-5218: Column-based decision trees implemented. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5218 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2350.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 #2350 commit dcc459665cea183119c6fe771d568bbba8580aea Author: Artem Malykh Date: 2017-07-26T17:33:25Z IGNITE-5218: Column-based decision trees implemented. > Decision trees > -- > > Key: IGNITE-5218 > URL: https://issues.apache.org/jira/browse/IGNITE-5218 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Artem Malykh > > We want to implement Decision trees for Ignite ML because it's really common > one for ML. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5838) The IgniteCache.loadCacheAsync method is not executed asynchronously.
[ https://issues.apache.org/jira/browse/IGNITE-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-5838: Priority: Major (was: Blocker) > The IgniteCache.loadCacheAsync method is not executed asynchronously. > - > > Key: IGNITE-5838 > URL: https://issues.apache.org/jira/browse/IGNITE-5838 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.0 >Reporter: Yujue Li > Fix For: 2.2 > > > The IgniteCache.loadCacheAsync method is not executed asynchronously. > for example,in the > https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/spring/CacheSpringStoreExample.java: > line 129: > If modified to: > cache.loadCacheAsync(null, ENTRY_COUNT); > We will find that the cache is not loaded asynchronously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)
[
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101936#comment-16101936
]
Dmitriy Pavlov edited comment on IGNITE-4767 at 7/26/17 5:07 PM:
-
I've restarted tests for 2.0 group using RunAll chain:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F1599%2Fhead
was (Author: dpavlov):
I've restarted tests for 2.0:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F1599%2Fhead
> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Dmitriy Pavlov
> Fix For: 2.2
>
>
> There is too much code places like:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e) {
> tx.rollbackAsync();
> throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
> try {
> tx.rollbackAsync();
> }
> catch (Throwable inner) {
> e.addSuppressed(inner);
> }
> throw e;
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)
[
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101936#comment-16101936
]
Dmitriy Pavlov commented on IGNITE-4767:
I've restarted tests for 2.0:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F1599%2Fhead
> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Dmitriy Pavlov
> Fix For: 2.2
>
>
> There is too much code places like:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e) {
> tx.rollbackAsync();
> throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
> try {
> tx.rollbackAsync();
> }
> catch (Throwable inner) {
> e.addSuppressed(inner);
> }
> throw e;
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5738) Add support of batch requests for jdbc2
[ https://issues.apache.org/jira/browse/IGNITE-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kalashnikov reassigned IGNITE-5738: -- Assignee: Sergey Kalashnikov > Add support of batch requests for jdbc2 > --- > > Key: IGNITE-5738 > URL: https://issues.apache.org/jira/browse/IGNITE-5738 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Evgenii Zhuravlev >Assignee: Sergey Kalashnikov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5848) Ignite should support Hibernate 5.2.X
[
https://issues.apache.org/jira/browse/IGNITE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-5848:
-
Labels: community java8 (was: community)
> Ignite should support Hibernate 5.2.X
> -
>
> Key: IGNITE-5848
> URL: https://issues.apache.org/jira/browse/IGNITE-5848
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Affects Versions: 2.0, 2.1
>Reporter: Nikolay Tikhonov
> Labels: community, java8
> Fix For: 2.3
>
>
> Currently Ignite supports Hibernate 5.1.X
> With Hibernate version of 5.2.X got the following exception:
> {code:java}
> Handler dispatch failed; nested exception is java.lang.AbstractMethodError:
> org.apache.ignite.cache.hibernate.HibernateEntityRegion$AccessStrategy.putFromLoad(Lorg/hibernate/engine/spi/SharedSessionContractImplementor;Ljava/lang/Object;Ljava/lang/Object;JLjava/lang/Object;Z)Z
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5817) Change checksum calculation methods
[ https://issues.apache.org/jira/browse/IGNITE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Setrakyan updated IGNITE-5817: -- Priority: Blocker (was: Major) > Change checksum calculation methods > --- > > Key: IGNITE-5817 > URL: https://issues.apache.org/jira/browse/IGNITE-5817 > Project: Ignite > Issue Type: Bug >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin >Priority: Blocker > Fix For: 2.2 > > > Neither sha1 nor md5 are trustful checksum calculation methods. We should be > switching to at least sha265 or higher. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5803) IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, stable reproducible locally
[
https://issues.apache.org/jira/browse/IGNITE-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101873#comment-16101873
]
Dmitriy Pavlov commented on IGNITE-5803:
Probably fixed in IGNITE-5806,
http://ci.ignite.apache.org/viewLog.html?buildId=740941&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache4
> IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed,
> stable reproducible locally
> ---
>
> Key: IGNITE-5803
> URL: https://issues.apache.org/jira/browse/IGNITE-5803
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=738392&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache4
> org.apache.ignite.testsuites.IgniteCacheTestSuite4:
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughAtomicReplicated
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx0
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx1
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx2
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTxReplicated
> All failed with
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.fail(Assert.java:64)
> at junit.framework.TestCase.fail(TestCase.java:235)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughAbstractTest$TestEntryProcessor.process(IgniteCacheInvokeReadThroughAbstractTest.java:362)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.applyTransformClosures(IgniteTxAdapter.java:1465)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.batchStoreCommit(IgniteTxAdapter.java:1221)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:501)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3030)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5771) Add Ignite.setActive method to C++ API
[
https://issues.apache.org/jira/browse/IGNITE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101868#comment-16101868
]
Pavel Tupitsyn commented on IGNITE-5771:
[~isapego] looks good to me.
> Add Ignite.setActive method to C++ API
> --
>
> Key: IGNITE-5771
> URL: https://issues.apache.org/jira/browse/IGNITE-5771
> Project: Ignite
> Issue Type: New Feature
>Affects Versions: 2.0
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.2
>
>
> Presently, {{Ignite.setActive}} method is unavailable in C++ API which means
> that there is now way to activate a cluster with the Ignite Persistent Store
> enabled from a C++ application side.
> Add this method and add a respective documentation paragraph to that section
> https://apacheignite-cpp.readme.io/v2.1/docs/ignite-persistence#section-usage
> in the same way as it's aleady done for .NET:
> https://apacheignite-net.readme.io/v2.1/docs/ignite-persistent-store#section-usage
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5848) Ignite should support Hibernate 5.2.X
Nikolay Tikhonov created IGNITE-5848:
Summary: Ignite should support Hibernate 5.2.X
Key: IGNITE-5848
URL: https://issues.apache.org/jira/browse/IGNITE-5848
Project: Ignite
Issue Type: Sub-task
Components: cache
Affects Versions: 2.0, 2.1
Reporter: Nikolay Tikhonov
Currently Ignite supports Hibernate 5.1.X
With Hibernate version of 5.2.X got the following exception:
{code:java}
Handler dispatch failed; nested exception is java.lang.AbstractMethodError:
org.apache.ignite.cache.hibernate.HibernateEntityRegion$AccessStrategy.putFromLoad(Lorg/hibernate/engine/spi/SharedSessionContractImplementor;Ljava/lang/Object;Ljava/lang/Object;JLjava/lang/Object;Z)Z
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5729) IgniteCacheProxy instances from "with..." methods are not reusable
[ https://issues.apache.org/jira/browse/IGNITE-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093428#comment-16093428 ] Alexey Goncharuk edited comment on IGNITE-5729 at 7/26/17 4:16 PM: --- Refactoring is ready. Branch is ignite-5729 Ignite TC: http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F2293%2Fhead# was (Author: jokser): Refactoring is ready. Branch in both repositories: ignite-5729 Ignite TC: http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F2293%2Fhead# > IgniteCacheProxy instances from "with..." methods are not reusable > -- > > Key: IGNITE-5729 > URL: https://issues.apache.org/jira/browse/IGNITE-5729 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.1 >Reporter: Pavel Kovalenko >Assignee: Alexey Goncharuk > Fix For: 2.2 > > > On cache restart all IgniteCacheProxy instances must be reset in order to > reuse them. > But bunch of methods in IgniteCache interface including withKeepBinary create > new instances of proxy for each call and these instances are not reset on > cache restart. > E.g. it leads to CacheStoppedException when reusing them after restoring from > snapshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)
[
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-4767:
--
Assignee: Dmitriy Pavlov (was: Alexey Goncharuk)
> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Dmitriy Pavlov
> Fix For: 2.2
>
>
> There is too much code places like:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e) {
> tx.rollbackAsync();
> throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
> try {
> tx.rollbackAsync();
> }
> catch (Throwable inner) {
> e.addSuppressed(inner);
> }
> throw e;
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5847) API for Models
Yury Babak created IGNITE-5847: -- Summary: API for Models Key: IGNITE-5847 URL: https://issues.apache.org/jira/browse/IGNITE-5847 Project: Ignite Issue Type: New Feature Components: ml Reporter: Yury Babak We want to design and implement API for Models. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5846) Add support of distributed matrices for OLS regression.
Yury Babak created IGNITE-5846: -- Summary: Add support of distributed matrices for OLS regression. Key: IGNITE-5846 URL: https://issues.apache.org/jira/browse/IGNITE-5846 Project: Ignite Issue Type: Improvement Components: ml Reporter: Yury Babak Currently OSL regression works only with local matrices. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5845) Benchmarks for ML algorithms.
Yury Babak created IGNITE-5845: -- Summary: Benchmarks for ML algorithms. Key: IGNITE-5845 URL: https://issues.apache.org/jira/browse/IGNITE-5845 Project: Ignite Issue Type: Improvement Components: ml Reporter: Yury Babak We want to create some benchmarks for ML algorithms. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-4172) SQL: Add support for Java 8 Time API classes in date\time functions
[ https://issues.apache.org/jira/browse/IGNITE-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101840#comment-16101840 ] ASF GitHub Bot commented on IGNITE-4172: GitHub user asfedotov opened a pull request: https://github.com/apache/ignite/pull/2349 IGNITE-4172 SQL: Add support for Java 8 Time API classes in date\time functions For CI purposes only. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4172 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2349.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 #2349 commit 925ee11c2002729b1264148ee5db5700ded5a7b7 Author: Alexey Kuznetsov Date: 2017-04-04T09:06:01Z Fixed typo. (cherry picked from commit 3b84f34) commit ce4b078c1c97cae4136c318ae38b27a50fe383cc Author: Alexey Kuznetsov Date: 2017-04-04T09:14:56Z master Updated version. (cherry picked from commit 5469626) commit ae435fb5474429e7ac76faadd680c19a4c657371 Author: Sergi Vladykin Date: 2017-04-02T12:35:04Z ignite-2913 - SQL: EXISTS support added commit b7ab27301b59bf93fc73b52fdf8e0bcf124fec1d Author: Andrey V. Mashenkov Date: 2017-04-06T11:43:50Z IGNITE-4832: Prevent service deployment on client by default when configuration is provided on startup. This closes #1748. commit b214211eb3461746b6931c0623e086bb208e5dda Author: Anton Vinogradov Date: 2017-04-06T12:00:12Z IGNITE-4644 Value from IgniteQueue in atomic mode could be lost commit 014161427fb603b6df7c8ecc3c0904f5df47a21d Author: Denis Magda Date: 2017-02-14T01:33:32Z IGNITE-4159: Kubernetes IP finder. (cherry picked from commit 37c0a22) commit 1db238402f11c67d2b28bfb7ff47955415f00c25 Author: Denis Magda Date: 2017-02-16T04:37:26Z IGNITE-4159: fixing logging (cherry picked from commit 06908d2) (cherry picked from commit fa27ee3) commit 5dfe16f7e91374008b9f6dfbb899364f5b2e1164 Author: Denis Magda Date: 2017-02-14T06:03:30Z IGNITE-4159: using logger instead of system.out.println (cherry picked from commit b9bf77c) commit 6e596d1ef426b66abd866d011a8f5cf5c5c25124 Author: Andrey V. Mashenkov Date: 2017-04-06T11:43:50Z IGNITE-4832: Prevent service deployment on client by default when configuration is provided on startup. This closes #1748. (cherry picked from commit b7ab273) commit 443ac9a7aa82af1359a03bcfc8f9212b108300e4 Author: Andrey V. Mashenkov Date: 2017-04-05T12:01:02Z IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarshaller . This closes #1736. commit 05f3c747921aed6838804d2f5f2c8d2bd7985337 Author: Andrey V. Mashenkov Date: 2017-04-05T12:01:02Z IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarshaller . This closes #1736. (cherry picked from commit 443ac9a) commit b8e3d1b6f972b6d30657b7c85c8b34506dc29b88 Author: Andrey V. Mashenkov Date: 2017-04-05T12:01:02Z IGNITE-4917: Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarshaller . This closes #1736. (cherry picked from commit 443ac9a) commit a0392605f39c23fcd20c98d852c4cab749cd059b Author: Andrey V. Mashenkov Date: 2017-04-06T11:43:50Z IGNITE-4832: Prevent service deployment on client by default when configuration is provided on startup. This closes #1748. (cherry picked from commit b7ab273) commit 3be4e00373ec5a2b49788d70eb0aebccc3cb6ccf Author: Alexander Fedotov Date: 2017-04-07T11:59:00Z Merge branch ignite-1.6.5 into ignite-1.8.5-p1 commit d81548d3a4e384e1a9b4adacf1fb487444bbfd33 Author: Alexander Fedotov Date: 2017-04-07T12:33:08Z Merge branch ignite-1.6.6-p1 into ignite-1.8.5-p1 commit 6954ff0c85f2f75507ee0bd306c879f490b4201a Author: Alexander Fedotov Date: 2017-04-07T12:44:48Z Merge branch ignite-1.6.12 into ignite-1.8.5-p1 commit 62dbba81c009170ff6243a28d3ef12fa75b96225 Author: Alexander Fedotov Date: 2017-04-07T12:46:11Z Merge branch ignite-1.7.4-p1 into ignite-1.8.5-p1 commit 4fce28054bc325741f65035ae384f9b4b9c3fee8 Author: Alexander Fedotov Date: 2017-04-07T13:06:34Z Merge branch ignite-1.8.4-p1 into ignite-1.8.5-p1 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java commit 220db882b466c03eadd148b3a19a0bf70d82d4a6 Author: dkarachentsev Date: 2017-04-10T07:28:15Z IGNITE-2466 - Use current NIO back pressure mechanism to limit received messages. Mark them process only when backups acknowledged. commit 3d616799efb472227b3b313516e6b40729654631 Author: dkarachentsev Date: 2017-04
[jira] [Created] (IGNITE-5844) Distributed versions of matrix decompositions
Yury Babak created IGNITE-5844: -- Summary: Distributed versions of matrix decompositions Key: IGNITE-5844 URL: https://issues.apache.org/jira/browse/IGNITE-5844 Project: Ignite Issue Type: New Feature Components: ml Reporter: Yury Babak We want to add support for distributed matrices. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5771) Add Ignite.setActive method to C++ API
[
https://issues.apache.org/jira/browse/IGNITE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101833#comment-16101833
]
ASF GitHub Bot commented on IGNITE-5771:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2348
IGNITE-5771: Added Ignite::SetActive() for C++
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5771
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2348.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 #2348
> Add Ignite.setActive method to C++ API
> --
>
> Key: IGNITE-5771
> URL: https://issues.apache.org/jira/browse/IGNITE-5771
> Project: Ignite
> Issue Type: New Feature
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.2
>
>
> Presently, {{Ignite.setActive}} method is unavailable in C++ API which means
> that there is now way to activate a cluster with the Ignite Persistent Store
> enabled from a C++ application side.
> Add this method and add a respective documentation paragraph to that section
> https://apacheignite-cpp.readme.io/v2.1/docs/ignite-persistence#section-usage
> in the same way as it's aleady done for .NET:
> https://apacheignite-net.readme.io/v2.1/docs/ignite-persistent-store#section-usage
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101820#comment-16101820 ] Semen Boikov commented on IGNITE-5712: -- Finished review, overall looks good, there are some minor comments: * in GridNearTxLocal.suspend/resume you check tx state, but state can be concurrently changed right after this check. Instead you need check that tx.state(SUSPENDED)/tx.state(ACTIVE) return 'true', if it returns 'false' throw exception, also move transaction map updates after tx.state(SUSPENDED)/tx.state(ACTIVE). * in TxManager.resumeTx you call 'txTop.set(tx.topologyVersionSnapshot());', why this is needed? I think tx.topologyVersionSnapshot() is always NONE there. * 'catch (Throwable e)' in CacheJtaResource.end, it is bad practice to catch Throwable, why not Exception? * to be on the safe side let's extend IgniteOptimisticTxSuspendResumeTest to run with more configurtions (You can use CacheOptimisticTransactionsWithFilterTest as example): ** with single node as it works now ** with multiple servers and clients, test operations are executed from both servers and clients ** test with near cache enabled ** test with changing topology: do some operations in tx, suspend tx, start new server node, resume tx and commit * is it possible to add in GridJtaTransactionManagerSelfTest case when tx is resumed from another thread? * 'public void threadId(long threadId) throws IgniteCheckedException' method does not throw exception, please remove 'throws' * no need to add @Nullable for assertThrowsWithCause, it never returns null * let's move IgniteOptimisticTxSuspendResumeTest and IgnitePessimisticTxSuspendResumeTest in IgniteCacheTestSuite6 Also please please merge latest changes from master. Thanks! > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101796#comment-16101796 ] Semen Boikov commented on IGNITE-5712: -- Asserts should not have any impact on performance when assertions are disabled, so add method 'boolean haveSystemTxForThread(long threadId)' and in resumeTx add: 'assert !haveSystemTxForThread(threadId)' > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[
https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101775#comment-16101775
]
Nikolay Izhikov commented on IGNITE-5712:
-
> Let's just add assert in TxManager.suspend() that tx is not system (assert
> !tx.system()).
OK.
> let's add such assert in TxManager.resumeTx.
It can't be done with simple assert since system transaction stored in map
`ConcurrentMap`
So check would be something like this.
Is it OK?
{code:java}
if (!sysThreadMap.isEmpty()) {
for (GridCacheContext cacheCtx :
cctx.cache().context().cacheContexts()) {
if (!cacheCtx.systemTx())
continue;
if (sysThreadMap.containsKey(new TxThreadKey(threadId,
cacheCtx.cacheId(
throw new IgniteCheckedException("Thread already start
system transaction.");
}
}
{code}
> Context switching for optimistic transactions
> -
>
> Key: IGNITE-5712
> URL: https://issues.apache.org/jira/browse/IGNITE-5712
> Project: Ignite
> Issue Type: Sub-task
> Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Nikolay Izhikov
>
> Implement context switching between threads for optimistic transactions
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101766#comment-16101766 ] Semen Boikov commented on IGNITE-5712: -- Hi, 1. System transactions are started by internal Ignite code, and it is supposed users can not access system txs. Let's just add assert in TxManager.suspend() that tx is not system (assert !tx.system()). 2. I think this is not possible case, but let's add such assert in TxManager.resumeTx. I'm reviewing your changes, will provide comments soon. Thanks! > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101727#comment-16101727 ] Nikolay Izhikov commented on IGNITE-5712: - [~sboikov] I have a couple of questions about this issue. Can you help me with answers? 1. Can we execute `tx.suspend()` for system transaction? Should we add some explicit check that user don't try to suspend system transaction? 2. Can we execute `tx.resume()` in the thread that already has an open system transaction? Is it a possilble case? Should we explicitly check that given thread has no system transaction already? > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-5834) .NET: Do not close transaction on async commit/rollback
[
https://issues.apache.org/jira/browse/IGNITE-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn closed IGNITE-5834.
--
> .NET: Do not close transaction on async commit/rollback
> ---
>
> Key: IGNITE-5834
> URL: https://issues.apache.org/jira/browse/IGNITE-5834
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.2
>
>
> Committed / rolled back transactions do not need to be closed.
> {{TransactionImpl.CloseWhenComplete}} and {{PlatformTransactions.txClose}}
> perform unnecessary work. This also causes problems with {{commitAsync}} and
> {{rollbackAsync}} since we close a transaction on another thread.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-5834) .NET: Do not close transaction on async commit/rollback
[
https://issues.apache.org/jira/browse/IGNITE-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-5834.
Resolution: Not A Problem
Not a problem actually:
{quote}
Currently tx is AutoCloseable and 'close' should be always called by
interface contract.
Currently Transaction is single-threaded and should not be used by multiple
concurrent threads. But if you call commitAsync and then call 'close' from
commitAsync listener this is correct usage and we should not prohibit
calling 'close' from another thread
{quote}
http://apache-ignite-developers.2346864.n4.nabble.com/Net-client-call-tx-close-in-other-thread-td20025.html
> .NET: Do not close transaction on async commit/rollback
> ---
>
> Key: IGNITE-5834
> URL: https://issues.apache.org/jira/browse/IGNITE-5834
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.2
>
>
> Committed / rolled back transactions do not need to be closed.
> {{TransactionImpl.CloseWhenComplete}} and {{PlatformTransactions.txClose}}
> perform unnecessary work. This also causes problems with {{commitAsync}} and
> {{rollbackAsync}} since we close a transaction on another thread.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5806) IgniteCache5 suite timed out, assertions in sessions close logic
[
https://issues.apache.org/jira/browse/IGNITE-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101722#comment-16101722
]
ASF GitHub Bot commented on IGNITE-5806:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2335
> IgniteCache5 suite timed out, assertions in sessions close logic
>
>
> Key: IGNITE-5806
> URL: https://issues.apache.org/jira/browse/IGNITE-5806
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
> Attachments: Ignite_2.0_Tests_Ignite_Cache_5_748.log.zip
>
>
> Ignite Cache 5 timeouts observed in master
> http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5&branch_Ignite20Tests=%3Cdefault%3E&tab=buildTypeStatusDiv
> Reproduced for builds 725, 740 and 748
> Log contains assertion coming from
> {code}
> !sesHolder.get().ended(store);
> {code}
> at
> {noformat} [2017-07-21
> 07:59:44,774][ERROR][sys-stripe-3-#117%cache.CacheSerializableTransactionsTest2%][G]
> Failed to execute runnable.
>
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionEnd0(GridCacheStoreManagerAdapter.java:878)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:335)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> {noformat}
> First time assertion came from test
> org.apache.ignite.internal.processors.cache.CacheSerializableTransactionsTest#testRandomOperations
> Assertion is reproducible locally. But test is considered passed
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5778) Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics and
[ https://issues.apache.org/jira/browse/IGNITE-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-5778: -- Summary: Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics and (was: Update JobMetrics on each job add/start/finish methods and add possibility to turn out JobMetrics and ) > Update JobMetrics on each job add/start/finish methods and add possibility to > turn off JobMetrics and > -- > > Key: IGNITE-5778 > URL: https://issues.apache.org/jira/browse/IGNITE-5778 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Evgenii Zhuravlev >Assignee: Evgenii Zhuravlev > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5778) Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics
[ https://issues.apache.org/jira/browse/IGNITE-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-5778: -- Summary: Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics (was: Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics and ) > Update JobMetrics on each job add/start/finish methods and add possibility to > turn off JobMetrics > - > > Key: IGNITE-5778 > URL: https://issues.apache.org/jira/browse/IGNITE-5778 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.9 >Reporter: Evgenii Zhuravlev >Assignee: Evgenii Zhuravlev > Fix For: 2.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5515) GridCacheReplicatedNodeRestartSelfTest hangs
[
https://issues.apache.org/jira/browse/IGNITE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5515:
---
Labels: MakeTeamcityGreenAgain test-fail (was: test-fail)
> GridCacheReplicatedNodeRestartSelfTest hangs
>
>
> Key: IGNITE-5515
> URL: https://issues.apache.org/jira/browse/IGNITE-5515
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
> Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
> Attachments:
> timedOut_CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart.log.zip
>
>
> Sample log:
> http://ci.ignite.apache.org/viewLog.html?buildId=06&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteDataGridRestarts
> Most probably this is the trigger:
> {code}
> [23:26:52]W: [org.apache.ignite:ignite-core] [2017-06-15
> 20:26:52,349][ERROR][sys-stripe-22-#191189%replicated.GridCacheReplicatedNodeRestartSelfTest3%][GridNearTxLocal]
> Commit failed.
> [23:26:52]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Commit produced a runtime exception (all transaction entries will be
> invalidated):
> GridDhtTxRemote[id=e8aef6dac51--067f-cbd2--0002,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=COMMITTING,
> invalidate=false, rollbackOnly=false,
> nodeId=64eba958-5741-4cee-ba4b-7ac75d81, duration=0]
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:721)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:790)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1208)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1116)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:177)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:175)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> [23:26:52]W: [org.apache.ignite:ignite-core]
[jira] [Commented] (IGNITE-5515) GridCacheReplicatedNodeRestartSelfTest hangs
[
https://issues.apache.org/jira/browse/IGNITE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101699#comment-16101699
]
Dmitriy Pavlov commented on IGNITE-5515:
Propably reproduced
http://ci.ignite.apache.org/viewLog.html?buildId=740686&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache5
logs from timed out test
CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart was
attached
> GridCacheReplicatedNodeRestartSelfTest hangs
>
>
> Key: IGNITE-5515
> URL: https://issues.apache.org/jira/browse/IGNITE-5515
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
> Labels: test-fail
> Fix For: 2.2
>
> Attachments:
> timedOut_CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart.log.zip
>
>
> Sample log:
> http://ci.ignite.apache.org/viewLog.html?buildId=06&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteDataGridRestarts
> Most probably this is the trigger:
> {code}
> [23:26:52]W: [org.apache.ignite:ignite-core] [2017-06-15
> 20:26:52,349][ERROR][sys-stripe-22-#191189%replicated.GridCacheReplicatedNodeRestartSelfTest3%][GridNearTxLocal]
> Commit failed.
> [23:26:52]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Commit produced a runtime exception (all transaction entries will be
> invalidated):
> GridDhtTxRemote[id=e8aef6dac51--067f-cbd2--0002,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=COMMITTING,
> invalidate=false, rollbackOnly=false,
> nodeId=64eba958-5741-4cee-ba4b-7ac75d81, duration=0]
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:721)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:790)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1208)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1116)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:177)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:175)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.jav
[jira] [Commented] (IGNITE-5807) Fix signing artifacts
[ https://issues.apache.org/jira/browse/IGNITE-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101692#comment-16101692 ] Oleg Ostanin commented on IGNITE-5807: -- [~avinogradov] Please look at the pr: https://github.com/apache/ignite/pull/2338 > Fix signing artifacts > - > > Key: IGNITE-5807 > URL: https://issues.apache.org/jira/browse/IGNITE-5807 > Project: Ignite > Issue Type: Bug >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > We need to fix pom.xml file to allow gpg plugin to sign .zip artifacts after > assembly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5515) GridCacheReplicatedNodeRestartSelfTest hangs
[
https://issues.apache.org/jira/browse/IGNITE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5515:
---
Attachment:
timedOut_CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart.log.zip
> GridCacheReplicatedNodeRestartSelfTest hangs
>
>
> Key: IGNITE-5515
> URL: https://issues.apache.org/jira/browse/IGNITE-5515
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
> Labels: test-fail
> Fix For: 2.2
>
> Attachments:
> timedOut_CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart.log.zip
>
>
> Sample log:
> http://ci.ignite.apache.org/viewLog.html?buildId=06&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteDataGridRestarts
> Most probably this is the trigger:
> {code}
> [23:26:52]W: [org.apache.ignite:ignite-core] [2017-06-15
> 20:26:52,349][ERROR][sys-stripe-22-#191189%replicated.GridCacheReplicatedNodeRestartSelfTest3%][GridNearTxLocal]
> Commit failed.
> [23:26:52]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Commit produced a runtime exception (all transaction entries will be
> invalidated):
> GridDhtTxRemote[id=e8aef6dac51--067f-cbd2--0002,
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=COMMITTING,
> invalidate=false, rollbackOnly=false,
> nodeId=64eba958-5741-4cee-ba4b-7ac75d81, duration=0]
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:721)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:790)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1208)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1116)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:177)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:175)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
> [23:26:52]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> [23:26:52]W: [org.apache.ign
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101676#comment-16101676 ] Nikolay Izhikov commented on IGNITE-5712: - Hello, [~sboikov], please, review my changes. > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101675#comment-16101675 ] Anton Vinogradov commented on IGNITE-5712: -- [~NIzhikov], Looks good to me, but we need to ask some expert to perform final check. > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5843) Ignite PDS: We don't save cache configuration if we get it on join
[ https://issues.apache.org/jira/browse/IGNITE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101650#comment-16101650 ] Eduard Shangareev edited comment on IGNITE-5843 at 7/26/17 1:18 PM: Pull request: https://github.com/apache/ignite/pull/2347 Test run: http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll&branch_Ignite20Tests=pull%2F2347%2Fhead&tab=buildTypeStatusDiv was (Author: edshanggg): Pull request: https://github.com/apache/ignite/pull/2347 > Ignite PDS: We don't save cache configuration if we get it on join > -- > > Key: IGNITE-5843 > URL: https://issues.apache.org/jira/browse/IGNITE-5843 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.2 > > > We don't save cache configuration when we get it on join (new node joins > cluster with cache which is not presented on config or on disk). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5843) Ignite PDS: We don't save cache configuration if we get it on join
[ https://issues.apache.org/jira/browse/IGNITE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101650#comment-16101650 ] Eduard Shangareev commented on IGNITE-5843: --- Pull request: https://github.com/apache/ignite/pull/2347 > Ignite PDS: We don't save cache configuration if we get it on join > -- > > Key: IGNITE-5843 > URL: https://issues.apache.org/jira/browse/IGNITE-5843 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.2 > > > We don't save cache configuration when we get it on join (new node joins > cluster with cache which is not presented on config or on disk). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5843) Ignite PDS: We don't save cache configuration if we get it on join
[ https://issues.apache.org/jira/browse/IGNITE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101648#comment-16101648 ] ASF GitHub Bot commented on IGNITE-5843: GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/2347 IGNITE-5843 Ignite PDS: We don't save cache configuration if we get i… …t on join You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5843 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2347.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 #2347 commit 3db78535fbb84dd37d2f178649edf6b9a4116513 Author: EdShangGG Date: 2017-07-26T12:54:30Z IGNITE-5843 Ignite PDS: We don't save cache configuration if we get it on join > Ignite PDS: We don't save cache configuration if we get it on join > -- > > Key: IGNITE-5843 > URL: https://issues.apache.org/jira/browse/IGNITE-5843 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.2 > > > We don't save cache configuration when we get it on join (new node joins > cluster with cache which is not presented on config or on disk). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5807) Fix signing artifacts
[ https://issues.apache.org/jira/browse/IGNITE-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin updated IGNITE-5807: - Summary: Fix signing artifacts (was: Fixing signing artifacts) > Fix signing artifacts > - > > Key: IGNITE-5807 > URL: https://issues.apache.org/jira/browse/IGNITE-5807 > Project: Ignite > Issue Type: Bug >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > We need to fix pom.xml file to allow gpg plugin to sign .zip artifacts after > assembly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5833) Change maven goal from "install" to "package" for building from sour
[ https://issues.apache.org/jira/browse/IGNITE-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin updated IGNITE-5833: - Summary: Change maven goal from "install" to "package" for building from sour (was: Changing maven goal from "install" to "package" for building from sources) > Change maven goal from "install" to "package" for building from sour > > > Key: IGNITE-5833 > URL: https://issues.apache.org/jira/browse/IGNITE-5833 > Project: Ignite > Issue Type: Bug >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > Currently we need to run 'mvn clean install' to build Apache Ignite from > sources, otherwise we can not perform javadoc generation in the next build > step in DEVNOTES.txt. We need to fix this issue before next release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5817) Change checksum calculation methods
[ https://issues.apache.org/jira/browse/IGNITE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ostanin updated IGNITE-5817: - Summary: Change checksum calculation methods (was: Changing checksum calculation methods) > Change checksum calculation methods > --- > > Key: IGNITE-5817 > URL: https://issues.apache.org/jira/browse/IGNITE-5817 > Project: Ignite > Issue Type: Bug >Reporter: Oleg Ostanin >Assignee: Oleg Ostanin > Fix For: 2.2 > > > Neither sha1 nor md5 are trustful checksum calculation methods. We should be > switching to at least sha265 or higher. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5468) Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis
[ https://issues.apache.org/jira/browse/IGNITE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101615#comment-16101615 ] Vitaliy Biryukov commented on IGNITE-5468: --- [~amashenkov], Done. > Need to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE on per query basis > -- > > Key: IGNITE-5468 > URL: https://issues.apache.org/jira/browse/IGNITE-5468 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.0 >Reporter: Yakov Zhdanov >Assignee: Vitaliy Biryukov >Priority: Critical > Fix For: 2.2 > > > Currently this property can be set via sys property only thus changing it > will require restart of the cluster. I think it is better to set it on > perquery basis with some default that is configured via cache configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)
[
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101602#comment-16101602
]
Alexandr Kuramshin commented on IGNITE-4767:
Hi, [~dpavlov],
Suppressed exceptions will be automatically logged when stack trace is printed.
Actually we should not worry about it.
I've found only this TC run in history, related to the 1599 PR
http://195.239.208.174/viewType.html?buildTypeId=IgniteTests_IgniteCache3&tab=buildTypeStatusDiv&branch_IgniteTests=pull%2F1599%2Fhead
Testing was done 2 months ago after merging with the master, I think
Ignite20Tests was not present at that time.
> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Alexey Goncharuk
> Fix For: 2.2
>
>
> There is too much code places like:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e) {
> tx.rollbackAsync();
> throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
> try {
> tx.rollbackAsync();
> }
> catch (Throwable inner) {
> e.addSuppressed(inner);
> }
> throw e;
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5843) Ignite PDS: We don't save cache configuration if we get it on join
Eduard Shangareev created IGNITE-5843: - Summary: Ignite PDS: We don't save cache configuration if we get it on join Key: IGNITE-5843 URL: https://issues.apache.org/jira/browse/IGNITE-5843 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.1 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Priority: Critical Fix For: 2.2 We don't save cache configuration when we get it on join (new node joins cluster with cache which is not presented on config or on disk). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-537) Continuous processor should support p2p deployment on discovery data exchange
[ https://issues.apache.org/jira/browse/IGNITE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Dmitriev updated IGNITE-537: --- Priority: Major (was: Critical) > Continuous processor should support p2p deployment on discovery data exchange > - > > Key: IGNITE-537 > URL: https://issues.apache.org/jira/browse/IGNITE-537 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Assignee: Yakov Zhdanov > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5174) Need to have opportunity to list only server nodes for specified topology version
[ https://issues.apache.org/jira/browse/IGNITE-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101573#comment-16101573 ] Dmitriy Pavlov commented on IGNITE-5174: Hi, [~zstan], I've checked you changes and it seems to be OK. > Need to have opportunity to list only server nodes for specified topology > version > - > > Key: IGNITE-5174 > URL: https://issues.apache.org/jira/browse/IGNITE-5174 > Project: Ignite > Issue Type: Bug >Reporter: Stanilovsky Evgeny >Assignee: Alexey Goncharuk >Priority: Minor > Fix For: 2.2 > > > Need to have common utility function which filters client nodes for specified > topology version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)
[
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101556#comment-16101556
]
Dmitriy Pavlov commented on IGNITE-4767:
Hi, [~ein],
I've checked the change and it seems to be OK.
In the same time e.getSuppressed() is never called. Is it indended to be logged
into apache log throught printStackTrace. Is suppressed exception logged
automatically or any additional change is required?
One more question, could you please share the link to TC run? Was it in
Ignite20Tests?
> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Alexey Goncharuk
> Fix For: 2.2
>
>
> There is too much code places like:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e) {
> tx.rollbackAsync();
> throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
> return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
> try {
> tx.rollbackAsync();
> }
> catch (Throwable inner) {
> e.addSuppressed(inner);
> }
> throw e;
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5842) ODBC: Make sure ODBC driver works correctly with RazorSQL.
Igor Sapego created IGNITE-5842:
---
Summary: ODBC: Make sure ODBC driver works correctly with RazorSQL.
Key: IGNITE-5842
URL: https://issues.apache.org/jira/browse/IGNITE-5842
Project: Ignite
Issue Type: Improvement
Components: odbc
Affects Versions: 2.0
Reporter: Igor Sapego
Users often try to use ODBC driver to connect to Ignite with RazorSQL. However,
it can't be used with our driver, as it tries to configure driver to act
according to unsupported ODBC version. Here is the log:
{noformat}
razorsql12d8-1374 ENTER SQLAllocEnv
HENV * 0x2FBEECB0
razorsql12d8-1374 EXIT SQLAllocEnv with return code 0
(SQL_SUCCESS)
HENV * 0x2FBEECB0 ( 0x003DE650)
razorsql12d8-1374 ENTER SQLAllocConnect
HENV0x003DE650
HDBC * 0x2FBEEC10
razorsql12d8-1374 EXIT SQLAllocConnect with return code 0
(SQL_SUCCESS)
HENV0x003DE650
HDBC * 0x2FBEEC10 ( 0x003DE6D0)
razorsql12d8-1374 ENTER SQLSetConnectOption
HDBC0x003DE6D0
SQLINTEGER 103
SQLPOINTER35
razorsql12d8-1374 EXIT SQLSetConnectOption with return code 0
(SQL_SUCCESS)
HDBC0x003DE6D0
SQLINTEGER 103
SQLPOINTER35
razorsql12d8-1374 ENTER SQLDriverConnectW
HDBC0x003DE6D0
HWND0x
WCHAR * 0x6F861F7C [ -3] "**\ 0"
SWORD -3
WCHAR * 0x6F861F7C
SWORD -3
SWORD * 0x
UWORD0
razorsql12d8-1374 EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC0x003DE6D0
HWND0x
WCHAR * 0x6F861F7C [ -3] "**\ 0"
SWORD -3
WCHAR * 0x6F861F7C
SWORD -3
SWORD * 0x
UWORD0
DIAG [S1000] ODBC version is not supported. (0)
DIAG [08001] Failed to establish connection with the host. (0)
razorsql12d8-1374 ENTER SQLErrorW
HENV0x
HDBC0x003DE6D0
HSTMT 0x
WCHAR * 0x2FBEEAF4
SDWORD *0x2FBEEB3C
WCHAR * 0x2FBEE6F4
SWORD 300
SWORD * 0x2FBEEB38
razorsql12d8-1374 EXIT SQLErrorW with return code 0
(SQL_SUCCESS)
HENV0x
HDBC0x003DE6D0
HSTMT 0x
WCHAR * 0x2FBEEAF4 [ 5] "S1000"
SDWORD *0x2FBEEB3C (0)
WCHAR * 0x2FBEE6F4 [ 30] "ODBC version is not
supported."
SWORD 300
SWORD * 0x2FBEEB38 (30)
razorsql12d8-1374 ENTER SQLErrorW
HENV0x
HDBC0x003DE6D0
HSTMT 0x
WCHAR * 0x2FBEEAF4
SDWORD *0x2FBEEB3C
WCHAR * 0x2FBEE6F4
SWORD 300
SWORD * 0x2FBEEB38
razorsql12d8-1374 EXIT SQLErrorW with return code 0
(SQL_SUCCESS)
HENV0x
HDBC0x003DE6D0
HSTMT 0x
WCHAR * 0x2FBEEAF4 [ 5] "08001"
SDWORD *0x2FBEEB3C (0)
WCHAR * 0x2FBEE6F4 [ 45] "Failed to establish
connection with the host."
SWORD 300
SWORD * 0x2FBEEB38 (45)
razorsql12d8-1374 ENTER SQLErrorW
HENV0x
HDBC0x003DE6D0
HSTMT 0x
WCHAR * 0x2FBEEAF4
SDWORD *0x2FBEEB3C
[jira] [Created] (IGNITE-5841) Ignite SPI Suite: testReconnectAfterFailTopologyChanged() test failure with assertions
Dmitriy Pavlov created IGNITE-5841:
--
Summary: Ignite SPI Suite: testReconnectAfterFailTopologyChanged()
test failure with assertions
Key: IGNITE-5841
URL: https://issues.apache.org/jira/browse/IGNITE-5841
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Found during PR testing, but fails also for master
http://ci.ignite.apache.org/viewLog.html?buildId=740511&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteSpi
There is flaky test failing in different suites
TcpClientDiscoverySpiFailureTimeoutSelfTest.testReconnectAfterFailTopologyChanged
Success rate 82,1%
{noformat}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.reconnectAfterFail(TcpClientDiscoverySpiSelfTest.java:1422)
at
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testReconnectAfterFailTopologyChanged(TcpClientDiscoverySpiSelfTest.java:1331)
{noformat}
TcpClientDiscoverySpiSelfTest.testReconnectAfterFailTopologyChanged
Success rate 84,3%
{noformat}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.reconnectAfterFail(TcpClientDiscoverySpiSelfTest.java:1422)
at
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testReconnectAfterFailTopologyChanged(TcpClientDiscoverySpiSelfTest.java:1331)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5061) Add ability to enable and disable rebalancing per-node
[ https://issues.apache.org/jira/browse/IGNITE-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101522#comment-16101522 ] Alexander Belyak commented on IGNITE-5061: -- Fixed - create new branch with only relevant changes > Add ability to enable and disable rebalancing per-node > -- > > Key: IGNITE-5061 > URL: https://issues.apache.org/jira/browse/IGNITE-5061 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexey Goncharuk >Assignee: Alexander Belyak > Fix For: 2.2 > > > It would be nice to have an ability to enable and disable rebalancing per > node. > First of all, we need to come up with a simple API to allow this. > Corresponding methods most likely should be also added to Ignite MBean. > We need to discuss on the dev-list whether it is enough to have this setting > per-node, or this needs to be done on a per-cache basis. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator
[
https://issues.apache.org/jira/browse/IGNITE-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5741:
---
Labels: MakeTeamcityGreenAgain (was: )
> Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator
> -
>
> Key: IGNITE-5741
> URL: https://issues.apache.org/jira/browse/IGNITE-5741
> Project: Ignite
> Issue Type: Task
> Components: persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>Assignee: Ilya Lantukh
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> In current implementation we can get OOM during iterate on wal records,
> because some wal record may be very large (more that 64Mb). We read using
> HeapByteBuffer, FileChannel reserve buffer same size as our HeapByteBuffer,
> but by default FileChannel can not allocate buffer more that 64Mb. (maxMemory
> = VM.maxDirectMemory())
> java-7-oracle
> {code}
> [16:07:54]W: [org.apache.ignite:ignite-core] [2017-07-12
> 13:07:54,809][ERROR][exchange-worker-#55966%node0-primary%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=3,
> minorTopVer=1], nodeId=105056d5, evt=DISCOVERY_CUSTOM_EVT]
> [16:07:54]W: [org.apache.ignite:ignite-core]
> java.lang.OutOfMemoryError: Direct buffer memory
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.Bits.reserveMemory(Bits.java:658)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.DirectByteBuffer.(DirectByteBuffer.java:123)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:306)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.Util.getTemporaryDirectBuffer(Util.java:174)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.IOUtil.read(IOUtil.java:195)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:149)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:62)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:116)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:303)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:376)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:385)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:697)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:673)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:243)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.advanceSegment(FileWriteAheadLogManager.java:2452)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:149)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2352)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.(FileWriteAheadLogManager.java:2290)
> [16:07:54]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.replay(FileWriteAheadLogManager.java:553)
> [16:07:54]W: [org.apache.ignite:igni
[jira] [Updated] (IGNITE-5840) IgniteUuid could not be used as a cache key
[
https://issues.apache.org/jira/browse/IGNITE-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-5840:
Component/s: cache
> IgniteUuid could not be used as a cache key
> ---
>
> Key: IGNITE-5840
> URL: https://issues.apache.org/jira/browse/IGNITE-5840
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>
> Following test fails in 2.0+
> {code:java}
> IgniteUuid id = IgniteUuid.randomUuid();
> cache.put(id, "1");
> assertNotNull(cache.get(id));
> {code}
> Reproducer is in [PR 2346 | https://github.com/apache/ignite/pull/2346]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5840) IgniteUuid could not be used as a cache key
[
https://issues.apache.org/jira/browse/IGNITE-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-5840:
Description:
Following test fails in 2.0+
{code:java}
IgniteUuid id = IgniteUuid.randomUuid();
cache.put(id, "1");
assertNotNull(cache.get(id));
{code}
Reproducer is in [PR 2346 | https://github.com/apache/ignite/pull/2346]
was:
Following test fails in 2.0+
{code:java}
IgniteUuid id = IgniteUuid.randomUuid();
cache.put(id, "1");
assertNotNull(cache.get(id));
{code}
> IgniteUuid could not be used as a cache key
> ---
>
> Key: IGNITE-5840
> URL: https://issues.apache.org/jira/browse/IGNITE-5840
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>
> Following test fails in 2.0+
> {code:java}
> IgniteUuid id = IgniteUuid.randomUuid();
> cache.put(id, "1");
> assertNotNull(cache.get(id));
> {code}
> Reproducer is in [PR 2346 | https://github.com/apache/ignite/pull/2346]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5840) IgniteUuid could not be used as a cache key
[
https://issues.apache.org/jira/browse/IGNITE-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-5840:
Affects Version/s: 2.0
> IgniteUuid could not be used as a cache key
> ---
>
> Key: IGNITE-5840
> URL: https://issues.apache.org/jira/browse/IGNITE-5840
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.0
>Reporter: Dmitry Karachentsev
>
> Following test fails in 2.0+
> {code:java}
> IgniteUuid id = IgniteUuid.randomUuid();
> cache.put(id, "1");
> assertNotNull(cache.get(id));
> {code}
> Reproducer is in [PR 2346 | https://github.com/apache/ignite/pull/2346]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5840) IgniteUuid could not be used as a cache key
[
https://issues.apache.org/jira/browse/IGNITE-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101504#comment-16101504
]
ASF GitHub Bot commented on IGNITE-5840:
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2346
IGNITE-5840 - Reproducer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5840
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2346.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 #2346
commit 65ea9f8471c957520d87a23bb701703789a20942
Author: dkarachentsev
Date: 2017-07-26T10:21:14Z
IGNITE-5840 - Reproducer
> IgniteUuid could not be used as a cache key
> ---
>
> Key: IGNITE-5840
> URL: https://issues.apache.org/jira/browse/IGNITE-5840
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitry Karachentsev
>
> Following test fails in 2.0+
> {code:java}
> IgniteUuid id = IgniteUuid.randomUuid();
> cache.put(id, "1");
> assertNotNull(cache.get(id));
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5840) IgniteUuid could not be used as a cache key
Dmitry Karachentsev created IGNITE-5840:
---
Summary: IgniteUuid could not be used as a cache key
Key: IGNITE-5840
URL: https://issues.apache.org/jira/browse/IGNITE-5840
Project: Ignite
Issue Type: Bug
Reporter: Dmitry Karachentsev
Following test fails in 2.0+
{code:java}
IgniteUuid id = IgniteUuid.randomUuid();
cache.put(id, "1");
assertNotNull(cache.get(id));
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5803) IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed, stable reproducible locally
[
https://issues.apache.org/jira/browse/IGNITE-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-5803:
--
Assignee: Dmitriy Pavlov
> IgniteCacheTestSuite4: IgniteCacheInvokeReadThroughTest: 6 test failed,
> stable reproducible locally
> ---
>
> Key: IGNITE-5803
> URL: https://issues.apache.org/jira/browse/IGNITE-5803
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=738392&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteCache4
> org.apache.ignite.testsuites.IgniteCacheTestSuite4:
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughAtomicReplicated
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx0
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx1
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTx2
>
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughTest.testInvokeReadThroughTxReplicated
> All failed with
> {noformat}
> junit.framework.AssertionFailedError: null
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.fail(Assert.java:64)
> at junit.framework.TestCase.fail(TestCase.java:235)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheInvokeReadThroughAbstractTest$TestEntryProcessor.process(IgniteCacheInvokeReadThroughAbstractTest.java:362)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.applyTransformClosures(IgniteTxAdapter.java:1465)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.batchStoreCommit(IgniteTxAdapter.java:1221)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:501)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3030)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes
[
https://issues.apache.org/jira/browse/IGNITE-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-1776:
---
Labels: MakeTeamcityGreenAgain Muted_test (was: Muted_test)
> [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails
> sometimes
> ---
>
> Key: IGNITE-1776
> URL: https://issues.apache.org/jira/browse/IGNITE-1776
> Project: Ignite
> Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
> Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.2
>
>
> TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails on TC
> sometimes.
> Looks like a test bug, need just increase awaitTime(). I see Node FAILED
> message exactly after 10 seconds. But it's strange that it's require too long
> time. May be something wrong on agent.
> Logs:
> {noformat}
> junit.framework.AssertionFailedError: Latch count: 1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.await(TcpClientDiscoverySpiSelfTest.java:2030)
> at
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer(TcpClientDiscoverySpiSelfTest.java:811)
> --- Stdout: ---
> [03:18:46,228][INFO ][main][root] >>> Starting test:
> testClientNodeFailOneServer <<<
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0]
> >>>__
> >>> / _/ ___/ |/ / _/_ __/ __/
> >>> _/ // (7 7// / / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Config URL: n/a
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Daemon mode: off
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS: Mac OS X 10.7.5
> x86_64
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS user: teamcity
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Language runtime:
> Java Platform API Specification ver. 1.7
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM information:
> Java(TM) SE Runtime Environment 1.7.0_67-b01 Oracle Corporation Java
> HotSpot(TM) 64-Bit Server VM 24.65-b04
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM total memory:
> 2.7GB
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Remote Management
> [restart: off, REST: off, JMX (remote: off)]
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0]
> IGNITE_HOME=/Users/teamcity/buildAgent/work/871ff4a46e450b13
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM arguments:
> [-DJAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home,
> -DMCAST_GRP=229.116.1.2, -Dagent.home.dir=/Users/teamcity/buildAgent,
> -Dagent.name=ip_192.168.1.116, -Dagent.ownPort=9090,
> -Dagent.work.dir=/Users/teamcity/buildAgent/work, -Dbuild.number=3345,
> -Dbuild.vcs.number=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
> -Dbuild.vcs.number.1=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
> -Dbuild.vcs.number.ApacheIgniteMirrorOnGitHub=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
>
> -Dclassworlds.conf=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.m2.conf,
> -Dcom.jetbrains.maven.watcher.report.file=/Users/teamcity/buildAgent/temp/buildTmp/maven-build-info.xml,
> -Djava.io.tmpdir=/Users/teamcity/buildAgent/temp/buildTmp,
> -Dmaven.home=/Users/teamcity/buildAgent/tools/maven3,
> -Dmaven.repo.local=/Users/teamcity/.m2/repository,
> -Dteamcity.agent.cpuBenchmark=605,
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2,
> -Dteamcity.agent.dotnet.build_id=555612,
> -Dteamcity.auth.password=j1gKlVPBOa3H6Wnrjp3Q3sK7ZqR4biuf,
> -Dteamcity.auth.userId=TeamCityBuildId=555612,
> -Dteamcity.build.changedFiles.file=/Users/teamcity/buildAgent/temp/buildTmp/changedFiles5940678572218707636.txt,
>
> -Dteamcity.build.checkoutDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
> -Dteamcity.build.id=555612,
> -Dteamcity.build.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.build3844607694634646095.properties,
> -Dteamcity.build.tempDir=/Users/teamcity/buildAgent/temp/buildTmp,
> -Dteamcity.build.workingDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
> -Dteamcity.buildConfName=Ignite SPI, -Dteamcity.buildType.id=Ignite_Spi,
> -Dteamcity.configuration.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.config8915518964213838573.properties,
> -Dteamcity.idea.home=/Users/te
[jira] [Commented] (IGNITE-4181) The several runs of ServicesExample causes NPE
[
https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101485#comment-16101485
]
Andrey Kuznetsov commented on IGNITE-4181:
--
[~avinogradov], Please review our changes. Public API reproducer was added
recently.
> The several runs of ServicesExample causes NPE
> --
>
> Key: IGNITE-4181
> URL: https://issues.apache.org/jira/browse/IGNITE-4181
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6, 1.7, 2.0
> Environment: Windows 10, Oracle JDK 7
>Reporter: Sergey Kozlov
>Assignee: Dmitriy Sorokin
> Labels: newbie
> Fix For: 2.2
>
>
> 0. Open example project in IDEA
> 1. Start 2-3 {{ExampleNodeStartup}}
> 2. Run {{ServicesExample}} several times.
> Sometimes it causes NullPointerException:
> {noformat}
> Executing closure [mapSize=10]
> Service was cancelled: myNodeSingletonService
> [15:37:20,020][INFO ][srvc-deploy-#24%null%][GridServiceProcessor] Cancelled
> service instance [name=myNodeSingletonService,
> execId=88a92a4d-c1cb-4a9b-8930-c67ac7f42bf3]
> [15:37:20,032][INFO ][sys-#33%null%][GridCacheProcessor] Stopped cache:
> myNodeSingletonService
> [15:37:20,033][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=4], evt=DISCOVERY_CUSTOM_EVT,
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,045][INFO ][sys-#39%null%][GridCacheProcessor] Stopped cache:
> myClusterSingletonService
> [15:37:20,046][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=5], evt=DISCOVERY_CUSTOM_EVT,
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,062][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager]
> Node left topology: TcpDiscoveryNode
> [id=4f9cbc67-d756-4c25-9ee4-aee6528da024, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
> 172.25.4.107, 2001:0:9d38:6ab8:34b2:9f3e:3c6f:269],
> sockAddrs=[/2001:0:9d38:6ab8:34b2:9f3e:3c6f:269:0, /127.0.0.1:0,
> /0:0:0:0:0:0:0:1:0, work-pc/172.25.4.107:0], discPort=0, order=10,
> intOrder=7, lastExchangeTime=1478522239236, loc=false,
> ver=1.7.3#20161107-sha1:5132ac87, isClient=true]
> [15:37:20,063][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager]
> Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=11.0GB]
> [15:37:20,064][INFO ][sys-#44%null%][GridCacheProcessor] Stopped cache:
> myMultiService
> [15:37:20,066][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=6], evt=DISCOVERY_CUSTOM_EVT,
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,076][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started
> cache [name=myClusterSingletonService, mode=PARTITIONED]
> [15:37:20,115][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=7], evt=DISCOVERY_CUSTOM_EVT,
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,121][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=11,
> minorTopVer=0], evt=NODE_LEFT, node=4f9cbc67-d756-4c25-9ee4-aee6528da024]
> [15:37:20,133][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started
> cache [name=myMultiService, mode=PARTITIONED]
> [15:37:20,135][ERROR][exchange-worker-#23%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=11,
> minorTopVer=1], nodeId=5faac72a, evt=DISCOVERY_CUSTOM_EVT]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedCacheOnCoordinator(CacheAffinitySharedManager.java:743)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:413)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:565)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:448)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1447)
> at
> org.apache.ignite.internal.util.worker.GridWo
[jira] [Updated] (IGNITE-5504) Failures in GridTcpCommunicationSpiRecoverySelfTest
[
https://issues.apache.org/jira/browse/IGNITE-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5504:
---
Labels: MakeTeamcityGreenAgain Muted_test test-fail (was: test-fail)
> Failures in GridTcpCommunicationSpiRecoverySelfTest
> ---
>
> Key: IGNITE-5504
> URL: https://issues.apache.org/jira/browse/IGNITE-5504
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Ozerov
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
>
> Reproducible only on TeamCity.
> Affected tests:
> {{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead1}}
> {{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead2}}
> {{GridTcpCommunicationSpiRecoverySelfTest.testBlockRead3}}
> Root cause:
> {code}
> [2017-06-14 18:16:30,016][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Failed to wait for session close
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.spi.communication.tcp.GridTcpCommunicationSpiRecoverySelfTest.testBlockRead1(GridTcpCommunicationSpiRecoverySelfTest.java:333)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1992)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1907)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4181) The several runs of ServicesExample causes NPE
[
https://issues.apache.org/jira/browse/IGNITE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101475#comment-16101475
]
Anton Vinogradov commented on IGNITE-4181:
--
[~cyberdemon]
I'll check it soon.
> The several runs of ServicesExample causes NPE
> --
>
> Key: IGNITE-4181
> URL: https://issues.apache.org/jira/browse/IGNITE-4181
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6, 1.7, 2.0
> Environment: Windows 10, Oracle JDK 7
>Reporter: Sergey Kozlov
>Assignee: Dmitriy Sorokin
> Labels: newbie
> Fix For: 2.2
>
>
> 0. Open example project in IDEA
> 1. Start 2-3 {{ExampleNodeStartup}}
> 2. Run {{ServicesExample}} several times.
> Sometimes it causes NullPointerException:
> {noformat}
> Executing closure [mapSize=10]
> Service was cancelled: myNodeSingletonService
> [15:37:20,020][INFO ][srvc-deploy-#24%null%][GridServiceProcessor] Cancelled
> service instance [name=myNodeSingletonService,
> execId=88a92a4d-c1cb-4a9b-8930-c67ac7f42bf3]
> [15:37:20,032][INFO ][sys-#33%null%][GridCacheProcessor] Stopped cache:
> myNodeSingletonService
> [15:37:20,033][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=4], evt=DISCOVERY_CUSTOM_EVT,
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,045][INFO ][sys-#39%null%][GridCacheProcessor] Stopped cache:
> myClusterSingletonService
> [15:37:20,046][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=5], evt=DISCOVERY_CUSTOM_EVT,
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,062][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager]
> Node left topology: TcpDiscoveryNode
> [id=4f9cbc67-d756-4c25-9ee4-aee6528da024, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
> 172.25.4.107, 2001:0:9d38:6ab8:34b2:9f3e:3c6f:269],
> sockAddrs=[/2001:0:9d38:6ab8:34b2:9f3e:3c6f:269:0, /127.0.0.1:0,
> /0:0:0:0:0:0:0:1:0, work-pc/172.25.4.107:0], discPort=0, order=10,
> intOrder=7, lastExchangeTime=1478522239236, loc=false,
> ver=1.7.3#20161107-sha1:5132ac87, isClient=true]
> [15:37:20,063][INFO ][disco-event-worker-#20%null%][GridDiscoveryManager]
> Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=11.0GB]
> [15:37:20,064][INFO ][sys-#44%null%][GridCacheProcessor] Stopped cache:
> myMultiService
> [15:37:20,066][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=6], evt=DISCOVERY_CUSTOM_EVT,
> node=5faac72a-72ab-4277-9643-0e962973b3f4]
> [15:37:20,076][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started
> cache [name=myClusterSingletonService, mode=PARTITIONED]
> [15:37:20,115][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=10,
> minorTopVer=7], evt=DISCOVERY_CUSTOM_EVT,
> node=478f1752-fdce-42c6-aef6-55a5f4c08d90]
> [15:37:20,121][INFO
> ][exchange-worker-#23%null%][GridCachePartitionExchangeManager] Skipping
> rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=11,
> minorTopVer=0], evt=NODE_LEFT, node=4f9cbc67-d756-4c25-9ee4-aee6528da024]
> [15:37:20,133][INFO ][exchange-worker-#23%null%][GridCacheProcessor] Started
> cache [name=myMultiService, mode=PARTITIONED]
> [15:37:20,135][ERROR][exchange-worker-#23%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=11,
> minorTopVer=1], nodeId=5faac72a, evt=DISCOVERY_CUSTOM_EVT]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedCacheOnCoordinator(CacheAffinitySharedManager.java:743)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:413)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:565)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:448)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1447)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.T
[jira] [Assigned] (IGNITE-5835) Implement highlight item in non-multiple dropdown
[ https://issues.apache.org/jira/browse/IGNITE-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-5835: Assignee: Andrey Novikov (was: Dmitriy Shabalin) Added improvments, pls review it > Implement highlight item in non-multiple dropdown > - > > Key: IGNITE-5835 > URL: https://issues.apache.org/jira/browse/IGNITE-5835 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Affects Versions: 2.2 >Reporter: Dmitriy Shabalin >Assignee: Andrey Novikov > > 1) Hide checkboxes in single dropdown > 2) Add highlight to selected item in single dropdown -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101455#comment-16101455 ] Nikolay Izhikov commented on IGNITE-5712: - TC run - http://ci.ignite.apache.org/viewLog.html?buildId=740472&tab=queuedBuildOverviewTab I run locally new failed tests both in upstream/master and my branch. Here is results: ||Test name||upstream/master||pull/2334/head|| |IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover |OK|OK| |IgniteCachePutRetryTransactionalSelfTest.testPutAsync |OK|OK| |GridCachePutAllFailoverSelfTest.testPutAllFailoverNearEnabledThreeBackups|OK|OK| |IgfsLocalSecondaryFileSystemProxyClientSelfTest.testAppendRenameNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxyClientSelfTest.testAppendRenameParentNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxyClientSelfTest.testCreateRenameNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxyClientSelfTest.testCreateRenameParentNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxySelfTest.testAppendRenameNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxySelfTest.testAppendRenameParentNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxySelfTest.testCreateRenameNoClose|FAIL|FAIL| |IgfsLocalSecondaryFileSystemProxySelfTest.testCreateRenameParentNoClose|FAIL|FAIL| |IgniteIgfsLinuxAndMacOSTestSuite.initializationError|can't run|can't run| |RedisProtocolStringSelfTest.testSetRange|OK|OK| .Net test fails is related to .Net client issue. See my conversation with PTupytsin \[1\] \[1\] http://apache-ignite-developers.2346864.n4.nabble.com/Net-client-call-tx-close-in-other-thread-td20025.html > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-5712) Context switching for optimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-5712: Comment: was deleted (was: TC results http://ci.ignite.apache.org/viewLog.html?buildId=738315&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAll Timeouted suits rerun: http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataStrucutures&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteLogging&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataGridRestarts&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache5&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCache3&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteCacheFailover2&branch_Ignite20Tests=pull%2F2334%2Fhead&tab=buildTypeStatusDiv ) > Context switching for optimistic transactions > - > > Key: IGNITE-5712 > URL: https://issues.apache.org/jira/browse/IGNITE-5712 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Nikolay Izhikov > > Implement context switching between threads for optimistic transactions -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-5800) Umbrella ticket for making Teamcity Green Again
[ https://issues.apache.org/jira/browse/IGNITE-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101433#comment-16101433 ] Dmitriy Pavlov edited comment on IGNITE-5800 at 7/26/17 9:27 AM: - This task is more similar to continious process than to particular issue with completion creteria. Filters were moved to wiki page https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again This task is closed as not necessary was (Author: dpavlov): This task is more like continious process that issue. Filters were moved to wiki page https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again This task is closed as not necessary > Umbrella ticket for making Teamcity Green Again > --- > > Key: IGNITE-5800 > URL: https://issues.apache.org/jira/browse/IGNITE-5800 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov > > *Discussions* > http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html > http://apache-ignite-developers.2346864.n4.nabble.com/Make-Teamcity-Green-Again-td19873.html > *Goal* > To allow community to grow more quickly and from the CI perspective, failing > tests should be the main concern > For Run All dependencies at Ignite 20 Tests > http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=%3Cdefault%3E > there should be no stable red suites. timed out suites and stable red tests. > *Priorities* > Following priorities are suggested for issues > - Test suite timeout - it hides real test failures from us and wastes agent > time > - Stable failing test - 50-100% of failures - issue is to be created as > blocked to the next release, test should be muted. > - Flaky tests 1%-50% of failures, which are considered by teamcity as flaky > may be not muted for now because TC interface helps us to identify these > tests. > *Scope* > TBD by JIRA queries > Failures not muted > https://issues.apache.org/jira/issues/?jql=labels%20%3D%20MakeTeamcityGreenAgain%20and%20labels%20!%3D%20Muted_test%20and%20resolution%20is%20EMPTY -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-5800) Umbrella ticket for making Teamcity Green Again
[ https://issues.apache.org/jira/browse/IGNITE-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-5800. Resolution: Information Provided This task is more like continious process that issue. Filters were moved to wiki page https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again This task is closed as not necessary > Umbrella ticket for making Teamcity Green Again > --- > > Key: IGNITE-5800 > URL: https://issues.apache.org/jira/browse/IGNITE-5800 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov > > *Discussions* > http://apache-ignite-developers.2346864.n4.nabble.com/Test-failures-td14353.html > http://apache-ignite-developers.2346864.n4.nabble.com/Make-Teamcity-Green-Again-td19873.html > *Goal* > To allow community to grow more quickly and from the CI perspective, failing > tests should be the main concern > For Run All dependencies at Ignite 20 Tests > http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=%3Cdefault%3E > there should be no stable red suites. timed out suites and stable red tests. > *Priorities* > Following priorities are suggested for issues > - Test suite timeout - it hides real test failures from us and wastes agent > time > - Stable failing test - 50-100% of failures - issue is to be created as > blocked to the next release, test should be muted. > - Flaky tests 1%-50% of failures, which are considered by teamcity as flaky > may be not muted for now because TC interface helps us to identify these > tests. > *Scope* > TBD by JIRA queries > Failures not muted > https://issues.apache.org/jira/issues/?jql=labels%20%3D%20MakeTeamcityGreenAgain%20and%20labels%20!%3D%20Muted_test%20and%20resolution%20is%20EMPTY -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5527) GridDeferredAckMessageSender can cause starvation in stripe pool on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101391#comment-16101391 ] ASF GitHub Bot commented on IGNITE-5527: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2150 > GridDeferredAckMessageSender can cause starvation in stripe pool on unstable > topology. > -- > > Key: IGNITE-5527 > URL: https://issues.apache.org/jira/browse/IGNITE-5527 > Project: Ignite > Issue Type: Bug > Components: clients, general >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Fix For: 2.1 > > > Slow or failed client can cause starvation in stripe-pool. > GridDeferredAckMessageSender.sendDeferredAckMessage() can stucks when add > message to buffer while other thread trying to send this buffer. > Seems, we shouldn't wait for readLock in DeferredAckMessageBuffer.add() > method and return false immediately. > Stacktrace: > Thread [name="sys-stripe-3-#4%null%", id=16, state=WAITING, blockCnt=3087, > waitCnt=204846] > Lock > [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@54ef60c9, > ownerName=sys-#12106%null%, ownerId=12326] > at sun.misc.Unsafe.park(Native Method) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283) > at > java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727) > at > o.a.i.i.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.add(GridDeferredAckMessageSender.java:176) > at > o.a.i.i.processors.cache.GridDeferredAckMessageSender.sendDeferredAckMessage(GridDeferredAckMessageSender.java:100) > at > o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3371) > at > o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3353) > at > o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1800(GridDhtAtomicCache.java:130) > at > o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:379) > at > o.a.i.i.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:374) > at > o.a.i.i.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:827) > at > o.a.i.i.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:369) > at > o.a.i.i.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:293) > at > o.a.i.i.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:95) > at > o.a.i.i.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:238) > at > o.a.i.i.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1217) > at > o.a.i.i.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:845) > at > o.a.i.i.managers.communication.GridIoManager.access$2100(GridIoManager.java:109) > at > o.a.i.i.managers.communication.GridIoManager$6.run(GridIoManager.java:785) > at o.a.i.i.util.StripedExecutor$Stripe.run(StripedExecutor.java:428) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-5839) Unclear exception from BinaryObjectBuilder::build call when builder is reused
[
https://issues.apache.org/jira/browse/IGNITE-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-5839:
Description:
Simple test where {{BinaryObjectBuilder}} builder object is reused fails with
exception {noformat}org.apache.ignite.binary.BinaryObjectException: Wrong value
has been set [typeName=SimpleCls, fieldName=str, fieldType=String,
assignedValueType=Object]{noformat}
{noformat}
IgniteCache cache = /* obtain a reference to
withKeepBinary cache instance */;
BinaryObjectBuilder bldr = grid(0).binary().builder("SimpleCls");
bldr.setField("str", "abc");
c.put(0, bldr.build());
bldr.setField("str", null);
c.put(1, bldr.build());
bldr.setField("str", "def");
c.put(2, bldr.build()); //exception will be thrown by call bldr.build()
{noformat}
It can be fixed by simply recreating BinaryObjectBuilder instead of reusing the
same instance.
However reusing builder object must be either explicitly prohibited or
exception must be fixed.
Right now documentation on builder class says nothing about reusing this object.
was:
Simple test where {{BinaryObjectBuilder}} builder object is reused fails with
exception {noformat}org.apache.ignite.binary.BinaryObjectException: Wrong value
has been set [typeName=SimpleCls, fieldName=str, fieldType=String,
assignedValueType=Object]{noformat}
{noformat}
IgniteCache cache = /* obtain a reference to
withKeepBinary cache instance */;
BinaryObjectBuilder bldr = grid(0).binary().builder("SimpleCls");
bldr.setField("str", "abc");
c.put(0, bldr.build());
bldr.setField("str", null);
c.put(1, bldr.build());
bldr.setField("str", "def");
c.put(2, bldr.build()); //exception will be thrown by call bldr.build()
{noformat}
It can be fixed by simply recreating BinaryObjectBuilder instead of reusing the
same instance. However reusing builder object must be either explicitly
prohibited or exception must be fixed.
Right now documentation on builder class says nothing about reusing this object.
> Unclear exception from BinaryObjectBuilder::build call when builder is reused
> -
>
> Key: IGNITE-5839
> URL: https://issues.apache.org/jira/browse/IGNITE-5839
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
> Fix For: 2.2
>
>
> Simple test where {{BinaryObjectBuilder}} builder object is reused fails with
> exception {noformat}org.apache.ignite.binary.BinaryObjectException: Wrong
> value has been set [typeName=SimpleCls, fieldName=str, fieldType=String,
> assignedValueType=Object]{noformat}
> {noformat}
> IgniteCache cache = /* obtain a reference to
> withKeepBinary cache instance */;
> BinaryObjectBuilder bldr = grid(0).binary().builder("SimpleCls");
> bldr.setField("str", "abc");
> c.put(0, bldr.build());
> bldr.setField("str", null);
> c.put(1, bldr.build());
> bldr.setField("str", "def");
> c.put(2, bldr.build()); //exception will be thrown by call
> bldr.build()
> {noformat}
> It can be fixed by simply recreating BinaryObjectBuilder instead of reusing
> the same instance.
> However reusing builder object must be either explicitly prohibited or
> exception must be fixed.
> Right now documentation on builder class says nothing about reusing this
> object.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5839) Unclear exception from BinaryObjectBuilder::build call when builder is reused
Sergey Chugunov created IGNITE-5839:
---
Summary: Unclear exception from BinaryObjectBuilder::build call
when builder is reused
Key: IGNITE-5839
URL: https://issues.apache.org/jira/browse/IGNITE-5839
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
Fix For: 2.2
Simple test where {{BinaryObjectBuilder}} builder object is reused fails with
exception {noformat}org.apache.ignite.binary.BinaryObjectException: Wrong value
has been set [typeName=SimpleCls, fieldName=str, fieldType=String,
assignedValueType=Object]{noformat}
{noformat}
IgniteCache cache = /* obtain a reference to
withKeepBinary cache instance */;
BinaryObjectBuilder bldr = grid(0).binary().builder("SimpleCls");
bldr.setField("str", "abc");
c.put(0, bldr.build());
bldr.setField("str", null);
c.put(1, bldr.build());
bldr.setField("str", "def");
c.put(2, bldr.build()); //exception will be thrown by call bldr.build()
{noformat}
It can be fixed by simply recreating BinaryObjectBuilder instead of reusing the
same instance. However reusing builder object must be either explicitly
prohibited or exception must be fixed.
Right now documentation on builder class says nothing about reusing this object.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5811) Detect internal Ignite problems (java-level deadlock, hangs, etc) and act according to a policy configured.
[ https://issues.apache.org/jira/browse/IGNITE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101317#comment-16101317 ] Semen Boikov commented on IGNITE-5811: -- I think these issue can cause cluster hang as well: - OutOfMemory error (java and probably our IgniteOutOfMemoryException?) - errors with persistent storage - transactions deadlock Also I don't think we really need 'policy', node should be stopped anyway, what we can provide is user callback, something like 'beforeNodeStop'. Thanks > Detect internal Ignite problems (java-level deadlock, hangs, etc) and act > according to a policy configured. > --- > > Key: IGNITE-5811 > URL: https://issues.apache.org/jira/browse/IGNITE-5811 > Project: Ignite > Issue Type: New Feature >Reporter: Yakov Zhdanov > Labels: usability > > This has something in common with segmentation policy we currently have. User > should get notified on a deadlock problem and node should take an action > (stop by default). > Also Ignite may react on internal errors and hangs in the same way - fire > event and take the appropriate action. > Current list of cases when node should (by default) stop itself: > # Discovery reports segmentation (already implemented) > # Critical discovery thread fails (already implemented) > # NIO communication thread fails (already implemented) > The following needs to be added > # Java-deadlock detected > # Internal threads stuck (no progress on current tasks during defined period) > # ExchangeWorker exits with error > We need to reapproach handling for all situations above to use the same > mechanism and make node take the action according to a configured policy -- This message was sent by Atlassian JIRA (v6.4.14#64029)
