[jira] [Updated] (IGNITE-4740) Service could be deployed/undeployed twice on concurrent cancel and discovery event
[ https://issues.apache.org/jira/browse/IGNITE-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-4740: Summary: Service could be deployed/undeployed twice on concurrent cancel and discovery event (was: Service could be deployed twice on concurrent cancel and discovery event) > Service could be deployed/undeployed twice on concurrent cancel and discovery > event > --- > > Key: IGNITE-4740 > URL: https://issues.apache.org/jira/browse/IGNITE-4740 > Project: Ignite > Issue Type: Bug > Components: managed services >Affects Versions: 1.8 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > In case of concurrent service cancel and discovery event, for example, > applying continuous query, may cause double service deploy/undeploy. > Fix should consist in filtering such DiscoveryCustomEvent in > GridServiceProcessor.TopologyListener. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877697#comment-15877697 ] Ryabov Dmitrii commented on IGNITE-602: --- How to unmute it on TC? Class contining this test is already in basic test suit. > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii > Labels: Muted_test > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. > see GG-5000. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4740) Service could be deployed twice on concurrent cancel and discovery event
[ https://issues.apache.org/jira/browse/IGNITE-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-4740: Description: In case of concurrent service cancel and discovery event, for example, applying continuous query, may cause double service deploy/undeploy. Fix should consist in filtering such DiscoveryCustomEvent in GridServiceProcessor.TopologyListener. was: In case of concurrent service cancel and discovery event, for example, applying continuous query, may cause double init() and execute() service method invocation. Fix should consist at least in filtering such DiscoveryCustomEvent in GridServiceProcessor.TopologyListener. The best solution is guarantee that despite of any discovery event service won't be intialized more than once. > Service could be deployed twice on concurrent cancel and discovery event > > > Key: IGNITE-4740 > URL: https://issues.apache.org/jira/browse/IGNITE-4740 > Project: Ignite > Issue Type: Bug > Components: managed services >Affects Versions: 1.8 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > In case of concurrent service cancel and discovery event, for example, > applying continuous query, may cause double service deploy/undeploy. > Fix should consist in filtering such DiscoveryCustomEvent in > GridServiceProcessor.TopologyListener. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4740) Service could be deployed twice on concurrent cancel and discovery event
[ https://issues.apache.org/jira/browse/IGNITE-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-4740: Summary: Service could be deployed twice on concurrent cancel and discovery event (was: Service could be initialized twice on concurrent cancel and discovery event) > Service could be deployed twice on concurrent cancel and discovery event > > > Key: IGNITE-4740 > URL: https://issues.apache.org/jira/browse/IGNITE-4740 > Project: Ignite > Issue Type: Bug > Components: managed services >Affects Versions: 1.8 >Reporter: Dmitry Karachentsev >Assignee: Dmitry Karachentsev > Fix For: 2.0 > > > In case of concurrent service cancel and discovery event, for example, > applying continuous query, may cause double init() and execute() service > method invocation. > Fix should consist at least in filtering such DiscoveryCustomEvent in > GridServiceProcessor.TopologyListener. > The best solution is guarantee that despite of any discovery event service > won't be intialized more than once. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4740) Service could be initialized twice on concurrent cancel and discovery event
Dmitry Karachentsev created IGNITE-4740: --- Summary: Service could be initialized twice on concurrent cancel and discovery event Key: IGNITE-4740 URL: https://issues.apache.org/jira/browse/IGNITE-4740 Project: Ignite Issue Type: Bug Components: managed services Affects Versions: 1.8 Reporter: Dmitry Karachentsev Assignee: Dmitry Karachentsev Fix For: 2.0 In case of concurrent service cancel and discovery event, for example, applying continuous query, may cause double init() and execute() service method invocation. Fix should consist at least in filtering such DiscoveryCustomEvent in GridServiceProcessor.TopologyListener. The best solution is guarantee that despite of any discovery event service won't be intialized more than once. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4739) CacheJdbcPojoStore: Add upsert support for PostgreSQL dialect
Andrey Novikov created IGNITE-4739: -- Summary: CacheJdbcPojoStore: Add upsert support for PostgreSQL dialect Key: IGNITE-4739 URL: https://issues.apache.org/jira/browse/IGNITE-4739 Project: Ignite Issue Type: Improvement Components: SQL Reporter: Andrey Novikov Priority: Minor https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.5#INSERT_..._ON_CONFLICT_DO_NOTHING.2FUPDATE_.28.22UPSERT.22.29 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4652) Optimization: implement BPlusTree.invoke
[ https://issues.apache.org/jira/browse/IGNITE-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-4652. -- Resolution: Fixed Assignee: (was: Semen Boikov) > Optimization: implement BPlusTree.invoke > > > Key: IGNITE-4652 > URL: https://issues.apache.org/jira/browse/IGNITE-4652 > Project: Ignite > Issue Type: Task > Components: cache >Reporter: Semen Boikov > Fix For: 2.0 > > > Currently for atomic cache update we first read previous cache value > (BPlusTree.find), then depending on some cache logic can do put or remove > (BPlusTree.put/remove). It is possible to get rid of first BPlusTree.find if > BPlusTree provide 'invoke' operation similar to IgnteCache.invoke. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-4226) Redis SET command should handle expirations
[ https://issues.apache.org/jira/browse/IGNITE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-4226. -- Assignee: (was: Roman Shtykh) > Redis SET command should handle expirations > --- > > Key: IGNITE-4226 > URL: https://issues.apache.org/jira/browse/IGNITE-4226 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.8 >Reporter: Roman Shtykh > Labels: redis > Fix For: 2.0 > > > Handling EX and PX parameters of SET command. > https://redis.io/commands/set -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4226) Redis SET command should handle expirations
[ https://issues.apache.org/jira/browse/IGNITE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877424#comment-15877424 ] ASF GitHub Bot commented on IGNITE-4226: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1510 > Redis SET command should handle expirations > --- > > Key: IGNITE-4226 > URL: https://issues.apache.org/jira/browse/IGNITE-4226 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.8 >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Labels: redis > Fix For: 2.0 > > > Handling EX and PX parameters of SET command. > https://redis.io/commands/set -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4226) Redis SET command should handle expirations
[ https://issues.apache.org/jira/browse/IGNITE-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877373#comment-15877373 ] Roman Shtykh commented on IGNITE-4226: -- [~anovikov] You are right. Please see the changes. > Redis SET command should handle expirations > --- > > Key: IGNITE-4226 > URL: https://issues.apache.org/jira/browse/IGNITE-4226 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.8 >Reporter: Roman Shtykh >Assignee: Roman Shtykh > Labels: redis > Fix For: 2.0 > > > Handling EX and PX parameters of SET command. > https://redis.io/commands/set -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-4737) Update Apache Flink dependencies to the latest version
[ https://issues.apache.org/jira/browse/IGNITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh closed IGNITE-4737. > Update Apache Flink dependencies to the latest version > -- > > Key: IGNITE-4737 > URL: https://issues.apache.org/jira/browse/IGNITE-4737 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Fix For: 2.0 > > > https://flink.apache.org/downloads.html#maven-dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4737) Update Apache Flink dependencies to the latest version
[ https://issues.apache.org/jira/browse/IGNITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877341#comment-15877341 ] ASF GitHub Bot commented on IGNITE-4737: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1567 > Update Apache Flink dependencies to the latest version > -- > > Key: IGNITE-4737 > URL: https://issues.apache.org/jira/browse/IGNITE-4737 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > Fix For: 2.0 > > > https://flink.apache.org/downloads.html#maven-dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4737) Update Apache Flink dependencies to the latest version
[ https://issues.apache.org/jira/browse/IGNITE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877326#comment-15877326 ] ASF GitHub Bot commented on IGNITE-4737: GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1567 IGNITE-4737: Update Apache Flink dependencies to 1.2.0. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-4737 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1567.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 #1567 commit 6ddf32ba54808fa7940f65059f7d4dbc1289b7fc Author: shtykh_roman Date: 2017-02-22T02:37:12Z IGNITE-4737: Update Apache Flink dependencies to 1.2.0. > Update Apache Flink dependencies to the latest version > -- > > Key: IGNITE-4737 > URL: https://issues.apache.org/jira/browse/IGNITE-4737 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Minor > > https://flink.apache.org/downloads.html#maven-dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4738) Support REGEXP_LIKE and REGEXP_REPLACE SQL functions
Valentin Kulichenko created IGNITE-4738: --- Summary: Support REGEXP_LIKE and REGEXP_REPLACE SQL functions Key: IGNITE-4738 URL: https://issues.apache.org/jira/browse/IGNITE-4738 Project: Ignite Issue Type: Improvement Components: SQL Affects Versions: 1.8 Reporter: Valentin Kulichenko Fix For: 2.0 These functions are supported by H2 in their latest version, but not in the version Ignite depends on. Most likely we just need to upgrade H2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
[ https://issues.apache.org/jira/browse/IGNITE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-3315. --- > CPP: Add documentation for ContinuousQuery API > -- > > Key: IGNITE-3315 > URL: https://issues.apache.org/jira/browse/IGNITE-3315 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.6 >Reporter: Igor Sapego >Assignee: Denis Magda >Priority: Minor > Labels: cpp > Fix For: 1.9 > > > We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we > also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-4619) .NET: TransactionScope documentation and example
[
https://issues.apache.org/jira/browse/IGNITE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Garg closed IGNITE-4619.
---
> .NET: TransactionScope documentation and example
>
>
> Key: IGNITE-4619
> URL: https://issues.apache.org/jira/browse/IGNITE-4619
> Project: Ignite
> Issue Type: Task
> Components: documentation, platforms
>Affects Versions: 1.9
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
> Labels: .NET
> Fix For: 1.9
>
>
> Create documentation and example for {{TransactionScope}} support
> (IGNITE-3430).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
[ https://issues.apache.org/jira/browse/IGNITE-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-3315: --- Assignee: Denis Magda (was: Prachi Garg) Completed review; Did minor fixes. > CPP: Add documentation for ContinuousQuery API > -- > > Key: IGNITE-3315 > URL: https://issues.apache.org/jira/browse/IGNITE-3315 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.6 >Reporter: Igor Sapego >Assignee: Denis Magda >Priority: Minor > Labels: cpp > Fix For: 1.9 > > > We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we > also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3422) No way to control object initialization during deserialization/unmarshalling
[
https://issues.apache.org/jira/browse/IGNITE-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876941#comment-15876941
]
Denis Magda commented on IGNITE-3422:
-
[~vozerov],
Presently I don't see demand for this feature however we did have it before. I
do remember we were discussing this feature with you and [~vkulichenko] some
time ago thinking of how would we support it.
In any case, I would have this feature especially if a half of it is already
done or we're following a right direction. As for .NET, it makes to take a look
at IGNITE-3102 and discuss the overall solution with [~ptupitsyn].
> No way to control object initialization during deserialization/unmarshalling
> -
>
> Key: IGNITE-3422
> URL: https://issues.apache.org/jira/browse/IGNITE-3422
> Project: Ignite
> Issue Type: Improvement
> Components: binary, general
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Presently there is no way to control instantiation of a {{BinaryObject}} that
> is being deserialized. The object is created using
> {{BinaryClassDescriptor#newInstance}} all the time.
> It makes sense to add {{BinaryConfiguration.setInitializationFactory()}}
> method that will provide with such support.
> Use case and details are provided in this discussion
> http://apache-ignite-users.70518.x6.nabble.com/Properly-Immutable-Keys-values-with-Binary-objects-tp6082.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876891#comment-15876891
]
Valentin Kulichenko commented on IGNITE-1903:
-
This is actually more generic issue. When a new node joins (client or server),
all existing cache configurations (which include cache stores) are sent to this
node. It then deserializes it during startup which can cause exceptions on
clients or servers where cache is not supposed to be deployed as defined by
node filter.
As a solution we can do the following:
* During discovery, send node filter and cache store factory in binary format
along with the cache configuration, not as its parts.
* On server, check node filter first and deserialize cache configuration and
cache store only if it returns true. In case of error, STOP join process (now
we just print exception in log and go on, which is very error-prone).
* On client, do not deserialize cache configuration and cache store until
user's code tries to actually use the cache (calls {{Ignite.cache}}. If cache
is ATOMIC, never deserialize the cache store.
> CacheStore implementation is serialised to grid clients whether they require
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Michael Griggs
> Labels: community
> Fix For: 2.0
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
> Brief summary: When a grid client joins the grid (clientMode=true) it
> receives a message from the server node(s) on the grid that contains the
> serialized CacheStore implementation object. If the client does not have
> this class on its CLASSPATH (and there is no reason it should, as it is a
> client) then the de-serialization of this message will fail, causing this
> exception:
> {code}SEVERE: Failed to unmarshal discovery data for component: 1
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all classes
> are available on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@14dad5dc
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
>
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
>
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException:
> c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite
> {code}
> where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
> implementation.
> The ostensible reason for the CacheStore serialization is so that clients of
> a TRANSACTIONAL cache can begin the transaction on the underlying store.
> The only current solution to this is to add the grid node's CacheStore
> implementation class definition to the CLASSPATH of the client. This creates
> an *undesirable coupling* between server and client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialized to nodes whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1903:
Summary: CacheStore implementation is serialized to nodes whether they
require it or not (was: CacheStore implementation is serialised to grid
clients whether they require it or not)
> CacheStore implementation is serialized to nodes whether they require it or
> not
> ---
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Michael Griggs
> Labels: community
> Fix For: 2.0
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
> Brief summary: When a grid client joins the grid (clientMode=true) it
> receives a message from the server node(s) on the grid that contains the
> serialized CacheStore implementation object. If the client does not have
> this class on its CLASSPATH (and there is no reason it should, as it is a
> client) then the de-serialization of this message will fail, causing this
> exception:
> {code}SEVERE: Failed to unmarshal discovery data for component: 1
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all classes
> are available on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@14dad5dc
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
>
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
>
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException:
> c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite
> {code}
> where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
> implementation.
> The ostensible reason for the CacheStore serialization is so that clients of
> a TRANSACTIONAL cache can begin the transaction on the underlying store.
> The only current solution to this is to add the grid node's CacheStore
> implementation class definition to the CLASSPATH of the client. This creates
> an *undesirable coupling* between server and client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not
[
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1903:
Priority: Major (was: Minor)
> CacheStore implementation is serialised to grid clients whether they require
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Michael Griggs
> Labels: community
> Fix For: 2.0
>
>
> See User discussion thread:
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
> Brief summary: When a grid client joins the grid (clientMode=true) it
> receives a message from the server node(s) on the grid that contains the
> serialized CacheStore implementation object. If the client does not have
> this class on its CLASSPATH (and there is no reason it should, as it is a
> client) then the de-serialization of this message will fail, causing this
> exception:
> {code}SEVERE: Failed to unmarshal discovery data for component: 1
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all classes
> are available on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@14dad5dc
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
>
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
>
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException:
> c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite
> {code}
> where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore
> implementation.
> The ostensible reason for the CacheStore serialization is so that clients of
> a TRANSACTIONAL cache can begin the transaction on the underlying store.
> The only current solution to this is to add the grid node's CacheStore
> implementation class definition to the CLASSPATH of the client. This creates
> an *undesirable coupling* between server and client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4617) CPP: Implement Field-access methods for binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876482#comment-15876482
]
Igor Sapego commented on IGNITE-4617:
-
Implemented discussed approach. Weirdly enough, requested schema is null on
Java side too. Going to dig deeper.
> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Labels: cpp
> Fix For: 2.0
>
>
> Currently we have very limited implementation of binary objects that does not
> provide access to fields of the binary object. At least such methods as
> {{HasField}} and {{GetField}} should be implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4720) Sporadically fails for Hadoop
[ https://issues.apache.org/jira/browse/IGNITE-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876456#comment-15876456 ] Ivan Veselovsky commented on IGNITE-4720: - Looks like problem caused by the following change: -- commit 30b869ddd32db637ee9ea8f13a115dd4bacc52fe Author: devozerov Date: Wed Dec 14 14:35:29 2016 +0300 IGNITE-4426: Hadoop: tasks can share the same classloader. This closes #1344. -- The following property allows to *work around* the problem: -Dignite.job.shared.classloader=false . > Sporadically fails for Hadoop > - > > Key: IGNITE-4720 > URL: https://issues.apache.org/jira/browse/IGNITE-4720 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: 1.8 >Reporter: Irina Zaporozhtseva >Assignee: Ivan Veselovsky > Fix For: 1.9 > > > hadoop example aggregatewordcount under apache ignite hadoop edition grid > with 4 nodes for hadoop-2_6_4 and hadoop-2_7_2: > aggregatewordcount returns 999712 instead of 100 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3710) Upgrade ignite-spark module to Spark 2.0
[
https://issues.apache.org/jira/browse/IGNITE-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876338#comment-15876338
]
Evgenii Zhuravlev commented on IGNITE-3710:
---
There was a problem with SharedRDDExample, so I moved it from java8 package to
a new spark package, that will be used only if scala or scala-2.10 profiles
turned on
> Upgrade ignite-spark module to Spark 2.0
>
>
> Key: IGNITE-3710
> URL: https://issues.apache.org/jira/browse/IGNITE-3710
> Project: Ignite
> Issue Type: Improvement
> Components: Ignite RDD
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 1.9
>
> Attachments: Ignite_Tests_Ignite_RDD_495.log
>
>
> Currently {{ignite-spark}} depends on Spark 1.5.2 and fails with 2.0 with
> this exception:
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/spark/Logging
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.ignite.spark.JavaIgniteContext.(JavaIgniteContext.scala:42)
> at client.SparkIgniteClient.main(SparkIgniteClient.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> Caused by: java.lang.ClassNotFoundException: org.apache.spark.Logging
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> {noformat}
> Need to investigate if we can upgrade without breaking compatibility with old
> versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-824) [Test] GridRandomSelfTest # testPerformance was disabled.
[ https://issues.apache.org/jira/browse/IGNITE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876246#comment-15876246 ] ASF GitHub Bot commented on IGNITE-824: --- GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/1566 IGNITE-824 Remove GridRandomSelfTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/SharplEr/ignite ignite-824 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1566.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 #1566 commit a25b1daeb2ccb29e7bc4b42712c8ea67a2c68649 Author: Alexander Menshikov Date: 2017-02-13T11:55:54Z Remove GridRandomSelfTest > [Test] GridRandomSelfTest # testPerformance was disabled. > - > > Key: IGNITE-824 > URL: https://issues.apache.org/jira/browse/IGNITE-824 > Project: Ignite > Issue Type: Bug > Components: yardstick >Reporter: Artem Shutak >Assignee: Alexander Menshikov > Labels: Muted_test > > GridRandomSelfTest # testPerformance was disabled. It has to be fixed or > removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
[
https://issues.apache.org/jira/browse/IGNITE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-4736.
Resolution: Fixed
> .NET: Remove swap API and cacheMemoryMode
> -
>
> Key: IGNITE-4736
> URL: https://issues.apache.org/jira/browse/IGNITE-4736
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
> branch {{ignite-3477}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
[
https://issues.apache.org/jira/browse/IGNITE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876178#comment-15876178
]
ASF GitHub Bot commented on IGNITE-4736:
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/1565
> .NET: Remove swap API and cacheMemoryMode
> -
>
> Key: IGNITE-4736
> URL: https://issues.apache.org/jira/browse/IGNITE-4736
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
> branch {{ignite-3477}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
[
https://issues.apache.org/jira/browse/IGNITE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876179#comment-15876179
]
Pavel Tupitsyn commented on IGNITE-4736:
Merged to {{ignite-3477}}
> .NET: Remove swap API and cacheMemoryMode
> -
>
> Key: IGNITE-4736
> URL: https://issues.apache.org/jira/browse/IGNITE-4736
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
> branch {{ignite-3477}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-1094) Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization
[ https://issues.apache.org/jira/browse/IGNITE-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-1094: Assignee: Alexey Kuznetsov > Ignite.createCache(CacheConfiguration) hangs if some exception occurs during > cache initialization > - > > Key: IGNITE-1094 > URL: https://issues.apache.org/jira/browse/IGNITE-1094 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-7 >Reporter: Sergey Evdokimov >Assignee: Alexey Kuznetsov > Labels: Muted_test > > User can pass broken configuration, for example, store factory that throws > exception from create() method. I created test to demonstrate the problem. > See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' > branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-1794:
-
Fix Version/s: (was: 1.9)
2.0
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Task
> Components: Hibernate L2 cache
>Reporter: Artem Shutak
>Assignee: Mykola Pereyma
> Labels: newbie
> Fix For: 2.0
>
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4626) GridDhtPartitionTopologyImpl refactoring
[ https://issues.apache.org/jira/browse/IGNITE-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876106#comment-15876106 ] Konstantin Dudkov commented on IGNITE-4626: --- [Code Review|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-101] > GridDhtPartitionTopologyImpl refactoring > > > Key: IGNITE-4626 > URL: https://issues.apache.org/jira/browse/IGNITE-4626 > Project: Ignite > Issue Type: Task >Reporter: Konstantin Dudkov >Assignee: Konstantin Dudkov > > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl#nodes(int, > org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion) > Need to refactor this method to use Object[] - partId->List -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4654) GridMarshallerPerformanceTest fail
[
https://issues.apache.org/jira/browse/IGNITE-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-4654:
-
Fix Version/s: 2.0
> GridMarshallerPerformanceTest fail
> --
>
> Key: IGNITE-4654
> URL: https://issues.apache.org/jira/browse/IGNITE-4654
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Stanilovsky Evgeny
>Priority: Minor
> Fix For: 2.0
>
>
> NPE fail
> {code}
> [13:46:49,678][INFO ][main][root] >>> Starting test class:
> GridMarshallerPerformanceTest <<<
> [13:46:49,688][INFO ][main][root] >>> Starting test:
> GridMarshallerPerformanceTest#testGridMarshaller <<<
> [13:46:49,694][ERROR][main][root] Test failed.
> class org.apache.ignite.internal.util.lang.GridClosureException: Failed to
> serialize object:
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$TestObject@d0bb6d5
> at
> org.apache.ignite.internal.util.lang.GridFunc.wrap(GridFunc.java:4582)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:41)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest.runTest(GridMarshallerPerformanceTest.java:236)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest.testGridMarshaller(GridMarshallerPerformanceTest.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> serialize object:
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$TestObject@d0bb6d5
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:197)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$3.applyx(GridMarshallerPerformanceTest.java:122)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$3.applyx(GridMarshallerPerformanceTest.java:120)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> ... 11 more
> Caused by: java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4415) .NET: EntityFramework 2nd level cache fails for some complex queries
[
https://issues.apache.org/jira/browse/IGNITE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876071#comment-15876071
]
Pavel Tupitsyn edited comment on IGNITE-4415 at 2/21/17 2:41 PM:
-
[~alexbchr] fix version was incorrectly set to 2.0. I've updated it and wiki
page now contains the ticket.
Code wise the fix is certainly in {{master}} and {{ignite-1.9}} branches:
https://github.com/apache/ignite/commit/781e5b7c93a1ee47299fc94519efbd0bea020940
was (Author: ptupitsyn):
[~alexbchr] fix version was incorrectly set to 2.0. I've updated it and wiki
page now contains the ticket.
> .NET: EntityFramework 2nd level cache fails for some complex queries
>
>
> Key: IGNITE-4415
> URL: https://issues.apache.org/jira/browse/IGNITE-4415
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> This EF query (sent by user) fails when EF caching is enabled:
> {code}
> var regionsAsm = user.GetAllChildRegions()
> .Where(w => w.RegionToRole.Any(a => a.RoleID ==
> (int)UserRoles.ASM));
>
> var allInvestTitle = user.RepositoryFactory.InvestTitle.All();
>
> var isFutureYear = filters.ActualYear.Value.Year >
>
> user.RepositoryFactory.Version.All().SingleOrDefault(w =>
> w.IsCurrent)?.ActualYear;
>
> var distributorToRegionAsmBindings = !isFutureYear
> ? regionsAsm.SelectMany(s => s.DistributorToRegionAsmBinding)
> : regionsAsm.SelectMany(s =>
> s.DistributorToRegionAsmBinding.Where(b => b.IsActual));
>
>
> var resultAllBudgets = distributorToRegionAsmBindings
> .Select(d => new { Distributor = d.Distributor, RegionAsm =
> d.Region, d })
> .SelectMany(dr => allInvestTitle, (dr, t) => new {
> dr.Distributor, dr.RegionAsm, InvestTitle = t, dr.d });
>
> var allBudgets = resultAllBudgets
> .Select(b => new BudgetResult
> {
> AsmRegionId = b.RegionAsm.ID,
> AsmRegionName = b.RegionAsm.Name,
> DistributorId = b.Distributor.ID,
> DistributorName = b.Distributor.Name,
> RsmRegionId = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.ParentRegionID)
> .FirstOrDefault(),
> RsmRegionName = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.Region1.Name)
> .FirstOrDefault(),
> InvestTitleId = b.InvestTitle.ID,
> InvestTitleName = b.InvestTitle.Name,
> });
>
> var result = allBudgets.ToList();
> {code}
> Error:
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Unexpected flag value
> [pos=43775, expected=12, actual=0]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlag(BinaryReaderExImpl.java:1403)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readByteArray(BinaryReaderExImpl.java:468)
> at
> org.apache.ignite.internal.processors.platform.entityframework.PlatformDotNetEntityFrameworkCacheExtension.processInOutStreamLong(PlatformDotNetEntityFrameworkCacheExtension.java:125)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:761)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutLong(PlatformAbstractTarget.java:78)
> {code}
> Generated SQL:
> {code}
> SELECT
> [Project17].[ID2] AS [ID],
> [Project17].[ID1] AS [ID1],
> [Project17].[Name1] AS [Name],
> [Project17].[ID] AS [ID2],
> [Project17].[Name] AS [Name1],
> CASE WHEN ([Project17].[C1] IS NULL) THEN 0 ELSE [Project17].[C2] END AS
> [C1],
> [Project17].[C3] AS [C2],
> [Project17].[Name2] AS [Name2]
> FROM ( SELECT
> [Project13].[ID] AS [ID],
> [Project13].[Name] AS [Name],
> [Project13].[ID1] AS [ID1],
> [Project13].[Name1] AS [Name1],
> [Project13].[ID2] AS [ID2],
> [Project13].[Name2] AS [Name2],
> [Project13].[C1] AS [C1],
> [Project13].[C2] AS [C2],
> (SELECT TOP (1)
> [Project14].[Name] AS [Name]
> FROM ( SELECT
[jira] [Commented] (IGNITE-4415) .NET: EntityFramework 2nd level cache fails for some complex queries
[
https://issues.apache.org/jira/browse/IGNITE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876071#comment-15876071
]
Pavel Tupitsyn commented on IGNITE-4415:
[~alexbchr] fix version was incorrectly set to 2.0. I've updated it and wiki
page now contains the ticket.
> .NET: EntityFramework 2nd level cache fails for some complex queries
>
>
> Key: IGNITE-4415
> URL: https://issues.apache.org/jira/browse/IGNITE-4415
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> This EF query (sent by user) fails when EF caching is enabled:
> {code}
> var regionsAsm = user.GetAllChildRegions()
> .Where(w => w.RegionToRole.Any(a => a.RoleID ==
> (int)UserRoles.ASM));
>
> var allInvestTitle = user.RepositoryFactory.InvestTitle.All();
>
> var isFutureYear = filters.ActualYear.Value.Year >
>
> user.RepositoryFactory.Version.All().SingleOrDefault(w =>
> w.IsCurrent)?.ActualYear;
>
> var distributorToRegionAsmBindings = !isFutureYear
> ? regionsAsm.SelectMany(s => s.DistributorToRegionAsmBinding)
> : regionsAsm.SelectMany(s =>
> s.DistributorToRegionAsmBinding.Where(b => b.IsActual));
>
>
> var resultAllBudgets = distributorToRegionAsmBindings
> .Select(d => new { Distributor = d.Distributor, RegionAsm =
> d.Region, d })
> .SelectMany(dr => allInvestTitle, (dr, t) => new {
> dr.Distributor, dr.RegionAsm, InvestTitle = t, dr.d });
>
> var allBudgets = resultAllBudgets
> .Select(b => new BudgetResult
> {
> AsmRegionId = b.RegionAsm.ID,
> AsmRegionName = b.RegionAsm.Name,
> DistributorId = b.Distributor.ID,
> DistributorName = b.Distributor.Name,
> RsmRegionId = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.ParentRegionID)
> .FirstOrDefault(),
> RsmRegionName = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.Region1.Name)
> .FirstOrDefault(),
> InvestTitleId = b.InvestTitle.ID,
> InvestTitleName = b.InvestTitle.Name,
> });
>
> var result = allBudgets.ToList();
> {code}
> Error:
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Unexpected flag value
> [pos=43775, expected=12, actual=0]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlag(BinaryReaderExImpl.java:1403)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readByteArray(BinaryReaderExImpl.java:468)
> at
> org.apache.ignite.internal.processors.platform.entityframework.PlatformDotNetEntityFrameworkCacheExtension.processInOutStreamLong(PlatformDotNetEntityFrameworkCacheExtension.java:125)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:761)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutLong(PlatformAbstractTarget.java:78)
> {code}
> Generated SQL:
> {code}
> SELECT
> [Project17].[ID2] AS [ID],
> [Project17].[ID1] AS [ID1],
> [Project17].[Name1] AS [Name],
> [Project17].[ID] AS [ID2],
> [Project17].[Name] AS [Name1],
> CASE WHEN ([Project17].[C1] IS NULL) THEN 0 ELSE [Project17].[C2] END AS
> [C1],
> [Project17].[C3] AS [C2],
> [Project17].[Name2] AS [Name2]
> FROM ( SELECT
> [Project13].[ID] AS [ID],
> [Project13].[Name] AS [Name],
> [Project13].[ID1] AS [ID1],
> [Project13].[Name1] AS [Name1],
> [Project13].[ID2] AS [ID2],
> [Project13].[Name2] AS [Name2],
> [Project13].[C1] AS [C1],
> [Project13].[C2] AS [C2],
> (SELECT TOP (1)
> [Project14].[Name] AS [Name]
> FROM ( SELECT
> [Extent14].[ParentRegionID] AS [ParentRegionID],
> [Extent15].[ID] AS [ID],
> [Extent15].[Name] AS [Name]
> FROM [dbo].[RegionExpand] AS [Extent14]
> INNER JOIN [dbo].[Region] AS [Extent15] ON
> [Extent14].[ParentRegionID] = [Extent15].[ID]
>
[jira] [Updated] (IGNITE-4415) .NET: EntityFramework 2nd level cache fails for some complex queries
[
https://issues.apache.org/jira/browse/IGNITE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4415:
---
Fix Version/s: (was: 2.0)
1.9
> .NET: EntityFramework 2nd level cache fails for some complex queries
>
>
> Key: IGNITE-4415
> URL: https://issues.apache.org/jira/browse/IGNITE-4415
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.9
>
>
> This EF query (sent by user) fails when EF caching is enabled:
> {code}
> var regionsAsm = user.GetAllChildRegions()
> .Where(w => w.RegionToRole.Any(a => a.RoleID ==
> (int)UserRoles.ASM));
>
> var allInvestTitle = user.RepositoryFactory.InvestTitle.All();
>
> var isFutureYear = filters.ActualYear.Value.Year >
>
> user.RepositoryFactory.Version.All().SingleOrDefault(w =>
> w.IsCurrent)?.ActualYear;
>
> var distributorToRegionAsmBindings = !isFutureYear
> ? regionsAsm.SelectMany(s => s.DistributorToRegionAsmBinding)
> : regionsAsm.SelectMany(s =>
> s.DistributorToRegionAsmBinding.Where(b => b.IsActual));
>
>
> var resultAllBudgets = distributorToRegionAsmBindings
> .Select(d => new { Distributor = d.Distributor, RegionAsm =
> d.Region, d })
> .SelectMany(dr => allInvestTitle, (dr, t) => new {
> dr.Distributor, dr.RegionAsm, InvestTitle = t, dr.d });
>
> var allBudgets = resultAllBudgets
> .Select(b => new BudgetResult
> {
> AsmRegionId = b.RegionAsm.ID,
> AsmRegionName = b.RegionAsm.Name,
> DistributorId = b.Distributor.ID,
> DistributorName = b.Distributor.Name,
> RsmRegionId = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.ParentRegionID)
> .FirstOrDefault(),
> RsmRegionName = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.Region1.Name)
> .FirstOrDefault(),
> InvestTitleId = b.InvestTitle.ID,
> InvestTitleName = b.InvestTitle.Name,
> });
>
> var result = allBudgets.ToList();
> {code}
> Error:
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Unexpected flag value
> [pos=43775, expected=12, actual=0]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlag(BinaryReaderExImpl.java:1403)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readByteArray(BinaryReaderExImpl.java:468)
> at
> org.apache.ignite.internal.processors.platform.entityframework.PlatformDotNetEntityFrameworkCacheExtension.processInOutStreamLong(PlatformDotNetEntityFrameworkCacheExtension.java:125)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:761)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutLong(PlatformAbstractTarget.java:78)
> {code}
> Generated SQL:
> {code}
> SELECT
> [Project17].[ID2] AS [ID],
> [Project17].[ID1] AS [ID1],
> [Project17].[Name1] AS [Name],
> [Project17].[ID] AS [ID2],
> [Project17].[Name] AS [Name1],
> CASE WHEN ([Project17].[C1] IS NULL) THEN 0 ELSE [Project17].[C2] END AS
> [C1],
> [Project17].[C3] AS [C2],
> [Project17].[Name2] AS [Name2]
> FROM ( SELECT
> [Project13].[ID] AS [ID],
> [Project13].[Name] AS [Name],
> [Project13].[ID1] AS [ID1],
> [Project13].[Name1] AS [Name1],
> [Project13].[ID2] AS [ID2],
> [Project13].[Name2] AS [Name2],
> [Project13].[C1] AS [C1],
> [Project13].[C2] AS [C2],
> (SELECT TOP (1)
> [Project14].[Name] AS [Name]
> FROM ( SELECT
> [Extent14].[ParentRegionID] AS [ParentRegionID],
> [Extent15].[ID] AS [ID],
> [Extent15].[Name] AS [Name]
> FROM [dbo].[RegionExpand] AS [Extent14]
> INNER JOIN [dbo].[Region] AS [Extent15] ON
> [Extent14].[ParentRegionID] = [Extent15].[ID]
> WHERE [Project13].[ID1] = [Extent14].[RegionID]
> ) AS [Project14]
> WHERE EXIS
[jira] [Commented] (IGNITE-3984) NullPointerException in IgniteCacheProxy when creating continuous query
[
https://issues.apache.org/jira/browse/IGNITE-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876065#comment-15876065
]
Alexey Kuznetsov commented on IGNITE-3984:
--
change status?
> NullPointerException in IgniteCacheProxy when creating continuous query
> ---
>
> Key: IGNITE-3984
> URL: https://issues.apache.org/jira/browse/IGNITE-3984
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Jason Man
> Attachments: ContQueryTest.java
>
>
> Test attached. This used to work fine in 1.6.
> {code}
> Exception in thread "main" javax.cache.CacheException:
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:709)
> at ContQueryTest.main(ContQueryTest.java:33)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.getOrCreatePartitionRecovery(CacheContinuousQueryHandler.java:835)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.waitTopologyFuture(CacheContinuousQueryHandler.java:543)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.executeQuery0(CacheContinuousQueryManager.java:660)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.executeQuery(CacheContinuousQueryManager.java:482)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.queryContinuous(IgniteCacheProxy.java:611)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:669)
> ... 6 more
> {code}
> This seem to be related to this jira and PR:
> https://issues.apache.org/jira/browse/IGNITE-3413
> https://github.com/apache/ignite/commit/89d64e74b697054a88c3a91433aaaf4f7fdd0284
> Here's the scenario:
> * First node starts with special attribute and creates a cache with the node
> filter that allows to deploy it only on nodes with this attribute
> * Second node starts without the attribute is started. When creating a
> continuous query to query the cache created by the first node, a
> NullPointerException is thrown.
> At first glance, it seems that because the NodeFilter prevented the
> GridContinuousProcessor.registerHandler() to be called , the
> ConcurrentMap rcvs is not initialized properly
> and NullPointerException is thrown on this line:
> {code}
> @NotNull private PartitionRecovery
> getOrCreatePartitionRecovery(GridKernalContext ctx, int partId) {
> PartitionRecovery rec = rcvs.get(partId);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4415) .NET: EntityFramework 2nd level cache fails for some complex queries
[
https://issues.apache.org/jira/browse/IGNITE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876061#comment-15876061
]
Alexandre Boucher commented on IGNITE-4415:
---
Any chances seeing this resolved in version 1.9 of Ignite?
I don't see this ticket referenced in 1.9 release
[tickets|https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+1.9],
even though you said it's fixed in master branch.
> .NET: EntityFramework 2nd level cache fails for some complex queries
>
>
> Key: IGNITE-4415
> URL: https://issues.apache.org/jira/browse/IGNITE-4415
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> This EF query (sent by user) fails when EF caching is enabled:
> {code}
> var regionsAsm = user.GetAllChildRegions()
> .Where(w => w.RegionToRole.Any(a => a.RoleID ==
> (int)UserRoles.ASM));
>
> var allInvestTitle = user.RepositoryFactory.InvestTitle.All();
>
> var isFutureYear = filters.ActualYear.Value.Year >
>
> user.RepositoryFactory.Version.All().SingleOrDefault(w =>
> w.IsCurrent)?.ActualYear;
>
> var distributorToRegionAsmBindings = !isFutureYear
> ? regionsAsm.SelectMany(s => s.DistributorToRegionAsmBinding)
> : regionsAsm.SelectMany(s =>
> s.DistributorToRegionAsmBinding.Where(b => b.IsActual));
>
>
> var resultAllBudgets = distributorToRegionAsmBindings
> .Select(d => new { Distributor = d.Distributor, RegionAsm =
> d.Region, d })
> .SelectMany(dr => allInvestTitle, (dr, t) => new {
> dr.Distributor, dr.RegionAsm, InvestTitle = t, dr.d });
>
> var allBudgets = resultAllBudgets
> .Select(b => new BudgetResult
> {
> AsmRegionId = b.RegionAsm.ID,
> AsmRegionName = b.RegionAsm.Name,
> DistributorId = b.Distributor.ID,
> DistributorName = b.Distributor.Name,
> RsmRegionId = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.ParentRegionID)
> .FirstOrDefault(),
> RsmRegionName = b.RegionAsm.RegionExpand
> .Where(w => w.Region1.RegionToRole.Any(a =>
> a.RoleID == (int) UserRoles.RSM))
> .Select(ss => ss.Region1.Name)
> .FirstOrDefault(),
> InvestTitleId = b.InvestTitle.ID,
> InvestTitleName = b.InvestTitle.Name,
> });
>
> var result = allBudgets.ToList();
> {code}
> Error:
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Unexpected flag value
> [pos=43775, expected=12, actual=0]
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlag(BinaryReaderExImpl.java:1403)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readByteArray(BinaryReaderExImpl.java:468)
> at
> org.apache.ignite.internal.processors.platform.entityframework.PlatformDotNetEntityFrameworkCacheExtension.processInOutStreamLong(PlatformDotNetEntityFrameworkCacheExtension.java:125)
> at
> org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:761)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutLong(PlatformAbstractTarget.java:78)
> {code}
> Generated SQL:
> {code}
> SELECT
> [Project17].[ID2] AS [ID],
> [Project17].[ID1] AS [ID1],
> [Project17].[Name1] AS [Name],
> [Project17].[ID] AS [ID2],
> [Project17].[Name] AS [Name1],
> CASE WHEN ([Project17].[C1] IS NULL) THEN 0 ELSE [Project17].[C2] END AS
> [C1],
> [Project17].[C3] AS [C2],
> [Project17].[Name2] AS [Name2]
> FROM ( SELECT
> [Project13].[ID] AS [ID],
> [Project13].[Name] AS [Name],
> [Project13].[ID1] AS [ID1],
> [Project13].[Name1] AS [Name1],
> [Project13].[ID2] AS [ID2],
> [Project13].[Name2] AS [Name2],
> [Project13].[C1] AS [C1],
> [Project13].[C2] AS [C2],
> (SELECT TOP (1)
> [Project14].[Name] AS [Name]
> FROM ( SELECT
> [Extent14].[ParentRegionID] AS [ParentRegionID],
> [Extent15].[ID] AS [ID],
> [Extent15].[Name] AS [Name]
> FROM [dbo].[RegionExpand
[jira] [Resolved] (IGNITE-768) Failed to start LOCAL cache on part of the grid
[
https://issues.apache.org/jira/browse/IGNITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov resolved IGNITE-768.
-
Resolution: Fixed
> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Attachments:
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException:
> Failed to start cache (a cache with the same name is already started):
> local-nid
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-768) Failed to start LOCAL cache on part of the grid
[
https://issues.apache.org/jira/browse/IGNITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-768:
---
Assignee: (was: Alexey Kuznetsov)
> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Attachments:
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException:
> Failed to start cache (a cache with the same name is already started):
> local-nid
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-768) Failed to start LOCAL cache on part of the grid
[
https://issues.apache.org/jira/browse/IGNITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-768.
---
> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Attachments:
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException:
> Failed to start cache (a cache with the same name is already started):
> local-nid
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (IGNITE-4737) Update Apache Flink dependencies to the latest version
Roman Shtykh created IGNITE-4737: Summary: Update Apache Flink dependencies to the latest version Key: IGNITE-4737 URL: https://issues.apache.org/jira/browse/IGNITE-4737 Project: Ignite Issue Type: Task Reporter: Roman Shtykh Assignee: Roman Shtykh Priority: Minor https://flink.apache.org/downloads.html#maven-dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
[
https://issues.apache.org/jira/browse/IGNITE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876027#comment-15876027
]
ASF GitHub Bot commented on IGNITE-4736:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1565
IGNITE-4736 .NET: Remove swap API and cacheMemoryMode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-3477-dotnet
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1565.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 #1565
commit b46288478519affee1006b8c9575f5dd710f65ab
Author: Pavel Tupitsyn
Date: 2017-02-21T12:57:58Z
.NET: Remove swap and cacheConfig.MemoryMode
commit a379a93a5315144d3c9e1c84e07516218fc92c71
Author: Pavel Tupitsyn
Date: 2017-02-21T12:59:37Z
Remove swap space remainings
commit 45633413604c54551efb197af392dd8375508935
Author: Pavel Tupitsyn
Date: 2017-02-21T13:01:32Z
wip swap
commit 8b7434ec2d788080d87b755a2728735076a295d8
Author: Pavel Tupitsyn
Date: 2017-02-21T13:05:34Z
cleanup
commit 7ce8232751855abf1eb00eb7ae1b0b02c2ff1019
Author: Pavel Tupitsyn
Date: 2017-02-21T13:07:03Z
cleanup
commit 8f4c02cbcad2ec10cacf7ac5cb4732615eb23018
Author: Pavel Tupitsyn
Date: 2017-02-21T13:09:37Z
more config cleanup
commit 375410908668806f5b86640e84799feb4cd91951
Author: Pavel Tupitsyn
Date: 2017-02-21T13:40:23Z
Disable CachePeekMode.Onheap
commit 3a4364bccc4457efd4acfe20c83dcb06ad9aa804
Author: Pavel Tupitsyn
Date: 2017-02-21T13:41:17Z
Remove swap peek mode
commit 19c1dd81d9817aeffdfb467c837b1835e0b87116
Author: Pavel Tupitsyn
Date: 2017-02-21T13:45:51Z
remap peek mode
commit 72fe341d6725c9a318a04e77444983d470e5c882
Author: Pavel Tupitsyn
Date: 2017-02-21T13:46:15Z
remove swap peek mode
commit 29a71f4c17fafcf195a08dee1fd5af40a253a204
Author: Pavel Tupitsyn
Date: 2017-02-21T13:51:52Z
wip
commit 39a89c522907b38ed0f1ad5d1b6603ba8bd31627
Author: Pavel Tupitsyn
Date: 2017-02-21T14:04:12Z
fix store tests
> .NET: Remove swap API and cacheMemoryMode
> -
>
> Key: IGNITE-4736
> URL: https://issues.apache.org/jira/browse/IGNITE-4736
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
> branch {{ignite-3477}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-4387) Incorrect Karaf OSGI feature for ignite-rest-http
[ https://issues.apache.org/jira/browse/IGNITE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4387: Assignee: Alexey Kuznetsov (was: Sergej Sidorov) > Incorrect Karaf OSGI feature for ignite-rest-http > - > > Key: IGNITE-4387 > URL: https://issues.apache.org/jira/browse/IGNITE-4387 > Project: Ignite > Issue Type: Bug > Components: osgi, rest >Affects Versions: 1.7 >Reporter: Sergej Sidorov >Assignee: Alexey Kuznetsov >Priority: Minor > > In accordance with the commit f177d4312c47 (IGNITE-3277 Replaced outdated > json-lib 2.4 to modern Jackson 2.7.5) dependencies in module ignite-rest-http > have been updated. But Karaf OSGI features config has not been updated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4284) Failed second client node join with continuous query and peer class loading enabled
[ https://issues.apache.org/jira/browse/IGNITE-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875984#comment-15875984 ] ASF GitHub Bot commented on IGNITE-4284: GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/1564 IGNITE-4284 You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite IGNITE-4284 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1564.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 #1564 commit bca9756cc4fbe3e89fbc29453d94619d2f90c95b Author: NSAmelchev Date: 2017-02-07T14:04:02Z Merge remote-tracking branch 'refs/remotes/apache/master' commit b676ee8bef440447968372ffd56bcf644bfa7175 Author: NSAmelchev Date: 2017-01-27T14:56:12Z Add test Second client node join with continuous query and peer class loading enabled commit 1e1846b681080bf1af29968e552662fbaebb5e66 Author: NSAmelchev Date: 2017-01-27T15:04:07Z Return null for event filter when remote filter factori is null Fix by returning null for event filter if remote filter factory is null. commit e90b78aacdc5175a56783c89e60f6e9c5800fd27 Author: NSAmelchev Date: 2017-02-20T17:14:48Z Add Nullable annotation commit 9266321939112fe39fba237bf7cd6b6d34213a9e Author: NSAmelchev Date: 2017-02-21T10:00:17Z Add test to suite commit 01d447c00a44becafffcd5bac8279512a30629e7 Author: NSAmelchev Date: 2017-02-21T13:44:07Z Merge remote-tracking branch 'apache/master' into IGNITE-4284 # Conflicts: # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite3.java > Failed second client node join with continuous query and peer class loading > enabled > --- > > Key: IGNITE-4284 > URL: https://issues.apache.org/jira/browse/IGNITE-4284 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.7 >Reporter: Dmitry Karachentsev >Assignee: Amelchev Nikita > Fix For: 2.0 > > > Steps to reproduce: > 1) Start server with cache and peer class loading enabled. > 2) Start client with peer class loading enabled. > 3) Start continuous query with custom event filter factory. > 4) Start second client -- Fail with NPE or AsserionError. > Test that reproduces error: > [PR#1267|https://github.com/apache/ignite/pull/1267] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
[
https://issues.apache.org/jira/browse/IGNITE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4736:
---
Description:
Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
branch {{ignite-3477}}
was:Swap space and cacheMemoryMode have been removed in Java. Do the same in
.NET
> .NET: Remove swap API and cacheMemoryMode
> -
>
> Key: IGNITE-4736
> URL: https://issues.apache.org/jira/browse/IGNITE-4736
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET
> branch {{ignite-3477}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1264. -- Resolution: Fixed > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1264. > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reopened IGNITE-1264: -- > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-1264. > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1264. -- Resolution: Fixed > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-1264: Assignee: (was: Alexey Kuznetsov) > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4372) Set up code coverage reports
[ https://issues.apache.org/jira/browse/IGNITE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875949#comment-15875949 ] ASF GitHub Bot commented on IGNITE-4372: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1560 > Set up code coverage reports > > > Key: IGNITE-4372 > URL: https://issues.apache.org/jira/browse/IGNITE-4372 > Project: Ignite > Issue Type: Improvement >Reporter: Ksenia Rybakova >Assignee: Ksenia Rybakova > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4736) .NET: Remove swap API and cacheMemoryMode
Pavel Tupitsyn created IGNITE-4736: -- Summary: .NET: Remove swap API and cacheMemoryMode Key: IGNITE-4736 URL: https://issues.apache.org/jira/browse/IGNITE-4736 Project: Ignite Issue Type: Sub-task Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.0 Swap space and cacheMemoryMode have been removed in Java. Do the same in .NET -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4734) Sporadic GridServiceNotFoundException in ServiceExample
[
https://issues.apache.org/jira/browse/IGNITE-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875928#comment-15875928
]
Dmitriy Govorukhin edited comment on IGNITE-4734 at 2/21/17 1:11 PM:
-
i think i know what the problem. We have race between creation context and
inject service in context. Context create and put in to context map (context
avalible for receipt) but service not inject in context. i think we must
discuss it, because if we change it, changed public api behavior.
was (Author: dmitriygovorukhin):
i think i know what the problem. We have race between creation context and
inject service in context. Context create and put it to context map (context
avalible for receipt) but service not inject in context. i think we must
discuss it, because if we change it, changed public api behavior.
> Sporadic GridServiceNotFoundException in ServiceExample
> ---
>
> Key: IGNITE-4734
> URL: https://issues.apache.org/jira/browse/IGNITE-4734
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ksenia Rybakova
>
> Sometimes ServiceExample thows GridServiceNotFoundException
> Configs might be different - 1 node/3 nodes, linux/windows
> Driver node log:
> {noformat}
> [10:50:31,428][INFO][main][GridDiscoveryManager] Topology snapshot [ver=2,
> servers=1, clients=1, CPUs=4, heap=2.0GB]
> >>>
> >>> Starting service proxy example.
> >>>
> [10:50:31,768][SEVERE][sys-#32%null%][GridTaskWorker] Failed to obtain remote
> job result policy for result from ComputeTask.result(..) method (will fail
> the whole task): GridJobResultImpl [job=C2V2 [c=ServiceProxyCallable
> [mtdName=put, svcName=myNodeSingletonService, ignite=null]],
> sib=GridJobSiblingImpl
> [sesId=b2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
> jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
> nodeId=01aea3a3-0981-4760-a26b-732afc4a8a27, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d, timeoutObj=null,
> attrs={}], node=TcpDiscoveryNode [id=01aea3a3-0981-4760-a26b-732afc4a8a27,
> addrs=[127.0.0.1, 172.25.2.17], sockAddrs=[/172.25.2.17:47500,
> /127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1487663430926, loc=false, ver=1.7.8#20170220-sha1:6112bce9,
> isClient=false], ex=class o.a.i.IgniteException: Service not found:
> myNodeSingletonService, hasRes=true, isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception
> (override or implement ComputeTask.result(..) method if you would like to
> have automatic failover for this exception).
> at
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1031)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1024)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1024)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:842)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Service not found:
> myNodeSingletonService
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2059)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:560)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:554
[jira] [Commented] (IGNITE-4734) Sporadic GridServiceNotFoundException in ServiceExample
[
https://issues.apache.org/jira/browse/IGNITE-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875928#comment-15875928
]
Dmitriy Govorukhin commented on IGNITE-4734:
i think i know what the problem. We have race between creation context and
inject service in context. Context create and put it to context map (context
avalible for receipt) but service not inject in context. i think we must
discuss it, because if we change it, changed public api behavior.
> Sporadic GridServiceNotFoundException in ServiceExample
> ---
>
> Key: IGNITE-4734
> URL: https://issues.apache.org/jira/browse/IGNITE-4734
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ksenia Rybakova
>
> Sometimes ServiceExample thows GridServiceNotFoundException
> Configs might be different - 1 node/3 nodes, linux/windows
> Driver node log:
> {noformat}
> [10:50:31,428][INFO][main][GridDiscoveryManager] Topology snapshot [ver=2,
> servers=1, clients=1, CPUs=4, heap=2.0GB]
> >>>
> >>> Starting service proxy example.
> >>>
> [10:50:31,768][SEVERE][sys-#32%null%][GridTaskWorker] Failed to obtain remote
> job result policy for result from ComputeTask.result(..) method (will fail
> the whole task): GridJobResultImpl [job=C2V2 [c=ServiceProxyCallable
> [mtdName=put, svcName=myNodeSingletonService, ignite=null]],
> sib=GridJobSiblingImpl
> [sesId=b2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
> jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
> nodeId=01aea3a3-0981-4760-a26b-732afc4a8a27, isJobDone=false],
> jobCtx=GridJobContextImpl
> [jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d, timeoutObj=null,
> attrs={}], node=TcpDiscoveryNode [id=01aea3a3-0981-4760-a26b-732afc4a8a27,
> addrs=[127.0.0.1, 172.25.2.17], sockAddrs=[/172.25.2.17:47500,
> /127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1487663430926, loc=false, ver=1.7.8#20170220-sha1:6112bce9,
> isClient=false], ex=class o.a.i.IgniteException: Service not found:
> myNodeSingletonService, hasRes=true, isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception
> (override or implement ComputeTask.result(..) method if you would like to
> have automatic failover for this exception).
> at
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1031)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1024)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1024)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:842)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Service not found:
> myNodeSingletonService
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2059)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:560)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:554)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
> at
> org.apache.ignite.internal.processors.job.GridJob
[jira] [Commented] (IGNITE-4733) Remove unused methods from GridFunc
[ https://issues.apache.org/jira/browse/IGNITE-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875923#comment-15875923 ] ASF GitHub Bot commented on IGNITE-4733: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/1563 IGNITE-4733 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4733 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1563.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 #1563 commit c893da70a9757b16b0799adc8eaa29fa1b03d06e Author: tledkov-gridgain Date: 2016-12-21T11:54:33Z IGNITE-4399: IGFS: Merged IgfsSecondaryFileSystem and IgfsSecondaryFileSystemV2 interfaces. This closes #1346. commit c5882a85f4e3a1f61723ac54fd92f087684df6da Author: devozerov Date: 2016-12-26T11:15:42Z Merge branch 'master' into ignite-2.0 commit 7e73d0223a3f09cbe0b7094a2c04bdf9d63ca9be Author: devozerov Date: 2016-12-28T09:54:47Z Merge branch 'master' into ignite-2.0 commit 7d82d6a06b5e9f1f8cd2909b865e37d46b8da03f Author: devozerov Date: 2016-12-28T09:58:11Z IGNITE-3875: Introduced separate thread pool for data streamer. This closes #1173. This closes #1383. commit a61b0eaff1817d84c0659e8a7e095f29e22800e1 Author: tledkov-gridgain Date: 2016-12-28T11:09:38Z IGNITE-4405: Hadoop: implemented "readLine" method for HadoopDataInStream and HadoopDirectDataInput classes. This closes #1358. commit 2df39a80d80e2575be61a902ccd48615796fcde9 Author: tledkov-gridgain Date: 2016-12-28T13:47:24Z IGNITE-3961: IGFS: Added IgfsSecondaryFileSystem.affintiy() method. This closes #1114. This closes #1252. commit 2e691d80ea4870c3e7b5b127792b66c920f72c39 Author: tledkov-gridgain Date: 2016-12-29T08:00:01Z IGNITE-4462: IGFS: removed grid name from HadoopIgfsEndpoint. This closes #1368. commit a9b1fc2b3840d47d7c978d9296e8ae6bdeb10be5 Author: tledkov-gridgain Date: 2016-12-29T08:07:22Z IGNITE-4459: Hadoop: weighted planned is default one from now on. This closes #1391. commit 1f743465d6875ef48b1835d03a78a0dbaf339bf6 Author: tledkov-gridgain Date: 2016-12-29T08:14:10Z IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This closes #1390. commit 6090ebdfcd0ea3840b0d32cb10197b43615e1e89 Author: devozerov Date: 2017-01-05T09:23:06Z Merge branch 'master' into ignite-2.0 commit 77ca2e636c73e464f833f227c4894df0785ae9e2 Author: devozerov Date: 2017-01-16T13:07:49Z Merge branch 'master' into ignite-2.0 commit d14e0727b3dd61ab5ec2957133d77dbc25e9ba68 Author: tledkov-gridgain Date: 2017-01-16T13:36:25Z IGNITE-4428: Hadoop: moved HadoopMapReducePlanner and dependent classes to public space. This closes #1389. This closes #1394. commit f1365421c299b754a10edf8b6f156aeeb5ff0ce1 Author: tledkov-gridgain Date: 2017-01-16T13:57:27Z IGNITE-4503: Hadoop: added boundary checks to HadoopDirectDataInput. This closes # 1416. commit e08b6ff48916edfab2dbd5d62092be5a1f819a2f Author: Pavel Tupitsyn Date: 2017-01-19T10:34:59Z Merge branch 'master' into ignite-2.0 commit 43adf8a3f09c6b29fe3e70f62dbc58251d8d7cb9 Author: Ivan Veselovskiy Date: 2017-01-19T11:34:23Z IGNITE-4219: Hadoop: fixed serialization of long strings. This closes #1409. commit 454b9769e72775c5f6b44a36f0eef84bcce13bd7 Author: devozerov Date: 2017-01-19T11:34:43Z Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0 commit 4cd332b781cf700b99402eed2363f988f6403602 Author: Sergey Chugunov Date: 2017-01-19T12:05:09Z IGNITE-4157 Use discovery custom messages instead of marshaller cache - Fixes #1271. Signed-off-by: Alexey Goncharuk commit d0a6c57aa26bca64ef68370c0ebdb5ce45bcc765 Author: Pavel Tupitsyn Date: 2017-01-19T14:10:41Z IGNITE-4441 Define plugin API in .NET This closes #1362 commit 34a97833905a33bdb31b8e4580a576c2142313a7 Author: Alexey Goncharuk Date: 2017-01-19T15:04:23Z IGNITE-4157 - Added mapping update listener stub commit e8377167b7b8dd020a93d92c743e4541dcd000ed Author: Pavel Tupitsyn Date: 2017-01-20T10:00:40Z Merge branch 'master' into ignite-2.0 commit 38cb67d45eb91e20ad4b92a490747534f5e8febb Author: Pavel Tupitsyn Date: 2017-01-20T13:09:57Z Merge branch 'master' into ignite-2.0 commit 82857d0cb6e2984a5359b822a9c903874414aa67 Author: Pavel Tupitsyn Date: 2017-01-23T10:12:12Z Merge branch 'master' into ignite-2.0 # Conflicts: # modules/hadoop/src/main/java/org/apache/ignite/internal/processors/hadoop/impl/v1/HadoopV1MapTask.java # modules/hadoop/src/main/java/org/apache/ignite/internal/processors/hadoop/impl/v1/HadoopV1ReduceTask.jav
[jira] [Commented] (IGNITE-4735) Some CPP files are missing from source releases.
[ https://issues.apache.org/jira/browse/IGNITE-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875918#comment-15875918 ] ASF GitHub Bot commented on IGNITE-4735: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1562 IGNITE-4735: Excluded CPP sources. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4735 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1562.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 #1562 commit 1c3e602032df72c844e44cc1eb6224b54d9e8712 Author: Igor Sapego Date: 2017-02-21T12:44:30Z IGNITE-4735: Excluded CPP sources. > Some CPP files are missing from source releases. > > > Key: IGNITE-4735 > URL: https://issues.apache.org/jira/browse/IGNITE-4735 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 1.8 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: cpp > Fix For: 1.9 > > > Some CPP files missing from the sources release. For example: > - modules/platforms/cpp/common/project/vs/targetver.h > - modules/platforms/cpp/jni/project/vs/targetver.h > - modules/platforms/cpp/core/include/ignite/impl/interop/interop_target.h > It seems that there is issue with files which has "target" in name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4735) Some CPP files are missing from source releases.
Igor Sapego created IGNITE-4735: --- Summary: Some CPP files are missing from source releases. Key: IGNITE-4735 URL: https://issues.apache.org/jira/browse/IGNITE-4735 Project: Ignite Issue Type: Bug Components: build Affects Versions: 1.8 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.9 Some CPP files missing from the sources release. For example: - modules/platforms/cpp/common/project/vs/targetver.h - modules/platforms/cpp/jni/project/vs/targetver.h - modules/platforms/cpp/core/include/ignite/impl/interop/interop_target.h It seems that there is issue with files which has "target" in name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4734) Sporadic GridServiceNotFoundException in ServiceExample
Ksenia Rybakova created IGNITE-4734:
---
Summary: Sporadic GridServiceNotFoundException in ServiceExample
Key: IGNITE-4734
URL: https://issues.apache.org/jira/browse/IGNITE-4734
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Ksenia Rybakova
Sometimes ServiceExample thows GridServiceNotFoundException
Configs might be different - 1 node/3 nodes, linux/windows
Driver node log:
{noformat}
[10:50:31,428][INFO][main][GridDiscoveryManager] Topology snapshot [ver=2,
servers=1, clients=1, CPUs=4, heap=2.0GB]
>>>
>>> Starting service proxy example.
>>>
[10:50:31,768][SEVERE][sys-#32%null%][GridTaskWorker] Failed to obtain remote
job result policy for result from ComputeTask.result(..) method (will fail the
whole task): GridJobResultImpl [job=C2V2 [c=ServiceProxyCallable [mtdName=put,
svcName=myNodeSingletonService, ignite=null]], sib=GridJobSiblingImpl
[sesId=b2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d,
nodeId=01aea3a3-0981-4760-a26b-732afc4a8a27, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=d2c66af5a51-87f5f92a-d9ee-4119-90a5-35659bd7e50d, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=01aea3a3-0981-4760-a26b-732afc4a8a27,
addrs=[127.0.0.1, 172.25.2.17], sockAddrs=[/172.25.2.17:47500,
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1487663430926, loc=false, ver=1.7.8#20170220-sha1:6112bce9,
isClient=false], ex=class o.a.i.IgniteException: Service not found:
myNodeSingletonService, hasRes=true, isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would like to have
automatic failover for this exception).
at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1031)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1024)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1024)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:842)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Service not found:
myNodeSingletonService
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2059)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:560)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:554)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
... 7 more
Caused by: class
org.apache.ignite.internal.processors.service.GridServiceNotFoundException:
Service not found: myNodeSingletonService
at
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:397)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2056)
... 14 more
Map service size: 10
>>>
>>> Starting service injection example.
>>>
[10:50:31,905][INFO][main][GridDeploymentLocalStore] Class locally dep
[jira] [Commented] (IGNITE-4729) Async operation support in platform plugins
[
https://issues.apache.org/jira/browse/IGNITE-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875898#comment-15875898
]
Pavel Tupitsyn commented on IGNITE-4729:
{{DoOutOpAsync}} added which maps to {{PlatformTarget.processInStreamAsync}}
> Async operation support in platform plugins
> ---
>
> Key: IGNITE-4729
> URL: https://issues.apache.org/jira/browse/IGNITE-4729
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Expose a set of async operations on {{IPlatformTarget}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-768) Failed to start LOCAL cache on part of the grid
[
https://issues.apache.org/jira/browse/IGNITE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-768:
---
Assignee: Alexey Kuznetsov
> Failed to start LOCAL cache on part of the grid
> ---
>
> Key: IGNITE-768
> URL: https://issues.apache.org/jira/browse/IGNITE-768
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Attachments:
> 0001-IGNITE-768-Test-for-LOCAL-cache-on-isolated-nodes.patch
>
>
> Steps to reproduce.
> # Start first node.
> # Start LOCAL cache "A" on first node (with node filter by node ID).
> # Start second node.
> # Start LOCAL cache "A" on second node (with node filter by node ID).
> Got exception:
> {code}
> Exception in thread "main" org.apache.ignite.cache.CacheExistsException:
> Failed to start cache (a cache with the same name is already started):
> local-nid
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1858)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.dynamicStartCache(GridCacheProcessor.java:1827)
> at
> org.apache.ignite.internal.IgniteKernal.createCache(IgniteKernal.java:2258)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-1837) Rebalancing on a big cluster (30 nodes and more)
[ https://issues.apache.org/jira/browse/IGNITE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-1837. -- Resolution: Won't Fix Assignee: (was: Semen Boikov) There were implemented several optimizations in discovery, affinity calculation and exchange processing (e.g. IGNITE-4296), after this suggested optimization does not make sense. > Rebalancing on a big cluster (30 nodes and more) > > > Key: IGNITE-1837 > URL: https://issues.apache.org/jira/browse/IGNITE-1837 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: ignite-1.4 >Reporter: Denis Magda > > It seems that Ignite has different rebalancing related issues that appear > when a big cluster is started. > Under the big cluster I mean: > - cluster of 64 server nodes; > - cluster of 64 server and 64 client nodes. > The issues can be divided on three main use cases. > 1) Slow rebalancing on start. > - If to set partitions number for some cache to value bigger than default one > (to 3200 or to 6400, etc.) then rebalancing of such caches may take several > minutes. The caches are empty at that time. In addition, as a part of this > issue let's document that the number of partitions can't exceed some value. > - exchange message on NODE_JOINED event that times out for a long time. > Discussed there: > http://apache-ignite-users.70518.x6.nabble.com/Help-with-tuning-for-larger-clusters-td1692.html#a1813 > 2) Slow rebalancing on client nodes shutdown. > If to stop a significant number of client nodes at the same time then again > by some reason the rebalancing will take serveral minutes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4729) Async operation support in platform plugins
[
https://issues.apache.org/jira/browse/IGNITE-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875837#comment-15875837
]
ASF GitHub Bot commented on IGNITE-4729:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1561
IGNITE-4729 Async operation support in platform plugins
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4729
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1561.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 #1561
commit e9b63445fce527baf5835227fd1414a8e2f7fbd9
Author: Pavel Tupitsyn
Date: 2017-02-21T11:34:26Z
IGNITE-4729 Async operation support in platform plugins
> Async operation support in platform plugins
> ---
>
> Key: IGNITE-4729
> URL: https://issues.apache.org/jira/browse/IGNITE-4729
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> Expose a set of async operations on {{IPlatformTarget}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (IGNITE-2933) Deprecate GridFunc class.
[ https://issues.apache.org/jira/browse/IGNITE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-2933. - Resolution: Won't Fix > Deprecate GridFunc class. > - > > Key: IGNITE-2933 > URL: https://issues.apache.org/jira/browse/IGNITE-2933 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4733) Remove unused methods from GridFunc
Vladimir Ozerov created IGNITE-4733: --- Summary: Remove unused methods from GridFunc Key: IGNITE-4733 URL: https://issues.apache.org/jira/browse/IGNITE-4733 Project: Ignite Issue Type: Task Components: general Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Minor Fix For: 2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-2933) Deprecate GridFunc class.
[ https://issues.apache.org/jira/browse/IGNITE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-2933. --- > Deprecate GridFunc class. > - > > Key: IGNITE-2933 > URL: https://issues.apache.org/jira/browse/IGNITE-2933 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (IGNITE-2935) GridFunc: Identify safe methods and move them to a new class.
[
https://issues.apache.org/jira/browse/IGNITE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-2935.
-
Resolution: Won't Fix
> GridFunc: Identify safe methods and move them to a new class.
> -
>
> Key: IGNITE-2935
> URL: https://issues.apache.org/jira/browse/IGNITE-2935
> Project: Ignite
> Issue Type: Sub-task
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> 1) Create new class. E.g. {{LangUtils}}.
> 2) Move all non-deprecated methods to it.
> 3) Replace all usages of deprecated methods from "F." to "GridFunc."
> 4) Remove unsafe methods.
> 5) Change {{F}} class to extend {{LangUtils}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (IGNITE-2935) GridFunc: Identify safe methods and move them to a new class.
[
https://issues.apache.org/jira/browse/IGNITE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-2935.
---
> GridFunc: Identify safe methods and move them to a new class.
> -
>
> Key: IGNITE-2935
> URL: https://issues.apache.org/jira/browse/IGNITE-2935
> Project: Ignite
> Issue Type: Sub-task
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> 1) Create new class. E.g. {{LangUtils}}.
> 2) Move all non-deprecated methods to it.
> 3) Replace all usages of deprecated methods from "F." to "GridFunc."
> 4) Remove unsafe methods.
> 5) Change {{F}} class to extend {{LangUtils}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4372) Set up code coverage reports
[ https://issues.apache.org/jira/browse/IGNITE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875790#comment-15875790 ] ASF GitHub Bot commented on IGNITE-4372: GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1560 IGNITE-4372 Ids quoting fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4732 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1560.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 #1560 commit 14290d3fe44af7e2269d42361f2bb1207b0ee8c3 Author: Alexander Paschenko Date: 2017-02-21T11:00:45Z IGNITE-4372 Ids quoting fix > Set up code coverage reports > > > Key: IGNITE-4372 > URL: https://issues.apache.org/jira/browse/IGNITE-4372 > Project: Ignite > Issue Type: Improvement >Reporter: Ksenia Rybakova >Assignee: Ksenia Rybakova > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4732) Invalid ids quoting logic in DML and GridSqlFunction
Alexander Paschenko created IGNITE-4732: --- Summary: Invalid ids quoting logic in DML and GridSqlFunction Key: IGNITE-4732 URL: https://issues.apache.org/jira/browse/IGNITE-4732 Project: Ignite Issue Type: Bug Components: SQL Affects Versions: 1.9 Reporter: Alexander Paschenko Assignee: Alexander Paschenko Fix For: 1.9 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4404) GridCacheOffHeapMultiThreadedUpdateAbstractSelfTest long running test refactoring
[ https://issues.apache.org/jira/browse/IGNITE-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-4404: -- Assignee: Ryabov Dmitrii > GridCacheOffHeapMultiThreadedUpdateAbstractSelfTest long running test > refactoring > - > > Key: IGNITE-4404 > URL: https://issues.apache.org/jira/browse/IGNITE-4404 > Project: Ignite > Issue Type: Test >Reporter: Konstantin Dudkov >Assignee: Ryabov Dmitrii > > in testTransform > final int THREADS = 5; > final int ITERATIONS_PER_THREAD = 10_000; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities
[
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874652#comment-15874652
]
Taras Ledkov edited comment on IGNITE-3469 at 2/21/17 10:28 AM:
h3. The list of the deprecated public class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- {{IgniteSpiContext}}: methods {{addMessageListener, removeMessageListener}};
- {{TcpCommunicationSpi}} properties:
-- {{connectionBufferSize}};
-- {{connectionBufferFlushFrequency}};
-- {{minimumBufferedMessageCount}};
- {{StreamTupleExtractor}} class and relations;
- ignite-hadoop: Several constructors of the
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.
h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- {{GridDhtPartitionDemander}}: {{demandLock, dmIdx, worker, SupplyMessage,
DemandWorker}};
- One of the constructors of the {{GridDhtPartitionFullMap}};
- {{GridDhtPartitionMap}};
- {{GridDhtPartitionSupplier}} old listeners & old demand message;
- {{AffinityTask.affinityKey()}}
- {{GridQueryRequest}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{GridTupleV}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};
was (Author: tledkov-gridgain):
h3. The list of the deprecated public class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- {{IgniteSpiContext}}: methods {{addMessageListener, removeMessageListener}};
- {{TcpCommunicationSp
[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities
[
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874652#comment-15874652
]
Taras Ledkov edited comment on IGNITE-3469 at 2/21/17 10:26 AM:
h3. The list of the deprecated public class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- {{IgniteSpiContext}}: methods {{addMessageListener, removeMessageListener}};
- {{TcpCommunicationSpi}} properties:
-- {{connectionBufferSize}};
-- {{connectionBufferFlushFrequency}};
-- {{minimumBufferedMessageCount}};
- {{StreamTupleExtractor}} class and relations;
h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- {{GridDhtPartitionDemander}}: {{demandLock, dmIdx, worker, SupplyMessage,
DemandWorker}};
- One of the constructors of the {{GridDhtPartitionFullMap}};
- {{GridDhtPartitionMap}};
- {{GridDhtPartitionSupplier}} old listeners & old demand message;
- {{AffinityTask.affinityKey()}}
- {{GridQueryRequest}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{GridTupleV}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};
-
was (Author: tledkov-gridgain):
The list of the deprecated public class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- {{IgniteSpiContext}}: methods {{addMessageListener, removeMessageListener}};
- {{TcpCommunicationSpi}} properties:
-- {{connectionBufferSize}};
-- {{connectionBufferFlushFrequency}};
-- {{minimumBufferedMessageCount}};
- {{StreamTupleExtracto
[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities
[
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874652#comment-15874652
]
Taras Ledkov edited comment on IGNITE-3469 at 2/21/17 10:25 AM:
The list of the deprecated public class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- {{IgniteSpiContext}}: methods {{addMessageListener, removeMessageListener}};
- {{TcpCommunicationSpi}} properties:
-- {{connectionBufferSize}};
-- {{connectionBufferFlushFrequency}};
-- {{minimumBufferedMessageCount}};
- {{StreamTupleExtractor}} class and relations;
The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- {{GridDhtPartitionDemander}}: {{demandLock, dmIdx, worker, SupplyMessage,
DemandWorker}};
- One of the constructors of the {{GridDhtPartitionFullMap}};
- {{GridDhtPartitionMap}};
- {{GridDhtPartitionSupplier}} old listeners & old demand message;
- {{AffinityTask.affinityKey()}}
- {{GridQueryRequest}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{GridTupleV}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};
-
was (Author: tledkov-gridgain):
The list of the deprecated class / methods / properties:
- two methods {{IgniteCluster.mapKeyToNode}} - the removing is simple because
its are used rare;
- {{IgniteCache.randomEntry}} - the removing is simple because it is used rare;
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- {{CacheTypeMetadata}};
- Classes related with {{AffinityNodeHashResolver}};
- Backup filters for affinity functions;
- {{RandomEvictionPolicy}};
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{transactionManagerLookupClassName}} and
{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{FileSystemConfiguration}} properties:
-- {{fragmentizerLocalWritesRatio}};
-- {{trashPurgeTimeout}};
-- {{dualModePutExecutorService}};
-- {{dualModePutExecutorServiceShutdown}};
-- {{dualModeMaxPendingPutsSize}};
- {{IgniteConfiguration}} properties:
-- {{nodeId}};
-- {{DFLT_PUBLIC_KEEP_ALIVE_TIME}};
-- {{DFLT_PUBLIC_THREADPOOL_QUEUE_CAP}};
-- {{DFLT_SYSTEM_MAX_THREAD_CNT}};
-- {{DFLT_SYSTEM_KEEP_ALIVE_TIME}};
-- {{DFLT_UTILITY_KEEP_ALIVE_TIME}};
-- {{DFLT_SYSTEM_THREADPOOL_QUEUE_CAP}};
- {{TransactionConfiguration}} properties:
-- {{txSerializableEnabled}};
-- {{txManagerLookupClassName}};
- Several methods at the {{IgfsPath}} class: empty constructor, {{root()}} and
{{isSame}} methods;
- Classes are retated to the {{GridSslContextFactory}};
-
> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
>
[jira] [Comment Edited] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory
[
https://issues.apache.org/jira/browse/IGNITE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875716#comment-15875716
]
Igor Seliverstov edited comment on IGNITE-4694 at 2/21/17 10:13 AM:
I've created two test suits:
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
But I cannot add them into the TeamCity project
Seems there is a lack of permissions
was (Author: gvvinblade):
I've created two test suits:
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
But I cannot add them into the TeamCity priject
Seems there is a lack of permissions
> Add tests to check there are no memory leaks in PageMemory
> --
>
> Key: IGNITE-4694
> URL: https://issues.apache.org/jira/browse/IGNITE-4694
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
>
> Need add several tests running for 5-10 munites verifying there are no memory
> leaks in new data structures based of PageMemory:
> - test various page size
> - test various objects size
> - test put/get/remove operations
> - test create cache/destroy cache operations
> - test cases when indexes enabled/disabled
> - test case when cache expiry policy is used
> New tests should be added in new test suite.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (IGNITE-4694) Add tests to check there are no memory leaks in PageMemory
[
https://issues.apache.org/jira/browse/IGNITE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875716#comment-15875716
]
Igor Seliverstov edited comment on IGNITE-4694 at 2/21/17 10:03 AM:
I've created two test suits:
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
But I cannot add them into the TeamCity priject
Seems there is a lack of permissions
was (Author: gvvinblade):
I've created two test suits:
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
- {{org.apache.ignite.testsuites.IgniteDbMemoryLeakTestSuite}}
But I cannot add them into the TeamCity priject
> Add tests to check there are no memory leaks in PageMemory
> --
>
> Key: IGNITE-4694
> URL: https://issues.apache.org/jira/browse/IGNITE-4694
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
>
> Need add several tests running for 5-10 munites verifying there are no memory
> leaks in new data structures based of PageMemory:
> - test various page size
> - test various objects size
> - test put/get/remove operations
> - test create cache/destroy cache operations
> - test cases when indexes enabled/disabled
> - test case when cache expiry policy is used
> New tests should be added in new test suite.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-3469) Get rid of deprecated APIs and entities
[ https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3469: Assignee: Taras Ledkov > Get rid of deprecated APIs and entities > --- > > Key: IGNITE-3469 > URL: https://issues.apache.org/jira/browse/IGNITE-3469 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Assignee: Taras Ledkov > Labels: important > Fix For: 2.0 > > > There are more than 220 deprecated elements in Ignite code kept for the sake > of backward compatibility. We need to cleanup the code for Ignite 2.0 release. > 2.0 migration guide has to be updated if needed: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-3018) Cache affinity calculation is slow with large nodes number
[
https://issues.apache.org/jira/browse/IGNITE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875707#comment-15875707
]
Taras Ledkov commented on IGNITE-3018:
--
Waits for TC [test
results|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F684%2Fhead]
after removing back compatibility for {{RendezvousAffinityFunction}}.
> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
> Attachments: 003.png, 064.png, 100.png, 128.png, 200.png, 300.png,
> 400.png, 500.png, 600.png
>
>
> With large number of cache server nodes (> 200) RendezvousAffinityFunction
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and
> nodes list sorting. As optimization we can try to cache {partion, node} MD5
> hash or try another hash function. Also several minor optimizations are
> possible (avoid unncecessary allocations, only one thread local 'get', etc).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4712) Memory leaks in PageMemory
[ https://issues.apache.org/jira/browse/IGNITE-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875697#comment-15875697 ] ASF GitHub Bot commented on IGNITE-4712: GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/1559 IGNITE-4712 Memory leaks in PageMemory You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4712 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1559.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 #1559 commit 3c9e3786a21ec7c8919de9c29bc04d2e3561846c Author: Igor Seliverstov Date: 2017-02-15T10:41:08Z IGNITE-4694 Add tests to check there are no memory leaks in PageMemory commit 8e12097f9094d7f155135ee2f4c9c33f5f7af9aa Author: sboikov Date: 2017-02-15T12:08:14Z ignite-4694 review commit e70d990f14288cfc8fe211fa25631016d5708144 Author: Igor Seliverstov Date: 2017-02-15T15:04:38Z IGNITE-4694 Add tests to check there are no memory leaks in PageMemory commit 84c03e0c522abc90b2d91e514138eac08388abd2 Author: Igor Seliverstov Date: 2017-02-16T10:41:51Z IGNITE-4694 Add tests to check there are no memory leaks in PageMemory (pending) commit e259b7a2032de9ec1334668e10f92fbae9e5c096 Author: Igor Seliverstov Date: 2017-02-20T10:40:05Z IGNITE-4712 Memory leaks in PageMemory commit fa395addf03376423b9aeb15dd74a7a9969cb851 Author: Igor Seliverstov Date: 2017-02-20T10:43:36Z IGNITE-4712 Memory leaks in PageMemory commit be241d9789392f13c4951e9588c85357cd79192f Author: Igor Seliverstov Date: 2017-02-20T13:19:00Z IGNITE-4712 Memory leaks in PageMemory commit 4376f82d13ef4d08c4eb8d9b6e3f19cba9d9ce1c Author: Igor Seliverstov Date: 2017-02-20T13:40:25Z IGNITE-4712 Memory leaks in PageMemory commit 95faf450cbbf6be4887965209bec3ae0244bcdd9 Author: Igor Seliverstov Date: 2017-02-20T15:11:34Z IGNITE-4712 Memory leaks in PageMemory commit bfb0021b9fbda0ca9fde83ba5513ed3eb32f3703 Author: Igor Seliverstov Date: 2017-02-20T15:25:07Z IGNITE-4712 Memory leaks in PageMemory commit 4ae7d7177b1e55c31579c4691514655eeadb833f Author: Igor Seliverstov Date: 2017-02-20T15:31:15Z IGNITE-4712 Memory leaks in PageMemory commit 5e4e991360c2f2917ec22128e40a353c13db8285 Author: Igor Seliverstov Date: 2017-02-21T08:49:35Z IGNITE-4694 Add tests to check there are no memory leaks in PageMemory > Memory leaks in PageMemory > -- > > Key: IGNITE-4712 > URL: https://issues.apache.org/jira/browse/IGNITE-4712 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov > Fix For: 2.0 > > > During performing put/get/remove operations on large objects (objects, which > size is more than 1kb) allocated pages number constantly grows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (IGNITE-3710) Upgrade ignite-spark module to Spark 2.0
[
https://issues.apache.org/jira/browse/IGNITE-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reopened IGNITE-3710:
--
Examples compilation from sources broken, please check.
{noformat}
exec] [INFO] Compiling 136 source files to
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/target/classes
at 1487618185118
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:20:
error: object spark is not a member of package org.apache.ignite
[22:16:30][exec] [ERROR] import org.apache.ignite.spark.{IgniteContext,
IgniteRDD}
[22:16:30][exec] [ERROR] ^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:22:
error: object spark is not a member of package org.apache
[22:16:30][exec] [ERROR] import org.apache.spark.{SparkConf, SparkContext}
[22:16:30][exec] [ERROR] ^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:37:
error: not found: type SparkConf
[22:16:30][exec] [ERROR] private val conf = new SparkConf()
[22:16:30][exec] [ERROR]^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:43:
error: not found: type SparkContext
[22:16:30][exec] [ERROR] val sparkContext = new SparkContext(conf)
[22:16:30][exec] [ERROR]^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:53:
error: not found: type IgniteContext
[22:16:30][exec] [ERROR] val igniteContext = new
IgniteContext(sparkContext, CONFIG, false)
[22:16:30][exec] [ERROR] ^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:56:
error: not found: type IgniteRDD
[22:16:30][exec] [ERROR] val sharedRDD: IgniteRDD[Int, Int] =
igniteContext.fromCache[Int, Int]("sharedRDD")
[22:16:30][exec] [ERROR]^
[22:16:30][exec] [ERROR]
/home/teamcity/buildAgent/work/b1f08d39c96b68d1/ggtest/var/apache-ignite-fabric-1.9.0-bin/examples/src/main/scala/org/apache/ignite/scalar/examples/spark/ScalarSharedRDDExample.scala:65:
error: not found: type IgniteRDD
[22:16:30][exec] [ERROR] val transformedValues: IgniteRDD[Int, Int] =
igniteContext.fromCache("sharedRDD")
[22:16:30][exec] [ERROR]^
[22:16:30][exec] [ERROR] 7 errors found
[22:16:30][exec] [INFO]
[22:16:30][exec] [INFO] BUILD FAILURE
[22:16:30][exec] [INFO]
[22:16:30][exec] [INFO] Total time: 11.416s
[22:16:30][exec] [INFO] Finished at: Mon Feb 20 22:16:30 MSK 2017
[22:16:30][exec] [INFO] Final Memory: 16M/163M
[22:16:30][exec] [INFO]
[22:16:30][exec] [ERROR] Failed to execute goal
net.alchim31.maven:scala-maven-plugin:3.2.0:compile (scala-compile-first) on
project ignite-examples: wrap: org.apache.commons.exec.ExecuteException: Pr
{noformat}
> Upgrade ignite-spark module to Spark 2.0
>
>
> Key: IGNITE-3710
> URL: https://issues.apache.org/jira/browse/IGNITE-3710
> Project: Ignite
> Issue Type: Improvement
> Components: Ignite RDD
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
>Priority: Critical
> Fix For: 1.9
>
> Attachments: Ignite_Tests_Ignite_RDD_495.log
>
>
> Currently {{ignite-spark}} depends on Spark 1.5.2 and fails with 2.0 with
> this exception:
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/spark/Logging
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> a
[jira] [Updated] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-602: -- Attachment: (was: master_3f4ebad9bd_ignite-602.patch) > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii > Labels: Muted_test > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. > see GG-5000. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4731) Web Console: Revise loaders
[ https://issues.apache.org/jira/browse/IGNITE-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4731: - Assignee: Vica Abramova > Web Console: Revise loaders > --- > > Key: IGNITE-4731 > URL: https://issues.apache.org/jira/browse/IGNITE-4731 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova > > Revise two types of loaders (big and small): > - check the color of big > - add loader to the Queries screen (on execute action) > - check the color of Refresh buttons with animated small loaders -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4731) Web Console: Revise loaders
Vica Abramova created IGNITE-4731: - Summary: Web Console: Revise loaders Key: IGNITE-4731 URL: https://issues.apache.org/jira/browse/IGNITE-4731 Project: Ignite Issue Type: Task Components: UI, wizards Reporter: Vica Abramova Revise two types of loaders (big and small): - check the color of big - add loader to the Queries screen (on execute action) - check the color of Refresh buttons with animated small loaders -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-2845) Get operation might ignore entry update from EntryProcessor.
[
https://issues.apache.org/jira/browse/IGNITE-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875630#comment-15875630
]
ASF GitHub Bot commented on IGNITE-2845:
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/1557
IGNITE-2845 Get operation might ignore entry update from EntryProcessor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-2845
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1557.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 #1557
commit e27b838b0d90dfc8479af56b7a315d84f2b684e2
Author: voipp
Date: 2017-02-20T14:15:10Z
IGNITE-2845 Get operation might ignore entry update from EntryProcessor.
> Get operation might ignore entry update from EntryProcessor.
>
>
> Key: IGNITE-2845
> URL: https://issues.apache.org/jira/browse/IGNITE-2845
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> Originally issue was observed during work with IGFS. Steps to reproduce:
> 1) Start REPLICATE cache.
> 2) Start PESSIMISITC/REPEATABLE_READ transaction.
> 3) Invoke EntryProcessor on non-existent key and call
> "MutableEntry.setValue()" inside it.
> 4) Call {{IgniteCache.get()}} on this value. It will return {{null}}, while
> normally it should return value set inside EntryProcessor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Issue Comment Deleted] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion
[ https://issues.apache.org/jira/browse/IGNITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-602: -- Comment: was deleted (was: Test fixed. Added notes to GridToStringBuilder about infinite looping in additional values.) > [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by > infinite recursion > > > Key: IGNITE-602 > URL: https://issues.apache.org/jira/browse/IGNITE-602 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Ryabov Dmitrii > Labels: Muted_test > Attachments: master_3f4ebad9bd_ignite-602.patch > > > See test > org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention > and related TODO in same source file. > Also take a look at > http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring > Test should be unmuted on TC after fix. > see GG-5000. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4141) JDBC driver should always set withKeepBinary flag when querying cache
[
https://issues.apache.org/jira/browse/IGNITE-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zhuravlev reassigned IGNITE-4141:
-
Assignee: Evgenii Zhuravlev
> JDBC driver should always set withKeepBinary flag when querying cache
> -
>
> Key: IGNITE-4141
> URL: https://issues.apache.org/jira/browse/IGNITE-4141
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc-driver, SQL
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
>
> Generally there are no model classes on the client which uses JDBC driver.
> This means that an attempt to query {{_key}} and {{_val}} fields (which are
> included in {{select *}}) will fail with "Failed resolve class for ID" error.
> To avoid this we should always set {{withKeepBinary()}} flag when executing
> query on server side.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4162) Step-by-step guidance on how to start and use Ignite cluster with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4162: Component/s: documentation > Step-by-step guidance on how to start and use Ignite cluster with Kubernetes > > > Key: IGNITE-4162 > URL: https://issues.apache.org/jira/browse/IGNITE-4162 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda > Fix For: 1.9 > > > At the end, we have to prepare a step-by-step guidance on how to: > - configure, launch and scale Ignite cluster. > - how to connect and work with this cluster from applications running inside > and outside of Kubernetes. > Refer to existed guidance prepared for other products: > https://github.com/kubernetes/kubernetes/tree/master/examples/storage/cassandra > https://github.com/pires/hazelcast-kubernetes > https://www.mongodb.com/blog/post/running-mongodb-as-a-microservice-with-docker-and-kubernetes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
