[jira] [Commented] (IGNITE-1000) Inconsistency: Jcloud changed credential format for Google Compute Engine
[ https://issues.apache.org/jira/browse/IGNITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730665#comment-14730665 ] Denis Magda commented on IGNITE-1000: - Keys are updated on public TC. > Inconsistency: Jcloud changed credential format for Google Compute Engine > - > > Key: IGNITE-1000 > URL: https://issues.apache.org/jira/browse/IGNITE-1000 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-6 >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: ignite-1.4 > > > Jclouds updated its version of the product, changed format of the file where > a key is stored for Google Compute Engine. > They also changed documentation which we rely on. That's why we must to > update our implementation, comments, configs respectively. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1364) Move C++ platform to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1364. --- Onle actual code has been moved. Examples, TC builds and docs will be handled in separate tickets. > Move C++ platform to Ignite. > > > Key: IGNITE-1364 > URL: https://issues.apache.org/jira/browse/IGNITE-1364 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: ignite-1.5 > > > This involves: > 1) Moving code base; > 2) Moving examples; > 3) Fixing doxygen docs generation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.
[ https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-1353. --- > PortableContext.typeId() incorrectly resolves type ID for predefined system > types. > -- > > Key: IGNITE-1353 > URL: https://issues.apache.org/jira/browse/IGNITE-1353 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Denis Magda >Priority: Critical > Fix For: ignite-1.5 > > > See PortableContext.typeId() method. > First it checks whether type is "system", and only then try picking > predefiend ID. As a result, predefined types like IgniteBiTuple are written > with wrong IDs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1374) Error org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type during a cache iteration
[
https://issues.apache.org/jira/browse/IGNITE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730701#comment-14730701
]
Enrico Olivelli commented on IGNITE-1374:
-
I have 2 server nodes (hosted in JVM process, not lanunched from the command
line), on servers no error is reported on logs
The error is on a ClientMode = true node
> Error org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type during a cache iteration
> -
>
> Key: IGNITE-1374
> URL: https://issues.apache.org/jira/browse/IGNITE-1374
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Enrico Olivelli
>Priority: Blocker
>
> Using ignite 1.3.0-incubating I get this error while issuing an iteration on
> a cache
> {code}
> Set keys = new HashSet<>();
> for (Iterator> it = cache.iterator();
> it.hasNext();) {
> String key = it.next().getKey();
> if (key.startsWith(prefix)) {
> keys.add(remaining);
> }
> }
> {code}
> This is the error
> {code}
> GRAVE: Failed to process message
> [senderId=a9548f63-2ac4-4600-a593-dfcdca71aa38, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse
> [finished=false, reqId=934, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:507)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:232)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1018)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2086)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:942)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:911)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1368) Unable to build apache ignite
[
https://issues.apache.org/jira/browse/IGNITE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov closed IGNITE-1368.
> Unable to build apache ignite
> -
>
> Key: IGNITE-1368
> URL: https://issues.apache.org/jira/browse/IGNITE-1368
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: ignite-1.4
> Environment: OS X 10.10.3
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> Steps for reproduction:
> 1. {noformat}git clone
> https://git-wip-us.apache.org/repos/asf/ignite{noformat}
> 2. {noformat}cd ignite/{noformat}
> 3. {noformat}mvn clean package -DskipTests{noformat}
> Result:
> {noformat}
> ...
> JavaDoc error: 'Other Packages' section should not be present, all packages
> should have corresponding documentation groups:
> /Users/gridgain/111/ignite/target/javadoc/core/overview-summary.html
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-apache-license-gen .. SUCCESS [ 1.571
> s]
> [INFO] ignite-tools ... SUCCESS [ 8.336
> s]
> [INFO] ignite-core SUCCESS [01:07
> min]
> [INFO] ignite-log4j ... SUCCESS [ 3.073
> s]
> [INFO] ignite-urideploy ... SUCCESS [ 2.891
> s]
> [INFO] ignite-spring .. SUCCESS [ 2.572
> s]
> [INFO] ignite-hadoop .. SUCCESS [ 9.678
> s]
> [INFO] ignite-extdata-p2p . SUCCESS [ 2.950
> s]
> [INFO] ignite-extdata-uri-dep . SUCCESS [ 1.587
> s]
> [INFO] ignite-extdata-uri . SUCCESS [ 0.541
> s]
> [INFO] ignite-indexing SUCCESS [ 5.057
> s]
> [INFO] ignite-rest-http ... SUCCESS [ 1.955
> s]
> [INFO] ignite-clients . SUCCESS [ 0.759
> s]
> [INFO] ignite-web . SUCCESS [ 1.869
> s]
> [INFO] ignite-aop . SUCCESS [ 2.114
> s]
> [INFO] ignite-ssh . SUCCESS [ 1.526
> s]
> [INFO] ignite-jta . SUCCESS [ 1.829
> s]
> [INFO] ignite-aws . SUCCESS [ 2.339
> s]
> [INFO] ignite-log4j2 .. SUCCESS [ 1.947
> s]
> [INFO] ignite-slf4j ... SUCCESS [ 1.701
> s]
> [INFO] ignite-jcl . SUCCESS [ 1.640
> s]
> [INFO] ignite-codegen . SUCCESS [ 1.650
> s]
> [INFO] ignite-gce . SUCCESS [ 1.881
> s]
> [INFO] ignite-cloud ... SUCCESS [ 2.728
> s]
> [INFO] ignite-mesos ... SUCCESS [ 2.696
> s]
> [INFO] ignite-kafka ... SUCCESS [ 1.961
> s]
> [INFO] ignite-yarn SUCCESS [ 7.675
> s]
> [INFO] ignite-jms11 ... SUCCESS [ 1.981
> s]
> [INFO] ignite-zookeeper ... SUCCESS [ 1.838
> s]
> [INFO] ignite-platform SUCCESS [ 4.888
> s]
> [INFO] ignite-scalar .. SUCCESS [ 45.905
> s]
> [INFO] ignite-spark ... SUCCESS [ 15.945
> s]
> [INFO] ignite-visor-console ... SUCCESS [ 47.642
> s]
> [INFO] ignite-visor-plugins ... SUCCESS [ 1.941
> s]
> [INFO] ignite-schema-import ... SUCCESS [ 3.566
> s]
> [INFO] apache-ignite .. FAILURE [ 21.677
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:48 min
> [INFO] Finished at: 2015-09-03T17:56:45+03:00
> [INFO] Final Memory: 175M/1252M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (javadoc-postprocessing)
> on project apache-ignite: An Ant BuildException has occured: Execution failed
> due to previous errors.
> [ERROR] around Ant part ... css="dotted">... @ 11:51 in
>
[jira] [Resolved] (IGNITE-1368) Unable to build apache ignite
[
https://issues.apache.org/jira/browse/IGNITE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov resolved IGNITE-1368.
--
Resolution: Fixed
Assignee: Ilya Suntsov (was: Vladimir Ozerov)
Fix confirmed
> Unable to build apache ignite
> -
>
> Key: IGNITE-1368
> URL: https://issues.apache.org/jira/browse/IGNITE-1368
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: ignite-1.4
> Environment: OS X 10.10.3
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> Steps for reproduction:
> 1. {noformat}git clone
> https://git-wip-us.apache.org/repos/asf/ignite{noformat}
> 2. {noformat}cd ignite/{noformat}
> 3. {noformat}mvn clean package -DskipTests{noformat}
> Result:
> {noformat}
> ...
> JavaDoc error: 'Other Packages' section should not be present, all packages
> should have corresponding documentation groups:
> /Users/gridgain/111/ignite/target/javadoc/core/overview-summary.html
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ignite-apache-license-gen .. SUCCESS [ 1.571
> s]
> [INFO] ignite-tools ... SUCCESS [ 8.336
> s]
> [INFO] ignite-core SUCCESS [01:07
> min]
> [INFO] ignite-log4j ... SUCCESS [ 3.073
> s]
> [INFO] ignite-urideploy ... SUCCESS [ 2.891
> s]
> [INFO] ignite-spring .. SUCCESS [ 2.572
> s]
> [INFO] ignite-hadoop .. SUCCESS [ 9.678
> s]
> [INFO] ignite-extdata-p2p . SUCCESS [ 2.950
> s]
> [INFO] ignite-extdata-uri-dep . SUCCESS [ 1.587
> s]
> [INFO] ignite-extdata-uri . SUCCESS [ 0.541
> s]
> [INFO] ignite-indexing SUCCESS [ 5.057
> s]
> [INFO] ignite-rest-http ... SUCCESS [ 1.955
> s]
> [INFO] ignite-clients . SUCCESS [ 0.759
> s]
> [INFO] ignite-web . SUCCESS [ 1.869
> s]
> [INFO] ignite-aop . SUCCESS [ 2.114
> s]
> [INFO] ignite-ssh . SUCCESS [ 1.526
> s]
> [INFO] ignite-jta . SUCCESS [ 1.829
> s]
> [INFO] ignite-aws . SUCCESS [ 2.339
> s]
> [INFO] ignite-log4j2 .. SUCCESS [ 1.947
> s]
> [INFO] ignite-slf4j ... SUCCESS [ 1.701
> s]
> [INFO] ignite-jcl . SUCCESS [ 1.640
> s]
> [INFO] ignite-codegen . SUCCESS [ 1.650
> s]
> [INFO] ignite-gce . SUCCESS [ 1.881
> s]
> [INFO] ignite-cloud ... SUCCESS [ 2.728
> s]
> [INFO] ignite-mesos ... SUCCESS [ 2.696
> s]
> [INFO] ignite-kafka ... SUCCESS [ 1.961
> s]
> [INFO] ignite-yarn SUCCESS [ 7.675
> s]
> [INFO] ignite-jms11 ... SUCCESS [ 1.981
> s]
> [INFO] ignite-zookeeper ... SUCCESS [ 1.838
> s]
> [INFO] ignite-platform SUCCESS [ 4.888
> s]
> [INFO] ignite-scalar .. SUCCESS [ 45.905
> s]
> [INFO] ignite-spark ... SUCCESS [ 15.945
> s]
> [INFO] ignite-visor-console ... SUCCESS [ 47.642
> s]
> [INFO] ignite-visor-plugins ... SUCCESS [ 1.941
> s]
> [INFO] ignite-schema-import ... SUCCESS [ 3.566
> s]
> [INFO] apache-ignite .. FAILURE [ 21.677
> s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:48 min
> [INFO] Finished at: 2015-09-03T17:56:45+03:00
> [INFO] Final Memory: 175M/1252M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (javadoc-postprocessing)
> on project apache-ignite: An Ant BuildException has occured: Execution failed
> due to previous errors.
> [ERROR]
[jira] [Commented] (IGNITE-1348) Move .Net platform from GridGain to Ignite.
[ https://issues.apache.org/jira/browse/IGNITE-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730564#comment-14730564 ] Vladimir Ozerov commented on IGNITE-1348: - Pavel, Overall everything looks fine. Please address the following outstanding issues: 1) Rename all remaining Grid* classes. This prefix can be either removed (e.g. in tests) or changed to "Ignite". 2) Search for a word "grid". You will find lots of problems in docs. In some places "grid" must be changed to "Ignite" (be careful with casing), in some places it must be removed (e.g. GridFailoverSpi -> FailoverSpi), etc.. Try minimize usage of "grid" word. > Move .Net platform from GridGain to Ignite. > --- > > Key: IGNITE-1348 > URL: https://issues.apache.org/jira/browse/IGNITE-1348 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: ignite-1.5 > > > It is necessary to move the whole .Net module from GridGain to Ignite. > We must: > 1) Rename GridFactory -> Ignition. > 2) Rename IGrid -> IIgnite > 3) Rename all other "Grid*" classes (if any) to Ignite's counterparts. > 4) Set correct Apache headers everywhere. > 5) Ensure RAT exclusing are set in IGNITE_HOME/parent module. > 6) Copy unit-test specific classes > Exclude DR, Security, Product, Licensing, and corresponding events. > Once ticket is completed, it is necessary to create another one to update > Ignite's build procedure. > Fixes to port from GG: > https://issues.apache.org/jira/browse/IGNITE-1354 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.
[ https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730634#comment-14730634 ] ASF GitHub Bot commented on IGNITE-1353: Github user dmagda closed the pull request at: https://github.com/apache/ignite/pull/59 > PortableContext.typeId() incorrectly resolves type ID for predefined system > types. > -- > > Key: IGNITE-1353 > URL: https://issues.apache.org/jira/browse/IGNITE-1353 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Denis Magda >Priority: Critical > Fix For: ignite-1.5 > > > See PortableContext.typeId() method. > First it checks whether type is "system", and only then try picking > predefiend ID. As a result, predefined types like IgniteBiTuple are written > with wrong IDs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1365) Unable to deserialize object because class ID key is not in the cache
[
https://issues.apache.org/jira/browse/IGNITE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730676#comment-14730676
]
Semen Boikov commented on IGNITE-1365:
--
Looks like this is failure scenario:
- daemon node is started first (topVer=1)
- then server node is started (topVer=2)
- exchange for topVer=2 is still in progress, daemon node sends jobs to server,
server marshalls result and sends response
- exchange for topVer=2 is still in progress, daemon node receives response and
tries to get value from marshaller cache using ready affinity version topVer=1,
at topVer=1 marshaller cache server node is not started yet and
ClusterTopologyServerNotFoundException is thrown
> Unable to deserialize object because class ID key is not in the cache
> -
>
> Key: IGNITE-1365
> URL: https://issues.apache.org/jira/browse/IGNITE-1365
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Semen Boikov
>Priority: Critical
>
> There is a test that fails because of object deserialization issue:
> http://204.14.53.153/viewLog.html?buildId=65291=buildResultsDiv=Ignite_IgniteBasic#testNameId7413691472559096192
> According to the log, the reason of the failure is the following:
> {noformat}
> Caused by: class
> org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException:
> Failed to map keys for cache (all partition nodes left the grid).
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.map(GridPartitionedGetFuture.java:308)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.init(GridPartitionedGetFuture.java:199)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync0(GridDhtAtomicCache.java:1048)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1300(GridDhtAtomicCache.java:124)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:336)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:648)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync(GridDhtAtomicCache.java:334)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.getTopologySafe(GridCacheAdapter.java:1345)
> at
> org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:148)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:256)
> {noformat}
> However, if to take a look at the test code we will see that this situation
> is impossible: all the nodes should be alive during the test's execution.
> It means that the issue is somewhere in {{GridCacheAdapter.getTopologySafe}}
> implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1375) Move CPP tests for "src/test" folder.
Vladimir Ozerov created IGNITE-1375: --- Summary: Move CPP tests for "src/test" folder. Key: IGNITE-1375 URL: https://issues.apache.org/jira/browse/IGNITE-1375 Project: Ignite Issue Type: Sub-task Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: ignite-1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731442#comment-14731442
]
Valentin Kulichenko commented on IGNITE-1238:
-
Raul, you can use scenario described here to reproduce the issue:
https://issues.apache.org/jira/browse/IGNITE-1205. Just replace Visor with an
ordinary node started with {{ignite.sh}} (i.e., without additional classes on
classpath). This node will join topology, but it should not be able to do this.
> Joining node should be discarded in case discovery exchange data can't be
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Currently a node will join even if unmarshalling fails (see
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected
> behaviour. For example, a continuous query listener is not deployed on some
> nodes in topology. Everything works, but some updates are lost. We should
> discard the node in this case and give a good error message to user with
> information on how to fix it properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1047) Make warning text more informative
[
https://issues.apache.org/jira/browse/IGNITE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-1047.
-
Resolution: Fixed
Fixed in 1.4 and master.
> Make warning text more informative
> --
>
> Key: IGNITE-1047
> URL: https://issues.apache.org/jira/browse/IGNITE-1047
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Valentin Kulichenko
>Priority: Trivial
> Fix For: ignite-1.4
>
>
> {code}
> [11:05:17,023][WARNING][ignite-#8%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,032][WARNING][ignite-#9%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,037][WARNING][ignite-#9%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,043][WARNING][ignite-#10%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,047][WARNING][ignite-#10%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,058][WARNING][ignite-#11%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,064][WARNING][ignite-#11%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> {code}
> And may be also we need throttling here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1047) Make warning text more informative
[
https://issues.apache.org/jira/browse/IGNITE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-1047.
---
> Make warning text more informative
> --
>
> Key: IGNITE-1047
> URL: https://issues.apache.org/jira/browse/IGNITE-1047
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-6
>Reporter: Pavel Konstantinov
>Assignee: Valentin Kulichenko
>Priority: Trivial
> Fix For: ignite-1.4
>
>
> {code}
> [11:05:17,023][WARNING][ignite-#8%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,032][WARNING][ignite-#9%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,037][WARNING][ignite-#9%pub-tester%][MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,043][WARNING][ignite-#10%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,047][WARNING][ignite-#10%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,058][WARNING][ignite-#11%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> [11:05:17,064][WARNING][ignite-#11%pub-tester%]MarshallerContextImpl] class
> o.a.i.i.processors.cache.GridCacheTryPutFailedException: null
> {code}
> And may be also we need throttling here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731640#comment-14731640
]
Valentin Kulichenko commented on IGNITE-1370:
-
Raul,
I looked at your changes. They look good, but I think we should throw an
exception if both single and multiple extractors are set, because only multiple
will be used.
Also it looks like multiple extractor supports all cases, so single can be
deprecated. What do you think?
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1378) Continuous processor doesn't remove message listener if continuous query failed to start
Valentin Kulichenko created IGNITE-1378:
---
Summary: Continuous processor doesn't remove message listener if
continuous query failed to start
Key: IGNITE-1378
URL: https://issues.apache.org/jira/browse/IGNITE-1378
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Blocker
Fix For: ignite-1.4
{{GridContinuousProcessor.startRoutine(..)}} method adds message listener on
line 538 and never removes it if handler registration fails (e.g., due to
marshalling issues). Need to fix exception handling in this method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-884) Cache store usability issues
[
https://issues.apache.org/jira/browse/IGNITE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-884:
---
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> Cache store usability issues
>
>
> Key: IGNITE-884
> URL: https://issues.apache.org/jira/browse/IGNITE-884
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: ignite-1.5
>
>
> * Need to validate read/write-through configuration. Currently, when cache
> store is configured, but {{readThrough}} and {{writeThrough}} flags on
> {{CacheConfiguration}} are switched off, the store will never be called,
> which is confusing. This case should be validated and proper warning should
> be printed out on startup (we can't throw an exception here because in some
> cases store implements only {{loadCache}} method and is not used for
> read/write-through).
> * Since cache store is instantiated by Ignite via factory, but not by Spring,
> user can't use Spring auto-wiring which is very common in Spring apps. Need
> to create utility method which will instantiate an instance with a factory
> and properly initialize it. All factory calls (store, expiry policy, ...)
> should be replaced with this utility method.
> To manually enable autowiring this code can be used:
> {code}
> appCtx.getAutowireCapableBeanFactory().autowireBean(obj);
> {code}
> ({{appCtx}} is Spring's {{ApplicationContext}})
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-940) Need to expose SQL metadata to public API
[
https://issues.apache.org/jira/browse/IGNITE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-940:
---
Fix Version/s: (was: ignite-1.4)
ignite-1.5
> Need to expose SQL metadata to public API
> -
>
> Key: IGNITE-940
> URL: https://issues.apache.org/jira/browse/IGNITE-940
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-5
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: Usability, user-request
> Fix For: ignite-1.5
>
>
> This is the request from one of our users.
> We already have {{GridCacheSqlMetadata}} and {{GridCacheSqlIndexMetadata}}
> interfaces and {{GridCacheQueryManager.sqlMetadata()}} method.
> Need to move interfaces to public package and add a new method on
> {{IgniteCache}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-995) Nodes on one host doesn't discover each other if IP finder doesn't explicitly provide port
[ https://issues.apache.org/jira/browse/IGNITE-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-995: --- Fix Version/s: (was: ignite-1.4) ignite-1.5 > Nodes on one host doesn't discover each other if IP finder doesn't explicitly > provide port > -- > > Key: IGNITE-995 > URL: https://issues.apache.org/jira/browse/IGNITE-995 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: sprint-4 >Reporter: Valentin Kulichenko >Assignee: Valentin Kulichenko > Labels: Usability > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1377) Portable metadata update on changing topology causes hangs in tests
Alexey Goncharuk created IGNITE-1377:
Summary: Portable metadata update on changing topology causes
hangs in tests
Key: IGNITE-1377
URL: https://issues.apache.org/jira/browse/IGNITE-1377
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
I removed metadata update on for objects not defined in configuration (this is
not an introduced bug, it existed before) because it causes portable failover
suite to hang.
Need to investigate further the cause of the hang and unmute
{{testNoConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1366) Start CacheProcessor before QueryProcessor
[ https://issues.apache.org/jira/browse/IGNITE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov closed IGNITE-1366. Assignee: (was: Semen Boikov) > Start CacheProcessor before QueryProcessor > -- > > Key: IGNITE-1366 > URL: https://issues.apache.org/jira/browse/IGNITE-1366 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Priority: Critical > Fix For: ignite-1.4 > > > Now QueryProcessor is started before CacheProcessor. With this order cache > processor can be stopped at the moment when query request is processed, and > this causes sporadic errors like NPE (I see this from time to time in > IgniteCacheQueryNodeRestartSelfTest). > Looks like cache processor does not need QueryProcessor when it's 'start' > method is called so I think start order should be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1333) SQL Group index can return wrong restult in half-bounded conditions
[ https://issues.apache.org/jira/browse/IGNITE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergi Vladykin closed IGNITE-1333. -- > SQL Group index can return wrong restult in half-bounded conditions > --- > > Key: IGNITE-1333 > URL: https://issues.apache.org/jira/browse/IGNITE-1333 > Project: Ignite > Issue Type: Bug >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin >Priority: Blocker > Fix For: ignite-1.4 > > > In case of Group index (a,b) and condition `a = ? and b > ?` query can > incorrectly return empty result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1333) SQL Group index can return wrong restult in half-bounded conditions
[ https://issues.apache.org/jira/browse/IGNITE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergi Vladykin resolved IGNITE-1333. Resolution: Fixed PR merged to 1.4 > SQL Group index can return wrong restult in half-bounded conditions > --- > > Key: IGNITE-1333 > URL: https://issues.apache.org/jira/browse/IGNITE-1333 > Project: Ignite > Issue Type: Bug >Reporter: Sergi Vladykin >Assignee: Sergi Vladykin >Priority: Blocker > Fix For: ignite-1.4 > > > In case of Group index (a,b) and condition `a = ? and b > ?` query can > incorrectly return empty result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
