[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046560#comment-15046560 ] Alexey Kuznetsov commented on IGNITE-1371: -- Igor, I do one more review round. All my changes in ignite-1371-review3 branch (I deleted old review branches). Take a look at my changes. And I would like to ask you to rework tests to be subclassed from GridCommonAbstractTest and implement Cassandra aware descendant of GridAbstractCacheStoreSelfTest. This will allow to remove usage of Log4J in tests in favor of IgniteLogger (GridCommonAbstractTest has all needed functionality out-of-the-box). Also I noticed (and removed) checks for (log != null). Logger is injected by grid. In case of tests if you write test without node you may inject with help getTestResources().inject(store); See CacheJdbcPojoStoreTest. And also, please give an estimation when you are planning to finish with embedded Cassandra in tests. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexandre Boudnik >Assignee: Igor Rudyak > Attachments: master_02b59e4_ignite-1371.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2101) NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded.
Vladimir Ozerov created IGNITE-2101: --- Summary: NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded. Key: IGNITE-2101 URL: https://issues.apache.org/jira/browse/IGNITE-2101 Project: Ignite Issue Type: Bug Components: hadoop Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Fix For: 1.6 See http://apache-ignite-users.70518.x6.nabble.com/NPE-issue-with-trying-to-submit-Hadoop-MapReduce-td2146.html When Hadoop module is not loaded, HadoopNoopProcessor is started on the node. And it's method nextJobId() returns null. This null is then propagated to the client and NPE is raised. There is no way for users to underastand what is wrong. Solution should be fairly simple: just throw an exception with sensible message from HadoopNoopProcessor.nextJobId() method. It should be propagated smoothly to the client. Also we need to add tests for this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)
[
https://issues.apache.org/jira/browse/IGNITE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046580#comment-15046580
]
ASF GitHub Bot commented on IGNITE-2050:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/291
> NPE: Failed to reinitialize local partitions (preloading will be stopped)
> -
>
> Key: IGNITE-2050
> URL: https://issues.apache.org/jira/browse/IGNITE-2050
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> I was testing using my own tester and catched NPE:
> {code}
> [10:42:43,151][SEVERE][exchange-worker-#52%tester%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTo
> pologyVersion [topVer=3, minorTopVer=1], nodeId=97e00c67,
> evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Type with name 'FSFMRule'
> already indexed in cache 'bank_FSFMRule'.
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.addTypeByName(GridQueryProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:255)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1021)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1630)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> [10:42:43,155][SEVERE][exchange-worker-#52%tester%][GridCachePartitionExchangeManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=partition-exchanger, gridName=tester, finis
> hed=false, isCancelled=false, hashCode=364597628, interrupted=false,
> runner=exchange-worker-#52%tester%]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1705)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1098)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:861)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2102) .NET: Simplify query examples
Vladimir Ozerov created IGNITE-2102: --- Summary: .NET: Simplify query examples Key: IGNITE-2102 URL: https://issues.apache.org/jira/browse/IGNITE-2102 Project: Ignite Issue Type: Task Components: interop Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Fix For: 1.6 Simply move IGNITE-2097 to .NET once it is ready. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2103) CPP: Simplify query examples.
Vladimir Ozerov created IGNITE-2103: --- Summary: CPP: Simplify query examples. Key: IGNITE-2103 URL: https://issues.apache.org/jira/browse/IGNITE-2103 Project: Ignite Issue Type: Task Components: interop Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Fix For: 1.6 Simply move IGNITE-2097 to .NET once it is ready. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046599#comment-15046599 ] Alexey Kuznetsov commented on IGNITE-1371: -- Igor, please also pull latest ignite-1.5 branch from upsteram to you barnch. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexandre Boudnik >Assignee: Igor Rudyak > Attachments: master_02b59e4_ignite-1371.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > It will provide ability to map particular cache holding POJOs to Cassandra > table. Later it would be generalized to support eventually any any Key-Value > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046615#comment-15046615
]
ASF GitHub Bot commented on IGNITE-1692:
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/300
IGNITE-1692 test suite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ignite-1692-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/300.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 #300
commit 310053f538c15ce7142b97182deaa6770722bfc8
Author: Ilya Lantukh
Date: 2015-12-04T12:23:14Z
Changed test initialization logic to remove race confition that caused
ClusterTopologyServerNotFoundException.
commit 38d4b2679fe1421ce5619f8fbdac3db03533ba4b
Author: Ilya Lantukh
Date: 2015-12-08T09:06:49Z
Test suite for DataStreamProcessorSelfTest.
> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to
> find server node for cache (all affinity nodes have left the grid or cache
> was stopped): null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by:
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to find server node for cache (all affinity nodes have left the grid
> or cache was stopped): null
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2094) building the project with 'install' crashes on Mesos module
[
https://issues.apache.org/jira/browse/IGNITE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046647#comment-15046647
]
Anton Vinogradov commented on IGNITE-2094:
--
Konstantin,
I've cleaned my maven repo,
download sources of 1.5.1-b1 and run
{code}
mvn clean install -DskipTests -Dhadoop.version=2.7.1 -Dspark.version=1.5.1
-Dignite.edition=hadoop
{code}
without redundant package.
and gain BUILD SUCCESS.
Could you please try same steps.
> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the
> build crashed on the Mesos module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2094) building the project with 'install' crashes on Mesos module
[
https://issues.apache.org/jira/browse/IGNITE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046647#comment-15046647
]
Anton Vinogradov edited comment on IGNITE-2094 at 12/8/15 9:45 AM:
---
Konstantin,
I've cleaned my maven repo,
download sources of 1.5.1-b1 and run
{code}
mvn clean install -DskipTests -Dhadoop.version=2.7.1 -Dspark.version=1.5.1
-Dignite.edition=hadoop
{code}
without redundant "package" step.
and gain BUILD SUCCESS.
Could you please try same steps.
was (Author: avinogradov):
Konstantin,
I've cleaned my maven repo,
download sources of 1.5.1-b1 and run
{code}
mvn clean install -DskipTests -Dhadoop.version=2.7.1 -Dspark.version=1.5.1
-Dignite.edition=hadoop
{code}
without redundant package.
and gain BUILD SUCCESS.
Could you please try same steps.
> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the
> build crashed on the Mesos module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046670#comment-15046670
]
Ilya Lantukh commented on IGNITE-1692:
--
Done.
> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to
> find server node for cache (all affinity nodes have left the grid or cache
> was stopped): null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by:
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to find server node for cache (all affinity nodes have left the grid
> or cache was stopped): null
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046675#comment-15046675
]
ASF GitHub Bot commented on IGNITE-1692:
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/300
> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to
> find server node for cache (all affinity nodes have left the grid or cache
> was stopped): null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by:
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to find server node for cache (all affinity nodes have left the grid
> or cache was stopped): null
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2050) NPE: Failed to reinitialize local partitions (preloading will be stopped)
[
https://issues.apache.org/jira/browse/IGNITE-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Shutak closed IGNITE-2050.
> NPE: Failed to reinitialize local partitions (preloading will be stopped)
> -
>
> Key: IGNITE-2050
> URL: https://issues.apache.org/jira/browse/IGNITE-2050
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
> Fix For: 1.5
>
>
> I was testing using my own tester and catched NPE:
> {code}
> [10:42:43,151][SEVERE][exchange-worker-#52%tester%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTo
> pologyVersion [topVer=3, minorTopVer=1], nodeId=97e00c67,
> evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Type with name 'FSFMRule'
> already indexed in cache 'bank_FSFMRule'.
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.addTypeByName(GridQueryProcessor.java:345)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:255)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1021)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1630)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> [10:42:43,155][SEVERE][exchange-worker-#52%tester%][GridCachePartitionExchangeManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=partition-exchanger, gridName=tester, finis
> hed=false, isCancelled=false, hashCode=364597628, interrupted=false,
> runner=exchange-worker-#52%tester%]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:1705)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1098)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:861)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2098) Need to check that Java Proxy is properly (de)serialized with binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk reassigned IGNITE-2098:
Assignee: Alexey Goncharuk
> Need to check that Java Proxy is properly (de)serialized with binary
> marshaller
> ---
>
> Key: IGNITE-2098
> URL: https://issues.apache.org/jira/browse/IGNITE-2098
> Project: Ignite
> Issue Type: Test
> Components: general
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Need to create test similar to {{OptimizedMarshallerTest.testProxy}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2098) Need to check that Java Proxy is properly (de)serialized with binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046697#comment-15046697
]
ASF GitHub Bot commented on IGNITE-2098:
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/301
IGNITE-2098 - Added test for java proxy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2098
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/301.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 #301
commit c5dc062f201e0276ce5c93a0ebdcc3775831f83b
Author: Alexey Goncharuk
Date: 2015-12-08T10:23:57Z
IGNITE-2098 - Added test for java proxy.
> Need to check that Java Proxy is properly (de)serialized with binary
> marshaller
> ---
>
> Key: IGNITE-2098
> URL: https://issues.apache.org/jira/browse/IGNITE-2098
> Project: Ignite
> Issue Type: Test
> Components: general
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Fix For: 1.5
>
>
> Need to create test similar to {{OptimizedMarshallerTest.testProxy}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046698#comment-15046698
]
Semen Boikov commented on IGNITE-1692:
--
Merged fix to 1.5. Ilya, please make sure test is unmuted on TC.
> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to
> find server node for cache (all affinity nodes have left the grid or cache
> was stopped): null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by:
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to find server node for cache (all affinity nodes have left the grid
> or cache was stopped): null
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2104) Marshalling fails with Binary marshaller if class hierarchy contains duplicate field names
Alexey Goncharuk created IGNITE-2104:
Summary: Marshalling fails with Binary marshaller if class
hierarchy contains duplicate field names
Key: IGNITE-2104
URL: https://issues.apache.org/jira/browse/IGNITE-2104
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.5
Reporter: Alexey Goncharuk
Fix For: 1.5
Binary marshaller writes {{fieldId}} which is calculated solely on the field
name. If a class hierarchy contains fields with the same name, marshalling will
fail:
{code}
class ClassA{
private int field;
}
class ClassB extends ClassA {
private int field;
}
{code}
Even though a private field with the same name in parent and child classes is a
error-prone approach, default serialization supports this.
Possible solutions:
* Keep it as it is now and properly document. The issue appeared only in an
artificial test. No other tests on TC revealed duplicate fields.
* Write all serializable classes in old format. While this solution works
perfectly for the marshalling, it will require objects to be deserialized on
server nodes in order for indexing to work, which defeats the purpose of
BinaryMarshaller
* Inspect the class at runtime and use new format if no duplicate fields are
detected, and print a warning message and switch to the old format otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2105) DirectMessageWriter cannot write nested collections.
Vladimir Ozerov created IGNITE-2105: --- Summary: DirectMessageWriter cannot write nested collections. Key: IGNITE-2105 URL: https://issues.apache.org/jira/browse/IGNITE-2105 Project: Ignite Issue Type: Bug Components: 1.4 Affects Versions: ignite-1.4 Reporter: Vladimir Ozerov Priority: Critical Fix For: 1.5 Steps to reproduce: 1) Run GridMessageCollectionTest in ignite-1.5 branch 2) Observe class-cast exception. The problem is caused by DirectByteBufferStreamImplV2 which is re-used across all nested objects. This class is stateful. When nested collection is written, instead of writing collection element it writes element of another collection which is upper in call stack. Looks pretty critical for me. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2097) Splitting Query example
[
https://issues.apache.org/jira/browse/IGNITE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-2097:
--
Description:
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called org.apache.ignite.examples.query and split
org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
like:
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
upd YZ: I think this should be done in separate package
{{org.apache.ignite.examples.datagrid.query}}
was:
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called org.apache.ignite.examples.query and split
org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
like
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
> Splitting Query example
> ---
>
> Key: IGNITE-2097
> URL: https://issues.apache.org/jira/browse/IGNITE-2097
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4, 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> CacheQueryExample is overloaded by query features. What's about to introduce
> a new package e.g. called org.apache.ignite.examples.query and split
> org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
> like:
> QueryScanExample
> QueryJoinExample
> QueryTextExample
> QueryAggregationExample
> QueryFieldsExample
> QueryFieldsJoinExample
> And add new ones:
> QueryCrossCacheExample
> QueryExplainExample
> upd YZ: I think this should be done in separate package
> {{org.apache.ignite.examples.datagrid.query}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2094) building the project with 'install' crashes on Mesos module
[
https://issues.apache.org/jira/browse/IGNITE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046787#comment-15046787
]
Sergey Kozlov commented on IGNITE-2094:
---
I just repeated original steps on empty local .m2 repository and build
successfully finished.
Could you clean up your .m2 and try again?
> building the project with 'install' crashes on Mesos module
> ---
>
> Key: IGNITE-2094
> URL: https://issues.apache.org/jira/browse/IGNITE-2094
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Konstantin Boudnik
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> Attempting to do {{mvn install...}} on the latest {{-b1}} release and the
> build crashed on the Mesos module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2106) BinaryMarshaller: near cache mustn't keep a copy on put() operation
Anton Vinogradov created IGNITE-2106: Summary: BinaryMarshaller: near cache mustn't keep a copy on put() operation Key: IGNITE-2106 URL: https://issues.apache.org/jira/browse/IGNITE-2106 Project: Ignite Issue Type: Bug Reporter: Anton Vinogradov Assignee: Anton Vinogradov Priority: Blocker Binary marshaller is an opensouced Gridgain Prortable marshaller, So bug http://atlassian.gridgain.com/jira/browse/GG-10791 moved to Ignite jira. There are several deployment related tests that fail when PortableMarshaller is used. GridPortableCacheDeploymentSelftTest.testDeployment3()/testDeployemnt4(); GridPortableCacheDeploymentOffHeapSelfTest.testDeployment3()/testDeployemnt4(); The reason of the failure is that a near cache stores a copy of a cache entry when the cache.put() is being executed. No cache.get() was explicitly called during the test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1957) .NET: Collections, dictionaries, object arrays and tuples must use handles.
[ https://issues.apache.org/jira/browse/IGNITE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046822#comment-15046822 ] ASF GitHub Bot commented on IGNITE-1957: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/302 IGNITE-1957 .NET: Collections, dictionaries, object arrays and tuples must use handles. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1957 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/302.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 #302 commit 238409f8af638363e5e274ac9decb054193a6d2c Author: Pavel Tupitsyn Date: 2015-12-04T14:24:22Z Test added commit 96e81ca49b8da090a1582bf42814605cc8386c70 Author: Pavel Tupitsyn Date: 2015-12-04T15:22:31Z All done! commit 98dc3b587dc07a1d9c6c057ecc00c0673ee854ee Author: Pavel Tupitsyn Date: 2015-12-04T15:27:19Z Cleanup commit 51f41a971a03deecba9102f5c4753aae5deb6e61 Author: Pavel Tupitsyn Date: 2015-12-07T15:30:35Z wip tests commit ee96607fbb0bb17e2d6910394a916b73a3be1597 Author: Pavel Tupitsyn Date: 2015-12-07T15:50:38Z wip commit 87266831fd20de3b8dbeffdad81475cd6289066c Author: Pavel Tupitsyn Date: 2015-12-07T15:53:00Z wip commit b19c4f8613e92cd02bf1b7ea592eab2932f55fa4 Author: Pavel Tupitsyn Date: 2015-12-07T15:53:39Z test done commit 5d87979f4f29dbb04dd45a07358099a905247917 Author: Pavel Tupitsyn Date: 2015-12-07T16:00:46Z wip commit fe948a6373bbc125bf335a52ef415a40df70409f Author: Pavel Tupitsyn Date: 2015-12-07T16:17:44Z wip SystemHandlers refactoring commit f9cac8e01c42d7cd5a376345aa607c455d2312f3 Author: Pavel Tupitsyn Date: 2015-12-07T16:24:49Z wip commit b10e03e58200c53a61d6d62403819edd819019d9 Author: Pavel Tupitsyn Date: 2015-12-07T16:25:38Z wip commit c518536974b8b3bf6106aef68c4fdd04b991a9b3 Author: Pavel Tupitsyn Date: 2015-12-07T16:27:36Z wip commit 96bb25b7a9b8a243d553e60a86aebb5aac5cd4b4 Author: Pavel Tupitsyn Date: 2015-12-07T16:40:08Z wip commit d9b90390a877c9b9f14d5c4758c5235d4cfb6ac2 Author: Pavel Tupitsyn Date: 2015-12-07T16:41:52Z wip commit 9ceb4a6430da7f2c032e7891f2517c5ea6fe2f90 Author: Pavel Tupitsyn Date: 2015-12-08T08:27:36Z wip commit 97364825dc62aa5fe5f4289cfb0436d9d77cddaa Author: Pavel Tupitsyn Date: 2015-12-08T09:23:57Z wip reader commit 6f142391d5c5f59622c1f758d4df953ef88999ac Author: Pavel Tupitsyn Date: 2015-12-08T09:32:04Z Fix handle reading commit faad03d2c174b6a7be2e75b62963f2262d1a88de Author: Pavel Tupitsyn Date: 2015-12-08T09:32:46Z wip commit 762de2b016c56bd12c962fe3df6b4b6ea919ddcc Author: Pavel Tupitsyn Date: 2015-12-08T09:39:38Z wip commit af0f82fa61067e7efeeb9ccd643bcdae496a7992 Author: Pavel Tupitsyn Date: 2015-12-08T09:40:35Z wip commit b046a8eee59a78cf54ac6d259043d4cb09d6aa62 Author: Pavel Tupitsyn Date: 2015-12-08T09:46:40Z wip commit 96e5a9533176133878748d5f6a89b9f2d0a2ba8f Author: Pavel Tupitsyn Date: 2015-12-08T10:01:10Z wip tests commit 00f94be4de3bf02513c78622325fadc1fc9127cc Author: Pavel Tupitsyn Date: 2015-12-08T10:04:43Z wip commit 4f503c37f5bf9b0add107629499524910eba9f6d Author: Pavel Tupitsyn Date: 2015-12-08T10:08:36Z wip commit 09d9bc8af4085c4605f4a7efdbd92d7084fe64e4 Author: Pavel Tupitsyn Date: 2015-12-08T10:11:45Z wip commit bc80caae44268757cffd9efde6d6ccbaedf19b6a Author: Pavel Tupitsyn Date: 2015-12-08T10:12:58Z wip commit 493394e1d96566a5480fee989218f95e10ed019b Author: Pavel Tupitsyn Date: 2015-12-08T10:16:32Z Fix WriteDictionary commit 9dcc63cd5e3ef83cbea272970b1bd8ae59d4efe3 Author: Pavel Tupitsyn Date: 2015-12-08T10:24:26Z wip commit e6d6ddefa05435b171232879266b9edc420846a5 Author: Pavel Tupitsyn Date: 2015-12-08T10:26:54Z wip DictionaryEntry commit 19499ad01754db2551e4d0d56510ad22b280455b Author: Pavel Tupitsyn Date: 2015-12-08T10:50:57Z wip > .NET: Collections, dictionaries, object arrays and tuples must use handles. > --- > > Key: IGNITE-1957 > URL: https://issues.apache.org/jira/browse/IGNITE-1957 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: 1.6 > > > We must track handles for the following cases: > - Collections > - Dictionaries > - Entries > - Object arrays > Reason: they may have cyclic deps on other
[jira] [Updated] (IGNITE-2026) .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs
[ https://issues.apache.org/jira/browse/IGNITE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2026: Component/s: interop > .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs > - > > Key: IGNITE-2026 > URL: https://issues.apache.org/jira/browse/IGNITE-2026 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > > Put and get a struct to cache - observe exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2026) .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs
[ https://issues.apache.org/jira/browse/IGNITE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2026: Fix Version/s: (was: 1.6) 1.5 > .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs > - > > Key: IGNITE-2026 > URL: https://issues.apache.org/jira/browse/IGNITE-2026 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Put and get a struct to cache - observe exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2026) .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs
[ https://issues.apache.org/jira/browse/IGNITE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-2026. --- > .Net: BinaryReflectiveSerializer fails with StackOverflowException on structs > - > > Key: IGNITE-2026 > URL: https://issues.apache.org/jira/browse/IGNITE-2026 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Put and get a struct to cache - observe exception -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2107) Splitting TX example and adding new
Yakov Zhdanov created IGNITE-2107:
-
Summary: Splitting TX example and adding new
Key: IGNITE-2107
URL: https://issues.apache.org/jira/browse/IGNITE-2107
Project: Ignite
Issue Type: Task
Components: general
Affects Versions: ignite-1.4, 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
Fix For: 1.6
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called org.apache.ignite.examples.query and split
org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
like:
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
upd YZ: I think this should be done in separate package
{{org.apache.ignite.examples.datagrid.query}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2107) Splitting TX example and adding new
[
https://issues.apache.org/jira/browse/IGNITE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-2107:
--
Description:
We need to introduce {{tx}} package and add examples demonstrating different
types of txs:
# pessimistic repeatable read
# optimistic repeatable read
# optimistic serializable - we need to accent that this is deadlock free mode.
was:
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called org.apache.ignite.examples.query and split
org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
like:
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
upd YZ: I think this should be done in separate package
{{org.apache.ignite.examples.datagrid.query}}
> Splitting TX example and adding new
> ---
>
> Key: IGNITE-2107
> URL: https://issues.apache.org/jira/browse/IGNITE-2107
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4, 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> We need to introduce {{tx}} package and add examples demonstrating different
> types of txs:
> # pessimistic repeatable read
> # optimistic repeatable read
> # optimistic serializable - we need to accent that this is deadlock free mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2107) Splitting TX example and adding new
[
https://issues.apache.org/jira/browse/IGNITE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-2107:
--
Reporter: Yakov Zhdanov (was: Sergey Kozlov)
> Splitting TX example and adding new
> ---
>
> Key: IGNITE-2107
> URL: https://issues.apache.org/jira/browse/IGNITE-2107
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4, 1.5
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> We need to introduce {{tx}} package and add examples demonstrating different
> types of txs:
> # pessimistic repeatable read
> # optimistic repeatable read
> # optimistic serializable - we need to accent that this is deadlock free mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node
Denis Magda created IGNITE-2108:
---
Summary: CacheJdbcPojoStoreFactory is not fully initialized when
deserialized on a remote node
Key: IGNITE-2108
URL: https://issues.apache.org/jira/browse/IGNITE-2108
Project: Ignite
Issue Type: Bug
Affects Versions: 1.5
Reporter: Denis Magda
Priority: Blocker
Fix For: 1.5
When a cache is started dynamically and has an implementation of
{{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup
procedure will fail on a remote node with the following exception:
{noformat}
[16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
class org.apache.ignite.IgniteCheckedException: Failed to start component:
class org.apache.ignite.IgniteException: Failed to initialize cache store (data
source is not provided).
at
org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to initialize cache
store (data source is not provided).
at
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
at
org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
... 8 more
{noformat}
The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked
significantly and presently it has field {{private transient DataSource
dataSrc}} that must be initiated somehow after deserialization.
The issue is easily to reproduce with schema-import example:
1) complete all the steps described in the demo tutorial
https://apacheignite.readme.io/docs/automatic-persistence#example
2) Start a remote node using {{DemoNode}}
3) Start {{Demo}}
4) The node started with {{DemoNode}} won't be able to start a cache because of
the issue with the storage described above
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node
[
https://issues.apache.org/jira/browse/IGNITE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046855#comment-15046855
]
Denis Magda commented on IGNITE-2108:
-
Used 1.5 beta
> CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a
> remote node
> -
>
> Key: IGNITE-2108
> URL: https://issues.apache.org/jira/browse/IGNITE-2108
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
>
> When a cache is started dynamically and has an implementation of
> {{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup
> procedure will fail on a remote node with the following exception:
> {noformat}
> [16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to start component:
> class org.apache.ignite.IgniteException: Failed to initialize cache store
> (data source is not provided).
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to initialize
> cache store (data source is not provided).
> at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
> ... 8 more
> {noformat}
> The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked
> significantly and presently it has field {{private transient DataSource
> dataSrc}} that must be initiated somehow after deserialization.
> The issue is easily to reproduce with schema-import example:
> 1) complete all the steps described in the demo tutorial
> https://apacheignite.readme.io/docs/automatic-persistence#example
> 2) Start a remote node using {{DemoNode}}
> 3) Start {{Demo}}
> 4) The node started with {{DemoNode}} won't be able to start a cache because
> of the issue with the storage described above
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1694) .Net: More efficient way to call native methods.
[ https://issues.apache.org/jira/browse/IGNITE-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1694. --- > .Net: More efficient way to call native methods. > > > Key: IGNITE-1694 > URL: https://issues.apache.org/jira/browse/IGNITE-1694 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Currently we invoke native platform using > "Marshal.GetDelegateForFunctionPointer". > This is the least efficient way to call external code. What can be done to > improve it: > 1) Add [SuppressUnmanagedCodeSecurity] attribute. > 2) Use P/Invoke instead. We do not use it now because we unpack native > library in runtime into some temp folder, while PInvoke searches for > libraries in predefined file system places. Need to evaluate whether we can > switch back to P/Invoke somehow. > See > http://ybeernet.blogspot.ru/2011/03/techniques-of-calling-unmanaged-code.html > for more info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1694) .Net: More efficient way to call native methods.
[ https://issues.apache.org/jira/browse/IGNITE-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1694: Fix Version/s: (was: 1.6) 1.5 > .Net: More efficient way to call native methods. > > > Key: IGNITE-1694 > URL: https://issues.apache.org/jira/browse/IGNITE-1694 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Currently we invoke native platform using > "Marshal.GetDelegateForFunctionPointer". > This is the least efficient way to call external code. What can be done to > improve it: > 1) Add [SuppressUnmanagedCodeSecurity] attribute. > 2) Use P/Invoke instead. We do not use it now because we unpack native > library in runtime into some temp folder, while PInvoke searches for > libraries in predefined file system places. Need to evaluate whether we can > switch back to P/Invoke somehow. > See > http://ybeernet.blogspot.ru/2011/03/techniques-of-calling-unmanaged-code.html > for more info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace
[ https://issues.apache.org/jira/browse/IGNITE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1433: Fix Version/s: 1.5 > .Net: Add IgniteException.JavaStackTrace > > > Key: IGNITE-1433 > URL: https://issues.apache.org/jira/browse/IGNITE-1433 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.5 > > > Propagate java stack trace as a string in ExceptionUtils.GetException and > write it to a new field in IgniteException class. > This will simplify debugging for us both locally and when getting error > reports from clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2109) PlatformUtils.errorData() contains invalid call to PlatformInputStream.remaining()
Vladimir Ozerov created IGNITE-2109:
---
Summary: PlatformUtils.errorData() contains invalid call to
PlatformInputStream.remaining()
Key: IGNITE-2109
URL: https://issues.apache.org/jira/browse/IGNITE-2109
Project: Ignite
Issue Type: Bug
Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Fix For: 1.5
See the following line:
{code}int len = in.remaining();{code}
WTF is that? Probably "length()" method should be called instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-1979:
-
Fix Version/s: (was: 1.6)
1.5
> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 1.5
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive
> and can contain all kind of symbols that are not supported by underlying H2
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}}
> that will let the end user use a cache name in case insensitive manner
> without quoted identifiers in SQL queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1979) Support case insensitive nonquoted cache names in SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-1979:
-
Assignee: Vladimir Ershov
> Support case insensitive nonquoted cache names in SQL queries
> -
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
> Fix For: 1.5
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive
> and can contain all kind of symbols that are not supported by underlying H2
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}}
> that will let the end user use a cache name in case insensitive manner
> without quoted identifiers in SQL queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis
[ https://issues.apache.org/jira/browse/IGNITE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov updated IGNITE-2030: - Assignee: Vladimir Ershov > ignite.bat file does not work when JAVA_HOME contains parethensis > - > > Key: IGNITE-2030 > URL: https://issues.apache.org/jira/browse/IGNITE-2030 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Denis Magda >Assignee: Vladimir Ershov > Fix For: 1.5 > > > When starting ignite.bat with a folder which contains parenthesis, the > launcher will fail: > For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\ > Program Files (x86) > Error (happens @ parseargs.bat script): > \Java\jre1.8.0_25\bin\java.exe" -cp > C:\ignite\gridgain-enterprise-fabric-7.5.0\g > ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5. > 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent > erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig > nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice > nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was > unexpect > ed at this time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution
Vladimir Ershov created IGNITE-2110:
---
Summary: Replace workarond for local node flag in TcpDiscoveryNode
with better solution
Key: IGNITE-2110
URL: https://issues.apache.org/jira/browse/IGNITE-2110
Project: Ignite
Issue Type: Task
Components: cache
Affects Versions: ignite-1.4
Reporter: Vladimir Ershov
Priority: Minor
We should get read of this workaround in
GridDhtAffinityAssignmentResponse#finishUnmarshal
{code:java}
// TODO IGNITE-10: setting 'local' for nodes not needed when
IGNITE-10 is implemented.
int assignments = affAssignment.size();
for (int n = 0; n < assignments; n++) {
List nodes = affAssignment.get(n);
int size = nodes.size();
for (int i = 0; i < size; i++) {
ClusterNode node = nodes.get(i);
if (node instanceof TcpDiscoveryNode)
((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
}
}
{code}
by designing new solution for TcpDiscoveryNode.local transient flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node
[
https://issues.apache.org/jira/browse/IGNITE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046898#comment-15046898
]
Denis Magda commented on IGNITE-2108:
-
The issue disappears if to replace H2DemoStoreFactory implementation with the
following
{noformat}
private static class H2DemoStoreFactory extends
CacheJdbcPojoStoreFactory {
@Override public CacheJdbcPojoStore create() {
setDialect(new H2Dialect());
setDataSource(JdbcConnectionPool.create("jdbc:h2:tcp://localhost/~/schema-import/demo",
"sa", ""));
return super.create();
}
}
{noformat}
It means that a default constructor, that is used in the current
implementation, is not got called during deserialization. The issue is
reproduced on both optimized and binary marshallers.
> CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a
> remote node
> -
>
> Key: IGNITE-2108
> URL: https://issues.apache.org/jira/browse/IGNITE-2108
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
>
> When a cache is started dynamically and has an implementation of
> {{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup
> procedure will fail on a remote node with the following exception:
> {noformat}
> [16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to start component:
> class org.apache.ignite.IgniteException: Failed to initialize cache store
> (data source is not provided).
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to initialize
> cache store (data source is not provided).
> at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
> ... 8 more
> {noformat}
> The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked
> significantly and presently it has field {{private transient DataSource
> dataSrc}} that must be initiated somehow after deserialization.
> The issue is easily to reproduce with schema-import example:
> 1) complete all the steps described in the demo tutorial
> https://apacheignite.readme.io/docs/automatic-persistence#example
> 2) Start a remote node using {{DemoNode}}
> 3) Start {{Demo}}
> 4) The node started with {{DemoNode}} won't be able to start a cache because
> of the issue with the storage described above
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup
[ https://issues.apache.org/jira/browse/IGNITE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046946#comment-15046946 ] Artem Shutak edited comment on IGNITE-1864 at 12/8/15 3:09 PM: --- Reviewed by Sem. Fixed review comments: - Removed redundant ReflectionFactory - added test on JndiTmFactory (fixed minor bug in implementation). Waiting for JTA build on TC: http://ci.ignite.apache.org/viewQueued.html?itemId=134654&tab=queuedBuildOverviewTab was (Author: ashutak): Reviewed by Sem. Fixed review comments: - Removed redundant ReflectionFactory - added test on JndiTmFactory (fixed minor bug in implementation). > Cannot configure jndiNames for CacheJndiTmLookup > - > > Key: IGNITE-1864 > URL: https://issues.apache.org/jira/browse/IGNITE-1864 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Yakov Zhdanov >Assignee: Artem Shutak >Priority: Critical > Fix For: 1.5 > > > Since user have an ability to configure only lookup class name via > org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName, > he lacks ability to properly configure all of its properties. > This seems to be a general problem for this approach -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup
[ https://issues.apache.org/jira/browse/IGNITE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046946#comment-15046946 ] Artem Shutak commented on IGNITE-1864: -- Reviewed by Sem. Fixed review comments: - Removed redundant ReflectionFactory - added test on JndiTmFactory (fixed minor bug in implementation). > Cannot configure jndiNames for CacheJndiTmLookup > - > > Key: IGNITE-1864 > URL: https://issues.apache.org/jira/browse/IGNITE-1864 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Yakov Zhdanov >Assignee: Artem Shutak >Priority: Critical > Fix For: 1.5 > > > Since user have an ability to configure only lookup class name via > org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName, > he lacks ability to properly configure all of its properties. > This seems to be a general problem for this approach -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node
[
https://issues.apache.org/jira/browse/IGNITE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046898#comment-15046898
]
Denis Magda edited comment on IGNITE-2108 at 12/8/15 3:13 PM:
--
The issue disappears if to replace H2DemoStoreFactory implementation with the
following
{noformat}
private static class H2DemoStoreFactory extends
CacheJdbcPojoStoreFactory {
@Override public CacheJdbcPojoStore create() {
setDialect(new H2Dialect());
setDataSource(JdbcConnectionPool.create("jdbc:h2:tcp://localhost/~/schema-import/demo",
"sa", ""));
return super.create();
}
}
{noformat}
It means that a default constructor, that is used in the current
implementation, is not got called during deserialization. The issue is
reproduced on both optimized and binary marshallers.
However it gets called in the previous versions.
was (Author: dmagda):
The issue disappears if to replace H2DemoStoreFactory implementation with the
following
{noformat}
private static class H2DemoStoreFactory extends
CacheJdbcPojoStoreFactory {
@Override public CacheJdbcPojoStore create() {
setDialect(new H2Dialect());
setDataSource(JdbcConnectionPool.create("jdbc:h2:tcp://localhost/~/schema-import/demo",
"sa", ""));
return super.create();
}
}
{noformat}
It means that a default constructor, that is used in the current
implementation, is not got called during deserialization. The issue is
reproduced on both optimized and binary marshallers.
> CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a
> remote node
> -
>
> Key: IGNITE-2108
> URL: https://issues.apache.org/jira/browse/IGNITE-2108
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 1.5
>
>
> When a cache is started dynamically and has an implementation of
> {{CacheJdbcPojoStoreFactory}} in its configuration then the cache startup
> procedure will fail on a remote node with the following exception:
> {noformat}
> [16:14:10,014][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2,
> minorTopVer=1], nodeId=a7a1f89a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to start component:
> class org.apache.ignite.IgniteException: Failed to initialize cache store
> (data source is not provided).
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1251)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to initialize
> cache store (data source is not provided).
> at
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
> at
> org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
> ... 8 more
> {noformat}
> The reason is that in version 1.5 {{CacheJdbcPojoStoreFactory}} was reworked
> significantly and presently it has field {{private transient DataSource
> dataSrc}} that must be initiated somehow after deserialization.
> The issue is easily to reproduce with schema-import example:
> 1) complete all the steps described in the demo tutorial
> https://apacheignite.readme.io/docs/automatic-persistence#example
> 2) Start a remote node using {{DemoNode}}
> 3) Start {{Demo}}
> 4) The node started with {{DemoNode}} won't be able to start a cache because
> of the issue with the storage described above
--
This message was sent by
[jira] [Commented] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup
[ https://issues.apache.org/jira/browse/IGNITE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046962#comment-15046962 ] Artem Shutak commented on IGNITE-1864: -- TC build passed. Ready for final review. > Cannot configure jndiNames for CacheJndiTmLookup > - > > Key: IGNITE-1864 > URL: https://issues.apache.org/jira/browse/IGNITE-1864 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Yakov Zhdanov >Assignee: Artem Shutak >Priority: Critical > Fix For: 1.5 > > > Since user have an ability to configure only lookup class name via > org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName, > he lacks ability to properly configure all of its properties. > This seems to be a general problem for this approach -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2111) .Net: Create a build script
Pavel Tupitsyn created IGNITE-2111: -- Summary: .Net: Create a build script Key: IGNITE-2111 URL: https://issues.apache.org/jira/browse/IGNITE-2111 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.5 * Create a build script (batch file) to easily produce x86/x64 binaries * Add a Maven step to generate Doxygen documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2112) Provide a way to serialize/deserialize an IgniteConfiguration object using JSON
Juan Velez created IGNITE-2112: -- Summary: Provide a way to serialize/deserialize an IgniteConfiguration object using JSON Key: IGNITE-2112 URL: https://issues.apache.org/jira/browse/IGNITE-2112 Project: Ignite Issue Type: Improvement Components: general Affects Versions: ignite-1.4 Reporter: Juan Velez Priority: Minor Currently as of Release 1.4, Ignite does not provide a way to serialize/deserialize an IgniteConfiguration object using JSON. Attempts to create a working serializer/deserializer are met with very difficult setup and configuration because the IgniteConfiguration (and subcomponents) rely on Factories, SPIs, etc for properties. as well as not being completely compliant with the JavaBeans standard. It would be great if the serialization/deserialization using JSON could be provided as either a new method in an existing/new Util class or part of the IgniteConfiguration class itself. I understand that in the case of deserialization most likely there would be constraints on how to correctly specify the JSON string but that would be left for implementors of the feature to correctly decide/design/document. See user@ thread http://apache-ignite-users.70518.x6.nabble.com/How-to-serialize-deserialize-IgniteConfiguration-to-from-JSON-td2164.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1433) .Net: Add IgniteException.JavaStackTrace
[ https://issues.apache.org/jira/browse/IGNITE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046970#comment-15046970 ] Pavel Tupitsyn commented on IGNITE-1433: 1) Agreed, but it is as unsafe as it was before 2) Agreed 3) In such cases I add Java stack trace to the message. However, simply logging in Java is a bad usability option: * Looking in Java log is inconvenient, in contrary to seeing all the details in debugger immediately * Exceptions in Java log have to be matched to particular exceptions in .NET * User may be sending exceptions over network or storing them, Java log won't be included * Users are not aware of a Java log, we'll often have to ask them explicitly to include it during investigation There is a range of issues when we absolutely need Java stack trace on .NET side, such as startup failures, topology join failures and manager startup failures. Let's address these initialization issues first. > .Net: Add IgniteException.JavaStackTrace > > > Key: IGNITE-1433 > URL: https://issues.apache.org/jira/browse/IGNITE-1433 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Fix For: 1.6 > > > Propagate java stack trace as a string in ExceptionUtils.GetException and > write it to a new field in IgniteException class. > This will simplify debugging for us both locally and when getting error > reports from clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2111) .Net: Create a build script
[ https://issues.apache.org/jira/browse/IGNITE-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2111: --- Description: * Create a build script (batch file) to easily produce x86/x64 debug/release binaries * Change examples reference paths to use produced binaries (to simplify example running) * Add a Maven step to generate Doxygen documentation was: * Create a build script (batch file) to easily produce x86/x64 binaries * Add a Maven step to generate Doxygen documentation > .Net: Create a build script > --- > > Key: IGNITE-2111 > URL: https://issues.apache.org/jira/browse/IGNITE-2111 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: 1.5 > > > * Create a build script (batch file) to easily produce x86/x64 debug/release > binaries > * Change examples reference paths to use produced binaries (to simplify > example running) > * Add a Maven step to generate Doxygen documentation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2030) ignite.bat file does not work when JAVA_HOME contains parethensis
[ https://issues.apache.org/jira/browse/IGNITE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ershov reassigned IGNITE-2030: --- Assignee: Semen Boikov (was: Vladimir Ershov) > ignite.bat file does not work when JAVA_HOME contains parethensis > - > > Key: IGNITE-2030 > URL: https://issues.apache.org/jira/browse/IGNITE-2030 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Denis Magda >Assignee: Semen Boikov > Fix For: 1.5 > > > When starting ignite.bat with a folder which contains parenthesis, the > launcher will fail: > For example, JAVA_HOME=C:\Program Files (x86)\jdk1.7.0_76\ > Program Files (x86) > Error (happens @ parseargs.bat script): > \Java\jre1.8.0_25\bin\java.exe" -cp > C:\ignite\gridgain-enterprise-fabric-7.5.0\g > ridgain-enterprise-fabric-7.5.0\libs\*;C:\ignite\gridgain-enterprise-fabric-7.5. > 0\gridgain-enterprise-fabric-7.5.0\libs\ignite-indexing\*;C:\ignite\gridgain-ent > erprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\ignite-spring\*;C:\ig > nite\gridgain-enterprise-fabric-7.5.0\gridgain-enterprise-fabric-7.5.0\libs\lice > nses\* org.apache.ignite.startup.cmdline.CommandLineTransformer "`) was > unexpect > ed at this time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
[
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047170#comment-15047170
]
Andrey Gura commented on IGNITE-2080:
-
Fixed: https://github.com/apache/ignite/pull/305
Waiting for TC and benchmarks results.
> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties,
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode
> solaris-sparc )
> # Problematic frame:
> # V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700], sp=0xfff0f6ffd1f0, free
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()
[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
[
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047170#comment-15047170
]
Andrey Gura edited comment on IGNITE-2080 at 12/8/15 6:24 PM:
--
Fixed: https://github.com/apache/ignite/pull/305
Waiting for TC and benchmarks results.
This PR also should fix https://issues.apache.org/jira/browse/IGNITE-1493 issue.
was (Author: agura):
Fixed: https://github.com/apache/ignite/pull/305
Waiting for TC and benchmarks results.
> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties,
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode
> solaris-sparc )
> # Problematic frame:
> # V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700], sp=0xfff0f6ffd1f0, free
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVe
[jira] [Created] (IGNITE-2113) Yardstick scripts don't work under Solaris (SunOS)
Andrey Gura created IGNITE-2113:
---
Summary: Yardstick scripts don't work under Solaris (SunOS)
Key: IGNITE-2113
URL: https://issues.apache.org/jira/browse/IGNITE-2113
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
Yardstick scripts don't work under Solaris (SunOS). The problem in shell
commands like {{pgrep}} that work a little different than under Linux.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1493) Fatal exception is thrown during queue instantiation when using Ignite with an HP-UX machine.
[
https://issues.apache.org/jira/browse/IGNITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047226#comment-15047226
]
Andrey Gura commented on IGNITE-1493:
-
Vladimir, Nicholas,
I believe that fix of https://issues.apache.org/jira/browse/IGNITE-2080 should
work for HP-UX also.
> Fatal exception is thrown during queue instantiation when using Ignite with
> an HP-UX machine.
> -
>
> Key: IGNITE-1493
> URL: https://issues.apache.org/jira/browse/IGNITE-1493
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
> Environment: * HP-UX B.11.31 IA64W machine
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
>Reporter: Nicholas Dzwill
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.5
>
> Attachments: ErrorLog.txt, server.log
>
>
> A fatal exception is thrown during queue instantiation when using an HP-UX
> B.11.31 IA64W machine.
> The environment is as follows:
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
> The error logged is as follows:
> * Current thread (01ab2800): JavaThread "main" [_thread_in_vm, id=23,
> lwp_id=3525570, stack(4e501000,4e601000)]
> * siginfo:si_signo=SIGBUS: si_errno=0, si_code=1 (BUS_ADRALN),
> si_addr=5e038d15
>
> The exception above means there is an "invalid address alignment" (writing to
> an odd memory location) when calling the following method:
> * Class: org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream
> * Method:
> {code:borderStyle=solid}
>/** {@inheritDoc} */
> @Override public void writeInt(int v) throws IOException {
> requestFreeSize(4);
> UNSAFE.putInt(bytes, byteArrOff + off, v); // byteArrOff + off =
> 17 when this exception is thrown
> onWrite(4);
> }
> {code}
>
> Basic setup - Ignite is configured with spring and pushed to the constructor
> of a class. That class uses this instance of Ignite to instantiate an
> IgniteQueue as follows:
> {code:borderStyle=solid}
> CollectionConfiguration configuration = new CollectionConfiguration();
> configuration.setCollocated(true);
> IgniteQueue queue = ignite.queue("queue", 0, configuration);
> {code}
>
> Partial stack:
> * Instantiating the queue calls:
> **
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.compatibleConfiguration()
>
> * Which in turn calls:
> ** org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke()
> * Leading to the fatal error when calling:
> **
> org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeInt()
> The error log has been attached with the stack trace of the error. The
> server log is also attached. We are running Ignite in a variety of
> environments and this issue only appears to exist in this specific
> environment and is consistently hit in the same place with no apparent
> work-around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2113) Yardstick scripts don't work under Solaris (SunOS)
[
https://issues.apache.org/jira/browse/IGNITE-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-2113:
Description:
Yardstick scripts don't work under Solaris (SunOS). The problem in shell
commands like {{pgrep}} that work a little different than under Linux.
The output:
{noformat}
$ ./bin/benchmark-run-all.sh config/benchmark.properties
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=0
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=1
tail: cannot open input
<10:46:32> Starting driver config '...' on localhost with id=0
ERROR: Driver process has not started on localhost during 10.0 seconds.
Type "--help" for usage.
<10:46:42> Driver is started on localhost with id=0
<10:46:42> Driver is stopped on localhost
<10:46:42> Server is stopped on localhost
<10:46:43> Server is stopped on localhost
{noformat}
But driver and server nodes keep working.
was:Yardstick scripts don't work under Solaris (SunOS). The problem in shell
commands like {{pgrep}} that work a little different than under Linux.
> Yardstick scripts don't work under Solaris (SunOS)
> --
>
> Key: IGNITE-2113
> URL: https://issues.apache.org/jira/browse/IGNITE-2113
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>
> Yardstick scripts don't work under Solaris (SunOS). The problem in shell
> commands like {{pgrep}} that work a little different than under Linux.
> The output:
> {noformat}
> $ ./bin/benchmark-run-all.sh config/benchmark.properties
> tail: cannot open input
> <10:46:28> Starting server config '...' on localhost with id=0
> tail: cannot open input
> <10:46:28> Starting server config '...' on localhost with id=1
> tail: cannot open input
> <10:46:32> Starting driver config '...' on localhost with id=0
> ERROR: Driver process has not started on localhost during 10.0 seconds.
> Type "--help" for usage.
> <10:46:42> Driver is started on localhost with id=0
> <10:46:42> Driver is stopped on localhost
> <10:46:42> Server is stopped on localhost
> <10:46:43> Server is stopped on localhost
> {noformat}
> But driver and server nodes keep working.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2113) Yardstick scripts don't work under Solaris (SunOS)
[
https://issues.apache.org/jira/browse/IGNITE-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-2113:
Description:
Yardstick scripts don't work under Solaris (SunOS). The problem in shell
commands like {{pgrep}} and {{pkill}} that work a little different than under
Linux.
The output:
{noformat}
$ ./bin/benchmark-run-all.sh config/benchmark.properties
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=0
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=1
tail: cannot open input
<10:46:32> Starting driver config '...' on localhost with id=0
ERROR: Driver process has not started on localhost during 10.0 seconds.
Type "--help" for usage.
<10:46:42> Driver is started on localhost with id=0
<10:46:42> Driver is stopped on localhost
<10:46:42> Server is stopped on localhost
<10:46:43> Server is stopped on localhost
{noformat}
But driver and server nodes keep working.
was:
Yardstick scripts don't work under Solaris (SunOS). The problem in shell
commands like {{pgrep}} that work a little different than under Linux.
The output:
{noformat}
$ ./bin/benchmark-run-all.sh config/benchmark.properties
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=0
tail: cannot open input
<10:46:28> Starting server config '...' on localhost with id=1
tail: cannot open input
<10:46:32> Starting driver config '...' on localhost with id=0
ERROR: Driver process has not started on localhost during 10.0 seconds.
Type "--help" for usage.
<10:46:42> Driver is started on localhost with id=0
<10:46:42> Driver is stopped on localhost
<10:46:42> Server is stopped on localhost
<10:46:43> Server is stopped on localhost
{noformat}
But driver and server nodes keep working.
> Yardstick scripts don't work under Solaris (SunOS)
> --
>
> Key: IGNITE-2113
> URL: https://issues.apache.org/jira/browse/IGNITE-2113
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>
> Yardstick scripts don't work under Solaris (SunOS). The problem in shell
> commands like {{pgrep}} and {{pkill}} that work a little different than under
> Linux.
> The output:
> {noformat}
> $ ./bin/benchmark-run-all.sh config/benchmark.properties
> tail: cannot open input
> <10:46:28> Starting server config '...' on localhost with id=0
> tail: cannot open input
> <10:46:28> Starting server config '...' on localhost with id=1
> tail: cannot open input
> <10:46:32> Starting driver config '...' on localhost with id=0
> ERROR: Driver process has not started on localhost during 10.0 seconds.
> Type "--help" for usage.
> <10:46:42> Driver is started on localhost with id=0
> <10:46:42> Driver is stopped on localhost
> <10:46:42> Server is stopped on localhost
> <10:46:43> Server is stopped on localhost
> {noformat}
> But driver and server nodes keep working.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2097) Splitting Query example
[
https://issues.apache.org/jira/browse/IGNITE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-2097:
--
Description:
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called {{org.apache.ignite.examples.query}} and split
{{org.apache.ignite.examples.datagrid.CacheQueryExample}} into separate
examples like:
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
upd YZ: I think this should be done in separate package
{{org.apache.ignite.examples.datagrid.query}}
was:
CacheQueryExample is overloaded by query features. What's about to introduce a
new package e.g. called org.apache.ignite.examples.query and split
org.apache.ignite.examples.datagrid.CacheQueryExample into separate examples
like:
QueryScanExample
QueryJoinExample
QueryTextExample
QueryAggregationExample
QueryFieldsExample
QueryFieldsJoinExample
And add new ones:
QueryCrossCacheExample
QueryExplainExample
upd YZ: I think this should be done in separate package
{{org.apache.ignite.examples.datagrid.query}}
> Splitting Query example
> ---
>
> Key: IGNITE-2097
> URL: https://issues.apache.org/jira/browse/IGNITE-2097
> Project: Ignite
> Issue Type: Task
> Components: general
>Affects Versions: ignite-1.4, 1.5
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: 1.6
>
>
> CacheQueryExample is overloaded by query features. What's about to introduce
> a new package e.g. called {{org.apache.ignite.examples.query}} and split
> {{org.apache.ignite.examples.datagrid.CacheQueryExample}} into separate
> examples like:
> QueryScanExample
> QueryJoinExample
> QueryTextExample
> QueryAggregationExample
> QueryFieldsExample
> QueryFieldsJoinExample
> And add new ones:
> QueryCrossCacheExample
> QueryExplainExample
> upd YZ: I think this should be done in separate package
> {{org.apache.ignite.examples.datagrid.query}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2088) EntryProcessor invoke might not run in CLOCK write order
[
https://issues.apache.org/jira/browse/IGNITE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047413#comment-15047413
]
Noam Liran commented on IGNITE-2088:
Hi Dmitriy,
EPs are invoked both in CLOCK and PRIMARY mode;
However, when several EPs are queued at the same time in CLOCK mode, some will
be potentially dropped due to "old versions".
This in turn makes some invoke()s return null and not be executed.
Maybe one of these would be an appropriate fix (according to my understanding):
# Set ignoreTime (GridCacheMapEntry.java:1828) to true if op == TRANSFORM
# Throw exception / print a warning from invoke()s if called on cache
configured with CLOCK mode
# (less desirable IMO) Document that invoke()s might return null and instruct
user to retry if null is returned.
BR
Noam
> EntryProcessor invoke might not run in CLOCK write order
>
>
> Key: IGNITE-2088
> URL: https://issues.apache.org/jira/browse/IGNITE-2088
> Project: Ignite
> Issue Type: Bug
>Affects Versions: ignite-1.4
> Environment: Windows 8.1 64 bit
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Ignite 1.4.0
>Reporter: Avihai Berkovitz
>
> I have a program that runs several threads at the same time, all of them
> executing an invoke() on the same cache key to update it. I found that the
> EntryProcessor is not always executed, and in this case invoke() returns
> null. This happens when the cache is configured with CLOCK
> CacheAtomicWriteOrderMode, but not when using PRIMARY.
> After some debugging I found out that it happens when the cache gets the
> invocations out of order, and dismisses the older ones, returning the result
> from GridCacheMapEntry line 1855.
> As I understand it, this mechanism is in place to protect against
> out-of-order updates. Invokes, however, are a special case as they execute
> client code with unknown side effects that should not be discarded. If you
> believe the current behavior is correct, it should at least be documented.
> Here is a sample program to illustrate the problem. Notice that "IN INVOKE"
> is printed less than 10 times (usually):
> {code}
> IgniteConfiguration igniteConfiguration = new IgniteConfiguration()
> .setFailoverSpi(new AlwaysFailoverSpi())
> .setGridLogger(new Slf4jLogger())
> .setPeerClassLoadingEnabled(false)
> .setDeploymentMode(DeploymentMode.CONTINUOUS);
> Ignite ignite = Ignition.start(igniteConfiguration);
> CacheConfiguration cacheConfiguration = new
> CacheConfiguration()
> .setName("test")
> .setCacheMode(CacheMode.PARTITIONED)
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
>
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
> IgniteCache cache = ignite.getOrCreateCache(cacheConfiguration);
> Thread[] threads = new Thread[10];
> for (int i = 0; i < threads.length; i++) {
> threads[i] = new Thread() {
> @Override
> public void run() {
> System.out.println(String.format("Thread %s running",
> getId()));
> Long result = cache.invoke("key", (entry, arguments) ->
> {
> Long value = entry.getValue();
> System.out.println(String.format("IN INVOKE:
> thread ID:%s exists:%s value:%s", getId(), entry.exists(), value));
> if (!entry.exists()) {
> entry.setValue(getId());
> }
> return value;
> });
> System.out.println(String.format("Thread %s got invoke
> result %s", getId(), result));
> }
> };
> }
> for (Thread thread : threads) {
> thread.start();
> }
> Thread.sleep(2_000);
> for (Thread thread : threads) {
> thread.interrupt();
> }
> for (Thread thread : threads) {
> thread.join();
> }
> System.out.println("Done");
> {code}
> Output sample:
> {noformat}
> [13:51:41]__
> [13:51:41] / _/ ___/ |/ / _/_ __/ __/
> [13:51:41] _/ // (7 7// / / / / _/
> [13:51:41] /___/\___/_/|_/___/ /_/ /___/
> [13:51:41]
> [13:51:41] ver. 1.4.0#20150924-sha1:c2def5f6
> [13:51:41] 2015 Copyright(C) Apache Software Foundation
> [13:51:41]
> [13:51:41] Ignite documentation: http://ignite.apache.org
> [13:51:41]
> [13:51:41] Quiet mode.
> [13:51:41] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [13:51:41]
> [13:51:41] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
>
[jira] [Created] (IGNITE-2114) implemented ability to download configuration as independent logic
Dmitriyff created IGNITE-2114: - Summary: implemented ability to download configuration as independent logic Key: IGNITE-2114 URL: https://issues.apache.org/jira/browse/IGNITE-2114 Project: Ignite Issue Type: Sub-task Reporter: Dmitriyff Assignee: Dmitriyff -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2033) Refactoring summary page
[ https://issues.apache.org/jira/browse/IGNITE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047977#comment-15047977 ] ASF GitHub Bot commented on IGNITE-2033: GitHub user Dmitriyff opened a pull request: https://github.com/apache/ignite/pull/306 IGNITE-2033 Completed base refactoring added common directive to show generated code You can merge this pull request into a Git repository by running: $ git pull https://github.com/Dmitriyff/ignite ignite-2033 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/306.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 #306 commit dcc8ac31a69de541592ec92bcaa85ccc8f65a776 Author: Dmitriyff Date: 2015-12-01T04:01:03Z IGNITE-2033 added common directive callout commit f3fa4fe637c936f394b6066b0c0d223a91403005 Author: Dmitriyff Date: 2015-12-01T04:01:59Z IGNITE-2033 added licensed comment commit e8c13e9229b46cd2d959d6286d596ad650c8055d Author: Dmitriyff Date: 2015-12-01T09:10:35Z IGNITE-2033 refactoring summary page commit 6cdd62d6fb5acf7ee6ef16386b405aeca9ca072e Author: Dmitriyff Date: 2015-12-02T10:32:42Z IGNITE-2033 create new directives commit 819658208c79422a3ef6ac2b958b709cc699c013 Author: Dmitriyff Date: 2015-12-02T11:31:17Z IGNITE-843-rc2 update tasks commit 823ded7073fabd5b7aabe284636f06b09d50fbb0 Author: Dmitriyff Date: 2015-12-03T04:36:39Z IGNITE-2033 refactoring directives commit c5e1e8830df07ae0df624dccb45a8326b99c470a Author: Dmitriyff Date: 2015-12-03T04:46:37Z Merge branch 'ignite-843-rc2' into ignite-2033 commit f9fc42320b251cdfebf5bf4fb3d45192c48c05d1 Author: Dmitriyff Date: 2015-12-03T08:55:30Z IGNITE-2033 develop derictive to pojos commit 50e4f1ae990a50f456691844a2c876598eff69e9 Author: Dmitriyff Date: 2015-12-04T09:52:24Z IGNITE-2033 complete refactoring directives to ace commit 80eca7c62c17b4b69e32bd4b859f34d113987d00 Author: AKuznetsov Date: 2015-12-02T12:58:41Z IGNITE-843 Minor. commit 6c47a0c6e484c220622c371ee280affbc6127145 Author: Andrey Date: 2015-12-03T02:43:09Z IGNITE-843 Fixed path. commit e93cc7109d52bbf99ec23f631f7d6197f83865c9 Author: Andrey Date: 2015-12-03T03:13:07Z IGNITE-2066 Review. commit 70fdee1fc5b4c98c4b1c3a6be8abe87f89ebacde Author: Vasiliy Sisko Date: 2015-12-03T03:34:47Z IGNITE-1980 Minor message fix. commit 126cd50244e2badcb035969edcf0acdadcd09cb3 Author: Dmitriyff Date: 2015-12-03T03:44:44Z IGNITE-2067 fixed minimize version, logout method - Fixes #287. Signed-off-by: Andrey commit 18f62765274bd8aa6e2620d1f2485e08efcf6ed9 Author: Andrey Date: 2015-12-03T03:46:16Z IGNITE-2067 Review. commit d71e22a189ce8088a182cf06ccbff2eebe6f8032 Author: Alexey Kuznetsov Date: 2015-12-03T03:48:58Z IGNITE-843 Minor. commit 42731c48a81c297fa9e5dfeda9f7596e8e0e0673 Author: Andrey Date: 2015-12-03T04:17:19Z IGNITE-2067 Minor fix. commit 3f877064af85fb367940c9e0eded447c47ae31a9 Author: Andrey Date: 2015-12-03T04:21:22Z IGNITE-2067 Minor fix. commit eca59bad3ad2d74ae3dadcf28791042fa3613029 Author: Alexey Kuznetsov Date: 2015-12-03T06:30:27Z IGNITE-2039 Fixed typo. commit 2a6fa6be1a18b16a49db48b624393f413cd030b4 Author: Andrey Date: 2015-12-03T07:40:30Z IGNITE-2014 Fixed url. commit 3ddb22817cb79b5a8c323a364d730e3f24b4b8c8 Author: Andrey Date: 2015-12-03T08:20:37Z IGNITE-2051 Fixed expanded query. commit 4afb61511eabbf41d30eae7c77cabe041bad5e76 Author: Andrey Date: 2015-12-04T02:42:06Z IGNITE-843 Fixed cookie expire commit 0d8fe7767421f75b803c9719944ec6e90ca76028 Author: Andrey Date: 2015-12-04T03:36:38Z IGNITE-843 Fixed configuration sidebar commit 0bd5068fd374c4ce3b38c618f07cc5ed9b3e830e Author: Andrey Date: 2015-12-04T06:47:16Z IGNITE-843 Fixed message from agent in case of connect to secure grid. commit e63a3960528f1ae18710ae7fc9332155f0b091c7 Author: Andrey Date: 2015-12-04T08:26:54Z IGNITE-843 Fixed auth. commit 38bdcdddf9607b9c9d3e399d2412297a73881c09 Author: Vasiliy Sisko Date: 2015-12-07T09:56:59Z IGNITE-843 Minor UI fix. commit 2fc2df7e05e04bd6eb0bdd142cc675b4ee686e7f Author: Dmitriyff Date: 2015-12-01T09:10:35Z IGNITE-2033 refactoring summary page commit b09560394a5e89686cf1cf8074e3682b1d6aabdb Author: Dmitriyff Date: 2015-12-02T10:32:42Z IGNITE-2033 create new directives commit 96f6fc85d50cbd692c69042c60d0d02bf19fb180 Author: Dmitriyff Date: 2015-12-03T08:55:30Z IGNITE-2033 develop derictive to pojos commit a94893cd75ec5704410692a0199174860711e6fd Author: Dmitriyff Date: 2015-12-08T04:23:08Z Merge branch 'ignite-843-rc2' of https://github.com/apache/ignite into ignite-2033
[jira] [Updated] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution
[
https://issues.apache.org/jira/browse/IGNITE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-2110:
-
Fix Version/s: 1.5
> Replace workarond for local node flag in TcpDiscoveryNode with better solution
> --
>
> Key: IGNITE-2110
> URL: https://issues.apache.org/jira/browse/IGNITE-2110
> Project: Ignite
> Issue Type: Task
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Minor
> Fix For: 1.5
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We should get read of this workaround in
> GridDhtAffinityAssignmentResponse#finishUnmarshal
> {code:java}
> // TODO IGNITE-10: setting 'local' for nodes not needed when
> IGNITE-10 is implemented.
> int assignments = affAssignment.size();
> for (int n = 0; n < assignments; n++) {
> List nodes = affAssignment.get(n);
> int size = nodes.size();
> for (int i = 0; i < size; i++) {
> ClusterNode node = nodes.get(i);
> if (node instanceof TcpDiscoveryNode)
>
> ((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
> }
> }
> {code}
> by designing new solution for TcpDiscoveryNode.local transient flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution
[
https://issues.apache.org/jira/browse/IGNITE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-2110:
Assignee: Vladimir Ershov
Vladimir,
I think to fix issue with 'TcpDiscoveryNode.local' flag we need to call
IgnitionEx.localIgnite() from TcpDiscoveryNode.readExternal and set local =
nodeId.equals(IgnitionEx.localIgnite(IgnitionEx.localIgnite().getLocalNodeId()).
> Replace workarond for local node flag in TcpDiscoveryNode with better solution
> --
>
> Key: IGNITE-2110
> URL: https://issues.apache.org/jira/browse/IGNITE-2110
> Project: Ignite
> Issue Type: Task
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ershov
>Assignee: Vladimir Ershov
>Priority: Minor
> Fix For: 1.5
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> We should get read of this workaround in
> GridDhtAffinityAssignmentResponse#finishUnmarshal
> {code:java}
> // TODO IGNITE-10: setting 'local' for nodes not needed when
> IGNITE-10 is implemented.
> int assignments = affAssignment.size();
> for (int n = 0; n < assignments; n++) {
> List nodes = affAssignment.get(n);
> int size = nodes.size();
> for (int i = 0; i < size; i++) {
> ClusterNode node = nodes.get(i);
> if (node instanceof TcpDiscoveryNode)
>
> ((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
> }
> }
> {code}
> by designing new solution for TcpDiscoveryNode.local transient flag
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1692) [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
[
https://issues.apache.org/jira/browse/IGNITE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh resolved IGNITE-1692.
--
Resolution: Fixed
> [Test] DataStreamProcessorSelfTest.testReplicated fails sometimes.
> --
>
> Key: IGNITE-1692
> URL: https://issues.apache.org/jira/browse/IGNITE-1692
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Veselovsky
>Assignee: Ilya Lantukh
>
> DataStreamProcessorSelfTest.testReplicated fails with ~7% probability with
> the following error:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to find server node for
> cache (all affinity nodes have left the grid or cache was stopped): null
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:311)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture$Listener.apply(GridCompoundFuture.java:302)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners(GridFutureAdapter.java:250)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:380)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:346)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:334)
> at
> org.apache.ignite.testframework.GridTestUtils$5.run(GridTestUtils.java:675)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:966)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by: org.apache.ignite.cache.CacheServerNotFoundException: Failed to
> find server node for cache (all affinity nodes have left the grid or cache
> was stopped): null
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:56)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:122)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:232)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> Caused by:
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to find server node for cache (all affinity nodes have left the grid
> or cache was stopped): null
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.nodes(DataStreamerImpl.java:772)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:638)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:547)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:583)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessorSelfTest$1.call(DataStreamProcessorSelfTest.java:226)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
[
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048220#comment-15048220
]
Semen Boikov commented on IGNITE-2080:
--
Andrey,
I still see suspicious unsafe usages in following places:
- GridCacheOffheapSwapEntry
- IgniteUtils.readVersion(long ptr, boolean verEx)
- PlatformMemoryUtils
- PlatformOutputStreamImpl/PlatformInputStreamImpl
- PortableOffheapInputStream/PortableOffheapOutputStream
Are you sure 'it is safe to not use 'aligned' get/put in these places.
Please also fix javadoc warnings in GridUnsafe: 'return' is missed in many
places.
> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties,
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode
> solaris-sparc )
> # Problematic frame:
> # V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700], sp=0xfff0f6ffd1f0, free
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearA
