[jira] [Created] (IGNITE-4206) .NET: ADO.NET Data Provider
Pavel Tupitsyn created IGNITE-4206: -- Summary: .NET: ADO.NET Data Provider Key: IGNITE-4206 URL: https://issues.apache.org/jira/browse/IGNITE-4206 Project: Ignite Issue Type: New Feature Components: platforms Reporter: Pavel Tupitsyn Fix For: 2.0 Implement ADO.NET Data Provider that works with Ignite cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander reassigned IGNITE-4111: - Assignee: Alexander > Communication fails to send message if target node did not finish join process > -- > > Key: IGNITE-4111 > URL: https://issues.apache.org/jira/browse/IGNITE-4111 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Alexander > Fix For: 1.8 > > > Currently this scenario is possible: > - joining node sent join request and waits for > TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology > - others nodes already see this node and can send messages to it (for example > try to run compute job on this node) > - joining node can not receive message: TcpCommunicationSpi will hang inside > 'onFirstMessage' on 'getSpiContext' call, so sending node will get error > trying to establish connection > Possible fix: if in onFirstMessage() spi context is not available, then > TcpCommunicationSpi should send special response which indicates that this > node is not ready yet, and sender should retry after some time. > Also need check internal code for places where message can be unnecessarily > sent to node: one such place is > GridCachePartitionExchangeManager.refreshPartitions - message is sent to all > known nodes, but here we can filter by node order / finished exchage version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4198) Ignite Kafka sink connector should have an option to transform Kafka values
[
https://issues.apache.org/jira/browse/IGNITE-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-4198:
-
Labels: community streaming (was: streaming)
> Ignite Kafka sink connector should have an option to transform Kafka values
> ---
>
> Key: IGNITE-4198
> URL: https://issues.apache.org/jira/browse/IGNITE-4198
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 1.7
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Labels: community, streaming
> Fix For: 1.8
>
>
> Currently the connector takes a Kafka key and uses it as an Ignite key.
> However, Kafka keys can be null, and users may want to specify an Ignite key
> from the value object.
> Instead of creating a new transformer interface, I think we can use
> {{StreamMultipleTupleExtractor}} whenever its implementation is specified by
> the user in connector config file.
> http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-td8731.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4198) Ignite Kafka sink connector should have an option to transform Kafka values
[
https://issues.apache.org/jira/browse/IGNITE-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-4198:
-
Component/s: streaming
> Ignite Kafka sink connector should have an option to transform Kafka values
> ---
>
> Key: IGNITE-4198
> URL: https://issues.apache.org/jira/browse/IGNITE-4198
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 1.7
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Labels: streaming
> Fix For: 1.8
>
>
> Currently the connector takes a Kafka key and uses it as an Ignite key.
> However, Kafka keys can be null, and users may want to specify an Ignite key
> from the value object.
> Instead of creating a new transformer interface, I think we can use
> {{StreamMultipleTupleExtractor}} whenever its implementation is specified by
> the user in connector config file.
> http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-td8731.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4198) Ignite Kafka sink connector should have an option to transform Kafka values
[
https://issues.apache.org/jira/browse/IGNITE-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653036#comment-15653036
]
ASF GitHub Bot commented on IGNITE-4198:
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1225
IGNITE-4198: Kafka Connect sink option to transform Kafka values.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-4198
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1225.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 #1225
commit 0fffdf71dfbaa3d7e551fd2e5b70c1d3f0f71839
Author: shtykh_roman
Date: 2016-11-10T04:52:07Z
IGNITE-4198: Kafka Connect sink option to transform Kafka values.
> Ignite Kafka sink connector should have an option to transform Kafka values
> ---
>
> Key: IGNITE-4198
> URL: https://issues.apache.org/jira/browse/IGNITE-4198
> Project: Ignite
> Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Currently the connector takes a Kafka key and uses it as an Ignite key.
> However, Kafka keys can be null, and users may want to specify an Ignite key
> from the value object.
> Instead of creating a new transformer interface, I think we can use
> {{StreamMultipleTupleExtractor}} whenever its implementation is specified by
> the user in connector config file.
> http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-td8731.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-4199) Functionality to extract keys from values when sinking data from kafka topics
[
https://issues.apache.org/jira/browse/IGNITE-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh resolved IGNITE-4199.
--
Resolution: Duplicate
Thank you, Austin. I will handle the issue with IGNITE-4198.
> Functionality to extract keys from values when sinking data from kafka topics
> -
>
> Key: IGNITE-4199
> URL: https://issues.apache.org/jira/browse/IGNITE-4199
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 1.7
> Environment: linux, centos 7
>Reporter: austin solomon
>Assignee: Roman Shtykh
>Priority: Blocker
> Labels: performance
> Fix For: 1.7
>
>
> I have a use case where I am reading a text file using kafka's
> FileStreamSource connector and sinking the data to Ignite's cache.
> I got an error while doing this
> Error: ERROR Failed to stream a record with null key!
> (org.apache.ignite.stream.kafka.connect.IgniteSinkTask:96)
> When I printed the streamed record i got the following result : key=null
> SinkRecord{kafkaOffset=2, timestampType=CreateTime}
> ConnectRecord{topic='ignitetest', kafkaPartition=2, key=null, value=k1,v1,
> timestamp=1478690650016}
> I wish to have a functionality to extracting keys from values or any work
> around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4199) Functionality to extract keys from values when sinking data from kafka topics
[
https://issues.apache.org/jira/browse/IGNITE-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh reassigned IGNITE-4199:
Assignee: Roman Shtykh
> Functionality to extract keys from values when sinking data from kafka topics
> -
>
> Key: IGNITE-4199
> URL: https://issues.apache.org/jira/browse/IGNITE-4199
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: 1.7
> Environment: linux, centos 7
>Reporter: austin solomon
>Assignee: Roman Shtykh
>Priority: Blocker
> Labels: performance
> Fix For: 1.7
>
>
> I have a use case where I am reading a text file using kafka's
> FileStreamSource connector and sinking the data to Ignite's cache.
> I got an error while doing this
> Error: ERROR Failed to stream a record with null key!
> (org.apache.ignite.stream.kafka.connect.IgniteSinkTask:96)
> When I printed the streamed record i got the following result : key=null
> SinkRecord{kafkaOffset=2, timestampType=CreateTime}
> ConnectRecord{topic='ignitetest', kafkaPartition=2, key=null, value=k1,v1,
> timestamp=1478690650016}
> I wish to have a functionality to extracting keys from values or any work
> around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method
Valentin Kulichenko created IGNITE-4205:
---
Summary: CassandraCacheStore should start IgniteThread threads in
loadCache() method
Key: IGNITE-4205
URL: https://issues.apache.org/jira/browse/IGNITE-4205
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.7
Reporter: Valentin Kulichenko
{{CassandraCacheStore.loadCache()}} method starts a generic thread pool for
parallel data load. Threads in this thread pool can't deserialize Ignite
internal objects (e.g. {{IgniteKernal}}) which can cause unexpected behavior.
Here is one of the scenarios:
* There is column in Cassandra which stores an object as BLOB using
{{JavaSerializer}}.
* {{CacheConfiguration.storeKeepBinary}} is {{true}}.
* When an object is saved, it's passed to the store as an instance of
{{BinaryObject}} which is converted to a byte array and saved in Cassandra.
* When the same object is loaded in {{loadCache}}, the store takes the byte
array and tries to convert it to {{BinaryObject}}. But it can't because this
implies calling {{IgnitionEx.localIgnite()}} from non-Ignite thread.
To fix this we need to provide a thread factory that will create instances of
{{IgniteThread}} and use it in the pool that loads the data.
Most likely the same issue exists in {{CacheAbstractJdbcStore}}.
And in general, any threads created by Ignite internals should be
{{IgniteThread}}-s. This should be revisited.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3674) C++: Add documentation and example for the distributed joins
[
https://issues.apache.org/jira/browse/IGNITE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-3674.
---
> C++: Add documentation and example for the distributed joins
>
>
> Key: IGNITE-3674
> URL: https://issues.apache.org/jira/browse/IGNITE-3674
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 1.8
>
>
> Igor, please add a documentation about the distributed joins that has been
> released recently. You can refer to the Java counterpart:
> https://apacheignite.readme.io/docs/sql-queries#distributed-joins
> In addition, please add a distributed join example. In Java we simply added
> it into {{CacheQueryExample}} extending the latter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3674) C++: Add documentation and example for the distributed joins
[
https://issues.apache.org/jira/browse/IGNITE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652439#comment-15652439
]
Prachi Garg commented on IGNITE-3674:
-
Added TOC to the page.
> C++: Add documentation and example for the distributed joins
>
>
> Key: IGNITE-3674
> URL: https://issues.apache.org/jira/browse/IGNITE-3674
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Minor
> Fix For: 1.8
>
>
> Igor, please add a documentation about the distributed joins that has been
> released recently. You can refer to the Java counterpart:
> https://apacheignite.readme.io/docs/sql-queries#distributed-joins
> In addition, please add a distributed join example. In Java we simply added
> it into {{CacheQueryExample}} extending the latter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3674) C++: Add documentation and example for the distributed joins
[
https://issues.apache.org/jira/browse/IGNITE-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prachi Garg reassigned IGNITE-3674:
---
Assignee: Denis Magda (was: Prachi Garg)
> C++: Add documentation and example for the distributed joins
>
>
> Key: IGNITE-3674
> URL: https://issues.apache.org/jira/browse/IGNITE-3674
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 1.8
>
>
> Igor, please add a documentation about the distributed joins that has been
> released recently. You can refer to the Java counterpart:
> https://apacheignite.readme.io/docs/sql-queries#distributed-joins
> In addition, please add a distributed join example. In Java we simply added
> it into {{CacheQueryExample}} extending the latter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4118) .NET: documentation and examples for deadlock-free transactions
[ https://issues.apache.org/jira/browse/IGNITE-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-4118: --- Assignee: Pavel Tupitsyn (was: Prachi Garg) > .NET: documentation and examples for deadlock-free transactions > --- > > Key: IGNITE-4118 > URL: https://issues.apache.org/jira/browse/IGNITE-4118 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Denis Magda >Assignee: Pavel Tupitsyn > Fix For: 1.8 > > > Presently the documentation and example about the deadlock-free transactions > are missing on .NET side. Let's fill this gap. > - Documentation can be taken from Java side > https://apacheignite.readme.io/v1.7/docs/transactions#optimistic-transactions > https://apacheignite.readme.io/v1.7/docs/transactions#deadlock-free-transactions > - The example that can be (should be) added to the distribution is the > following > https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/OptimisticTransactionExample.cs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4118) .NET: documentation and examples for deadlock-free transactions
[ https://issues.apache.org/jira/browse/IGNITE-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652409#comment-15652409 ] Prachi Garg commented on IGNITE-4118: - Looks good. > .NET: documentation and examples for deadlock-free transactions > --- > > Key: IGNITE-4118 > URL: https://issues.apache.org/jira/browse/IGNITE-4118 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Denis Magda >Assignee: Prachi Garg > Fix For: 1.8 > > > Presently the documentation and example about the deadlock-free transactions > are missing on .NET side. Let's fill this gap. > - Documentation can be taken from Java side > https://apacheignite.readme.io/v1.7/docs/transactions#optimistic-transactions > https://apacheignite.readme.io/v1.7/docs/transactions#deadlock-free-transactions > - The example that can be (should be) added to the distribution is the > following > https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/OptimisticTransactionExample.cs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2680) Terminating running SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652060#comment-15652060
]
Denis Magda commented on IGNITE-2680:
-
[~ascherbakov], could update SQL readme.io documentation [1] by including
information about the feature I've just implemented?
[1] https://apacheignite.readme.io/docs/sql-queries
> Terminating running SQL queries
> ---
>
> Key: IGNITE-2680
> URL: https://issues.apache.org/jira/browse/IGNITE-2680
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Alexei Scherbakov
> Labels: important
> Fix For: 1.8
>
>
> If to start a long running SQL query over a huge cache will millions of
> entries there should be a way terminate it. Even if {{QueryCursor}} is closed
> the query won't be cancelled consuming available resources.
> There should be a way to close a query having using an object that is related
> to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2680) Terminating running SQL queries
[
https://issues.apache.org/jira/browse/IGNITE-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov resolved IGNITE-2680.
---
Resolution: Fixed
Fix Version/s: 1.8
Resolved, merged to master.
> Terminating running SQL queries
> ---
>
> Key: IGNITE-2680
> URL: https://issues.apache.org/jira/browse/IGNITE-2680
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Alexei Scherbakov
> Labels: important
> Fix For: 1.8
>
>
> If to start a long running SQL query over a huge cache will millions of
> entries there should be a way terminate it. Even if {{QueryCursor}} is closed
> the query won't be cancelled consuming available resources.
> There should be a way to close a query having using an object that is related
> to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4175) SQL: JdbcResultSet class wasNull() method should return true on NULL fields
[ https://issues.apache.org/jira/browse/IGNITE-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651790#comment-15651790 ] Andrew Mashenkov commented on IGNITE-4175: -- Fixed. > SQL: JdbcResultSet class wasNull() method should return true on NULL fields > --- > > Key: IGNITE-4175 > URL: https://issues.apache.org/jira/browse/IGNITE-4175 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.6, 1.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Labels: newbie > Fix For: 1.8 > > > For now wasNull() method can return false for NULL field in case of field > typed as String. > Startpoints are org.apache.ignite.internal.jdbc.JdbcResultSet class > and org.apache.ignite.internal.jdbc2.JdbcResultSet class -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4175) SQL: JdbcResultSet class wasNull() method should return true on NULL fields
[
https://issues.apache.org/jira/browse/IGNITE-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651680#comment-15651680
]
Andrey Gura commented on IGNITE-4175:
-
I completely don't understand why our JDBC drivers return {{"null"}} string
instead of {{null}} value in this case. From my point of view current behavior
is incorrect. See also JDCB {{ResultSet.getString()}} method's javadoc:
{code:java}
/**
* Retrieves the value of the designated column in the current row
* of this ResultSet object as
* a String in the Java programming language.
*
* @param columnIndex the first column is 1, the second is 2, ...
* @return the column value; if the value is SQL NULL, the
* value returned is null
* @exception SQLException if the columnIndex is not valid;
* if a database access error occurs or this method is
*called on a closed result set
*/
String getString(int columnIndex) throws SQLException;
{code}
> SQL: JdbcResultSet class wasNull() method should return true on NULL fields
> ---
>
> Key: IGNITE-4175
> URL: https://issues.apache.org/jira/browse/IGNITE-4175
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Labels: newbie
> Fix For: 1.8
>
>
> For now wasNull() method can return false for NULL field in case of field
> typed as String.
> Startpoints are org.apache.ignite.internal.jdbc.JdbcResultSet class
> and org.apache.ignite.internal.jdbc2.JdbcResultSet class
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4145) "No query result found for request" exception when running multiple queries concurrently.
[
https://issues.apache.org/jira/browse/IGNITE-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651631#comment-15651631
]
Andrew Mashenkov commented on IGNITE-4145:
--
This bug is a race condition and I it's impossible to make a unit test for it.
It should be some kind of load or stress test.
It take few minutes for me to reproduce this bug under load. I'll add a
reproducer, but which test suite it should be added to?
> "No query result found for request" exception when running multiple queries
> concurrently.
> -
>
> Key: IGNITE-4145
> URL: https://issues.apache.org/jira/browse/IGNITE-4145
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> When many queries are executed simultaneously in multi-node cluster, the
> following exception might appear from time to time:
> {code}
> Exception in thread "qry-exec-20" javax.cache.CacheException: Failed to fetch
> data from node: 3432842f-2fa2-44b9-b69b-cadba286d317
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$3.fetchNextPage(GridReduceQueryExecutor.java:298)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex.fetchNextPage(GridMergeIndex.java:229)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexUnsorted$1.hasNext(GridMergeIndexUnsorted.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$IteratorCursor.next(GridMergeIndex.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.next(GridMergeIndex.java:382)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:640)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1057)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:81)
> at
> org.apache.ignite.yardstick.ringcentral.AdgRunner$QueryExecutor.run(AdgRunner.java:394)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: javax.cache.CacheException: Failed to execute map query on
> the node: c51bc4f2-7038-4df6-88a9-eb87506c2f86, class
> javax.cache.CacheException:No query result found for request:
> GridQueryNextPageRequest [qryReqId=93, qry=0, pageSize=1024]
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:259)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:249)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:230)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:178)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1900)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:708)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:101)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:671)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> {code}
> Quick analysis shows that next-page request could possibly arrive before
> original query message is processed. Need to confirm it with deeper debugging
> first.
> The best way to reproduce it:
> 1) Generate some data
> 2) Start several data nodes (e.g. 4)
> 3) Start client node
> 4) Concurrently execute multiple SQL queries from the client in different
> threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2731) Cache and cluster metrics documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergej Sidorov reassigned IGNITE-2731: -- Assignee: Sergej Sidorov > Cache and cluster metrics documentation on readme.io > > > Key: IGNITE-2731 > URL: https://issues.apache.org/jira/browse/IGNITE-2731 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0.final >Reporter: Denis Magda >Assignee: Sergej Sidorov > Fix For: 1.8 > > > Cache and cluster metrics related topic is becoming hot on the user list. > 1) > http://apache-ignite-users.70518.x6.nabble.com/Monitoring-Cache-Data-counters-Cache-Data-Size-td3203.html#a3211 > 2) > http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-cache-metrics-for-all-the-nodes-in-cluster-combined-td2674.html > 3) > http://apache-ignite-users.70518.x6.nabble.com/Metrics-for-backup-caches-td2689.html#a2692 > The time to add the documentation to the readme.io has come. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4204) OptimizedMarshaller throws exception for Cache. JdkMarshaller works fine but slow.
Quenie Sun created IGNITE-4204: -- Summary: OptimizedMarshaller throws exception for Cache. JdkMarshaller works fine but slow. Key: IGNITE-4204 URL: https://issues.apache.org/jira/browse/IGNITE-4204 Project: Ignite Issue Type: Bug Reporter: Quenie Sun 2016-11-08 10:35:47.099-06:00 INFO [main] o.a.catalina.core.StandardService - Stopping service Tomcat 2016-11-08 10:35:47.118-06:00 ERROR [main] o.s.boot.SpringApplication - Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'springContextBridge': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.netscout.biexport.datacollection.ProvisioningCacheSync com.netscout.biexport.util.SpringContextBridge.provisioningTimeCoordinator; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'provisioningUpdateTimeCoordinator' defined in class path resource [PipelineAppContext.xml]: Cannot resolve reference to bean 'lookupImpl' while setting bean property 'dimensionLookup'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'lookupImpl' defined in class path resource [LookupAppContext.xml]: Invocation of init method failed; nested exception is javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to serialize object: DynaProperty[name=hst_handset_id,type=class java.lang.Integer] at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:334) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1214) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772) ~[spring-beans-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839) ~[spring-context-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538) ~[spring-context-4.2.5.RELEASE.jar:4.2.5.RELEASE] at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:307) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1191) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1180) [spring-boot-1.3.3.RELEASE.jar:1.3.3.RELEASE] at com.netscout.biexport.DataImportApplication.main(DataImportApplication.java:27) [classes/:na] Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.netscout.biexport.datacollection.ProvisioningCacheSync com.netscout.
[jira] [Updated] (IGNITE-4202) .NET: Document Entity Framework caching on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4202: --- Priority: Trivial (was: Major) > .NET: Document Entity Framework caching on readme.io > > > Key: IGNITE-4202 > URL: https://issues.apache.org/jira/browse/IGNITE-4202 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Trivial > Labels: .NET > Fix For: 1.8 > > > Keep the page hidden until release > https://apacheignite-net.readme.io/v1.7/docs/entity-framework-second-level-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4203) .NET: Document ASP.NET Session State caching on readme.io
Pavel Tupitsyn created IGNITE-4203: -- Summary: .NET: Document ASP.NET Session State caching on readme.io Key: IGNITE-4203 URL: https://issues.apache.org/jira/browse/IGNITE-4203 Project: Ignite Issue Type: Task Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Priority: Trivial Fix For: 1.8 Keep the page hidden until release https://apacheignite-net.readme.io/v1.7/docs/aspnet-session-state-caching -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4202) .NET: Document Entity Framework caching on readme.io
Pavel Tupitsyn created IGNITE-4202: -- Summary: .NET: Document Entity Framework caching on readme.io Key: IGNITE-4202 URL: https://issues.apache.org/jira/browse/IGNITE-4202 Project: Ignite Issue Type: Task Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.8 Keep the page hidden until release https://apacheignite-net.readme.io/v1.7/docs/entity-framework-second-level-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4100) Some typos and missing references in cpp platform instructions
[
https://issues.apache.org/jira/browse/IGNITE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651290#comment-15651290
]
ASF GitHub Bot commented on IGNITE-4100:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1223
IGNITE-4100: Improved README and DEVNOTES for CPP.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4100
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1223.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 #1223
commit 7290d88e14a15a3d030b7381dbd0a3f14cb65a12
Author: Pavel Tupitsyn
Date: 2016-10-18T14:17:17Z
IGNITE-4030 Streamline PlatformTarget operation methods
This closes #1167
commit 66c76d1f30f024b58db8cab07ba9e7d429f596f8
Author: tledkov-gridgain
Date: 2016-10-18T15:45:06Z
IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest.
Clear connection poll after the test, cosmetic.
commit f37fbcab1ae2c7553696e96b7a9c3194a570d7af
Author: isapego
Date: 2016-10-19T10:06:42Z
IGNITE-3705: Fixed compiliation warnings. This closes #1169.
commit 7ed2bb7e341701d052220a36a2b2f8f0a46fd644
Author: AMRepo
Date: 2016-10-19T15:33:59Z
IGNITE-3448 Support SQL queries with distinct aggregates added. This closes
#3448.
commit 551a4dfae6169a07a5e28f9b266f90311f3216b7
Author: tledkov-gridgain
Date: 2016-10-21T10:25:57Z
IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest.
Clear connection poll before and after the test
commit ec12a9db2265180f96be72e2217e60ced856164e
Author: vozerov-gridgain
Date: 2016-10-24T14:52:36Z
Minor fix for flags passed to GridCacheMapEntry.initialValue from data
streamer isolated updater.
commit 44740465677c39068dc813dabd464e60f09e5f49
Author: tledkov-gridgain
Date: 2016-10-26T13:00:11Z
IGNITE-4062: fix BinaryObject.equals: compare only bytes containing the
fields' data (without header and footer). This closes #1182.
commit c22411b740d1cdbe0c24c2502b4d6cb992335d6f
Author: isapego
Date: 2016-10-26T16:16:14Z
IGNITE-4100: Improved README and DEVNOTES for CPP.
commit 277691c1da25746093eb96019f2801386922fdbd
Author: Igor Sapego
Date: 2016-11-09T15:55:03Z
IGNITE-4100: Specified full path to ODBC readme file.
> Some typos and missing references in cpp platform instructions
> --
>
> Key: IGNITE-4100
> URL: https://issues.apache.org/jira/browse/IGNITE-4100
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> 1) Fix typo in $IGNITE_HOME/platforms/cpp/DEVNOTES.txt, line 40:
> {{heasders}} -> {{headers}}
> 2) Fix typo in $IGNITE_HOME/platforms/cpp/README.txt, line 5:
> {{you can execute perform}} -> {{you can perform}} or {{you can execute}}
> 3) Fix typo in $IGNITE_HOME/platforms/cpp/README.txt, line 52:
> {{odbc.dll}} -> {{ignite.odbc.dll}}
> 4) $IGNITE_HOME/platforms/cpp/DEVNOTES.txt:
> add some note (to both linux and windows sections or to common section) that
> user should refer to $IGNITE_HOME/platforms/cpp/odbc/README.txt to install
> odbc driver
> 5) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 10 {{Apache Ignite
> C++ must be built according to instructions for your platform}}:
> add a reference to the instruction $IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 6) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 29 {{Apache Ignite
> ODBC driver must be built and installed according to instructions for your
> platform.}}:
> suggest you moving this to {{Common requirements}} (since it's actual for
> both Linux and Win) and adding a reference to the instruction
> $IGNITE_HOME/platforms/cpp/odbc/README.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4157) Use discovery custom messages instead of marshaller and system cache
[ https://issues.apache.org/jira/browse/IGNITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651287#comment-15651287 ] Sergey Chugunov commented on IGNITE-4157: - Implemented first version of supplying a newly joined node with mapping information existing on other nodes in Ignite cluster. > Use discovery custom messages instead of marshaller and system cache > > > Key: IGNITE-4157 > URL: https://issues.apache.org/jira/browse/IGNITE-4157 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexey Goncharuk >Assignee: Sergey Chugunov > Fix For: 2.0 > > > Currently we use system caches for keeping classname to class ID mapping and > for storing binary metadata > This has several serious disadvantages: > 1) We need to introduce at least two additional thread pools for each of > these caches > 2) Since cache operations require stable topology, registering a class ID or > updating metadata inside a transaction or another cache operation is tricky > and deadlock-prone. > 3) It may be beneficial in some cases to have nodes with no caches at all, > currently this is impossible because system caches are always present. > 4) Reading binary metadata leads to huge local contention, caching metadata > values in a local map doubles memory consumption > I suggest we use discovery custom events for these purposes. Each node will > have a corresponding local map (state) which will be updated inside custom > event handler. From the first point of view, this should remove all the > disadvantages above. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4100) Some typos and missing references in cpp platform instructions
[
https://issues.apache.org/jira/browse/IGNITE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651279#comment-15651279
]
Igor Sapego commented on IGNITE-4100:
-
Vladimir, the problem is there are different paths for binary and source
distributions:
* {{$IGNITE_HOME/modules/platforms/cpp/odbc/README.txt}} for source
distribution.
* {{$IGNITE_HOME/platforms/cpp/odbc/README.txt}} for binary distribution.
> Some typos and missing references in cpp platform instructions
> --
>
> Key: IGNITE-4100
> URL: https://issues.apache.org/jira/browse/IGNITE-4100
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> 1) Fix typo in $IGNITE_HOME/platforms/cpp/DEVNOTES.txt, line 40:
> {{heasders}} -> {{headers}}
> 2) Fix typo in $IGNITE_HOME/platforms/cpp/README.txt, line 5:
> {{you can execute perform}} -> {{you can perform}} or {{you can execute}}
> 3) Fix typo in $IGNITE_HOME/platforms/cpp/README.txt, line 52:
> {{odbc.dll}} -> {{ignite.odbc.dll}}
> 4) $IGNITE_HOME/platforms/cpp/DEVNOTES.txt:
> add some note (to both linux and windows sections or to common section) that
> user should refer to $IGNITE_HOME/platforms/cpp/odbc/README.txt to install
> odbc driver
> 5) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 10 {{Apache Ignite
> C++ must be built according to instructions for your platform}}:
> add a reference to the instruction $IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 6) $IGNITE_HOME/platforms/cpp/examples/README.txt, line 29 {{Apache Ignite
> ODBC driver must be built and installed according to instructions for your
> platform.}}:
> suggest you moving this to {{Common requirements}} (since it's actual for
> both Linux and Win) and adding a reference to the instruction
> $IGNITE_HOME/platforms/cpp/odbc/README.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-1915. Resolution: Fixed Assignee: (was: Pavel Tupitsyn) > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > Attachments: Program.cs > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[
https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651270#comment-15651270
]
Pavel Tupitsyn commented on IGNITE-1915:
How to test:
* Create a new Console Application project in Visual Studio
* Install EntityFramework packages to work with SQL CE: Install-Package
EntityFramework.SqlServerCompact
* Paste the code from attached Program.cs. It uses Entity Framework without any
caching. Run the code and verify that it creates and queries an object,
printing "Hello!"
* Install Apache.Ignite.EntityFramework NuGet package (nightly build can be
installed via {code} Install-Package Apache.Ignite.EntityFramework -Pre -Source
https://www.myget.org/F/apache-ignite-net-nightly{code})
* Mark FooContext class with
{code}[DbConfigurationType(typeof(IgniteDbConfiguration))]{code}
* Run the program again and verify that it works: Ignite node starts, then
"Hello!" is printed like before
* Add the following to the end of the main method:
{code}
using (var ctx = new FooContext())
{
Console.WriteLine(ctx.Foos.Single().Bar);
}
foreach (var cacheName in Ignition.GetIgnite().GetCacheNames())
{
Console.WriteLine(">>> " + cacheName);
foreach (var e in Ignition.GetIgnite().GetCache(cacheName).WithKeepBinary())
{
Console.WriteLine(e);
}
}
{code}
Verify that the output is similar to:
{code}
Hello!
Hello!
>>> entityFrameworkQueryCache_metadata
CacheEntry [Key=Foo, Value=1]
>>> entityFrameworkQueryCache_data
CacheEntry [Key=PlatformDotNetEntityFrameworkCacheKey [idHash=29530116],
Value=PlatformDotNetEntityFrameworkCacheEntry [idHash=6454]]
CacheEntry [Key=PlatformDotNetEntityFrameworkCacheKey [idHash=43129175],
Value=PlatformDotNetEntityFrameworkCacheEntry [idHash=52618256]]
CacheEntry [Key=PlatformDotNetEntityFrameworkCacheKey [idHash=3802258],
Value=PlatformDotNetEntityFrameworkCacheEntry [idHash=34220326]]
{code}
> .NET: Ignite as Entity Framework Second-Level Cache
> ---
>
> Key: IGNITE-1915
> URL: https://issues.apache.org/jira/browse/IGNITE-1915
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
> Attachments: Program.cs
>
>
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with
> Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in
> one, EF6 requies more customization or a 3rd party lib like
> https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1915: --- Attachment: Program.cs > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > Attachments: Program.cs > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4201) CPP: fix versioning of C++ libs
[ https://issues.apache.org/jira/browse/IGNITE-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651211#comment-15651211 ] ASF GitHub Bot commented on IGNITE-4201: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1222 IGNITE-4201: Fixed version fix maven step. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4201 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1222.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 #1222 commit 3ef5f61b6e6abcb1fcce89af842fa59af52d0674 Author: Igor Sapego Date: 2016-11-09T15:17:38Z IGNITE-4201: Fixed version fix maven step. > CPP: fix versioning of C++ libs > --- > > Key: IGNITE-4201 > URL: https://issues.apache.org/jira/browse/IGNITE-4201 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.7 >Reporter: Ksenia Rybakova >Assignee: Igor Sapego > > Currently versions are not set properly in Ignite C++ core libraries names > if we build this libraries on Linux according to > $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. > For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of > libignite*-1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651199#comment-15651199 ] Pavel Tupitsyn commented on IGNITE-1915: Merged to master. > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651197#comment-15651197 ] ASF GitHub Bot commented on IGNITE-1915: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1221 > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4186) .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
[
https://issues.apache.org/jira/browse/IGNITE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651187#comment-15651187
]
Pavel Tupitsyn commented on IGNITE-4186:
I wonder if this happens in a particular ASP.NET version. Can't reproduce with
.NET 4.0 and .NET 4.6 for now.
> .NET: "Invalid session release request" exception in
> IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
> ---
>
> Key: IGNITE-4186
> URL: https://issues.apache.org/jira/browse/IGNITE-4186
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
> Environment: Windows 10
> MS VS 2015
> .NET Framework 4.0.30319
> ASP.NET 4.6.1586.0
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Steps:
> - Create a new C# Web application in MS Visual Studio
> - Install Apache.Ignite.AspNet package via Tools->NuGet Package
> ManagerPackage Manager Console
> - Open Web.config file, remove default sessionState section in
> and add the following instead:
> {noformat}
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> - Open Default.aspx.cs file and add the following to Page_Load method
> {noformat}
> Session["test"] = "abc";
> {noformat}
> - Run project
> Result:
> {noformat}
> [IgniteException: Invalid session release request, expected lockId: 0,
> actual: ]
>
> Apache.Ignite.AspNet.IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive(HttpContext
> context, String id, SessionStateStoreData item, Object lockId, Boolean
> newItem) +298
>System.Web.SessionState.SessionStateModule.OnReleaseState(Object source,
> EventArgs eventArgs) +573
>
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> +141
>System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +69
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4186) .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
[
https://issues.apache.org/jira/browse/IGNITE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-4186:
--
Assignee: Pavel Tupitsyn
> .NET: "Invalid session release request" exception in
> IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive
> ---
>
> Key: IGNITE-4186
> URL: https://issues.apache.org/jira/browse/IGNITE-4186
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
> Environment: Windows 10
> MS VS 2015
> .NET Framework 4.0.30319
> ASP.NET 4.6.1586.0
>Reporter: Ksenia Rybakova
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Steps:
> - Create a new C# Web application in MS Visual Studio
> - Install Apache.Ignite.AspNet package via Tools->NuGet Package
> ManagerPackage Manager Console
> - Open Web.config file, remove default sessionState section in
> and add the following instead:
> {noformat}
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> - Open Default.aspx.cs file and add the following to Page_Load method
> {noformat}
> Session["test"] = "abc";
> {noformat}
> - Run project
> Result:
> {noformat}
> [IgniteException: Invalid session release request, expected lockId: 0,
> actual: ]
>
> Apache.Ignite.AspNet.IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive(HttpContext
> context, String id, SessionStateStoreData item, Object lockId, Boolean
> newItem) +298
>System.Web.SessionState.SessionStateModule.OnReleaseState(Object source,
> EventArgs eventArgs) +573
>
> System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
> +141
>System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
> completedSynchronously) +69
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4145) "No query result found for request" exception when running multiple queries concurrently.
[
https://issues.apache.org/jira/browse/IGNITE-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651139#comment-15651139
]
Sergi Vladykin commented on IGNITE-4145:
Looks good to me, but do we have a test for this issue?
> "No query result found for request" exception when running multiple queries
> concurrently.
> -
>
> Key: IGNITE-4145
> URL: https://issues.apache.org/jira/browse/IGNITE-4145
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> When many queries are executed simultaneously in multi-node cluster, the
> following exception might appear from time to time:
> {code}
> Exception in thread "qry-exec-20" javax.cache.CacheException: Failed to fetch
> data from node: 3432842f-2fa2-44b9-b69b-cadba286d317
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$3.fetchNextPage(GridReduceQueryExecutor.java:298)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex.fetchNextPage(GridMergeIndex.java:229)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexUnsorted$1.hasNext(GridMergeIndexUnsorted.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$IteratorCursor.next(GridMergeIndex.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.next(GridMergeIndex.java:382)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:640)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1057)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:81)
> at
> org.apache.ignite.yardstick.ringcentral.AdgRunner$QueryExecutor.run(AdgRunner.java:394)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: javax.cache.CacheException: Failed to execute map query on
> the node: c51bc4f2-7038-4df6-88a9-eb87506c2f86, class
> javax.cache.CacheException:No query result found for request:
> GridQueryNextPageRequest [qryReqId=93, qry=0, pageSize=1024]
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:259)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:249)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:230)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:178)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1900)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:708)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:101)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:671)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> {code}
> Quick analysis shows that next-page request could possibly arrive before
> original query message is processed. Need to confirm it with deeper debugging
> first.
> The best way to reproduce it:
> 1) Generate some data
> 2) Start several data nodes (e.g. 4)
> 3) Start client node
> 4) Concurrently execute multiple SQL queries from the client in different
> threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4201) CPP: fix versioning of C++ libs
[ https://issues.apache.org/jira/browse/IGNITE-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-4201: --- Assignee: Igor Sapego > CPP: fix versioning of C++ libs > --- > > Key: IGNITE-4201 > URL: https://issues.apache.org/jira/browse/IGNITE-4201 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.7 >Reporter: Ksenia Rybakova >Assignee: Igor Sapego > > Currently versions are not set properly in Ignite C++ core libraries names > if we build this libraries on Linux according to > $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. > For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of > libignite*-1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1075) IgniteDataStreamer doesn't throw an exception if there are no data nodes
[
https://issues.apache.org/jira/browse/IGNITE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650958#comment-15650958
]
Anton Vinogradov commented on IGNITE-1075:
--
Issue fixed by IGNITE-500
> IgniteDataStreamer doesn't throw an exception if there are no data nodes
>
>
> Key: IGNITE-1075
> URL: https://issues.apache.org/jira/browse/IGNITE-1075
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Labels: Usability
> Time Spent: 3h
> Remaining Estimate: 0h
>
> If you call {{addData}} method, but there are no data nodes, you will never
> know about it. Looks like it is returned in a future, but it's
> counterintuitive to call it on each operation just to check for exception.
> Probably we should print out these errors in logs as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1075) IgniteDataStreamer doesn't throw an exception if there are no data nodes
[
https://issues.apache.org/jira/browse/IGNITE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-1075:
Assignee: Anton Vinogradov (was: Semen Boikov)
> IgniteDataStreamer doesn't throw an exception if there are no data nodes
>
>
> Key: IGNITE-1075
> URL: https://issues.apache.org/jira/browse/IGNITE-1075
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Anton Vinogradov
>Priority: Critical
> Labels: Usability
> Time Spent: 3h
> Remaining Estimate: 0h
>
> If you call {{addData}} method, but there are no data nodes, you will never
> know about it. Looks like it is returned in a future, but it's
> counterintuitive to call it on each operation just to check for exception.
> Probably we should print out these errors in logs as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4201) CPP: fix versioning of C++ libs
[ https://issues.apache.org/jira/browse/IGNITE-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ksenia Rybakova updated IGNITE-4201: Description: Currently versions are not set properly in Ignite C++ core libraries names if we build this libraries on Linux according to $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of libignite*-1.7.3 was: Currently versions are not set properly in Ignite C++ core libraries names if we build the libs on Linux according to $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of libignite*-1.7.3 > CPP: fix versioning of C++ libs > --- > > Key: IGNITE-4201 > URL: https://issues.apache.org/jira/browse/IGNITE-4201 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.7 >Reporter: Ksenia Rybakova > > Currently versions are not set properly in Ignite C++ core libraries names > if we build this libraries on Linux according to > $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. > For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of > libignite*-1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4201) CPP: fix versioning of C++ libs
Ksenia Rybakova created IGNITE-4201: --- Summary: CPP: fix versioning of C++ libs Key: IGNITE-4201 URL: https://issues.apache.org/jira/browse/IGNITE-4201 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.7 Reporter: Ksenia Rybakova Currently versions are not set properly in Ignite C++ core libraries names if we build the libs on Linux according to $IGNITE_HOME/platforms/cpp/DEVNOTES.txt. For instance, for version 1.7.3 names are libignite*-1.6.0.8653 instead of libignite*-1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3873) ODBC: Create installer for the ODBC.
[ https://issues.apache.org/jira/browse/IGNITE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650928#comment-15650928 ] Igor Sapego commented on IGNITE-3873: - Vladimir, Done. > ODBC: Create installer for the ODBC. > > > Key: IGNITE-3873 > URL: https://issues.apache.org/jira/browse/IGNITE-3873 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > It would be nice to have .msi installer for our ODBC driver, so that user > would not have a need to compile and install driver manually. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3873) ODBC: Create installer for the ODBC.
[ https://issues.apache.org/jira/browse/IGNITE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-3873. - Resolution: Fixed > ODBC: Create installer for the ODBC. > > > Key: IGNITE-3873 > URL: https://issues.apache.org/jira/browse/IGNITE-3873 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > It would be nice to have .msi installer for our ODBC driver, so that user > would not have a need to compile and install driver manually. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out
[
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-3862:
-
Assignee: Dmitry Karachentsev (was: Semen Boikov)
> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an
> exception on server side can cause the closure execution never finish. For
> example, this happens when the exception is thrown during the serialization
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650899#comment-15650899 ] ASF GitHub Bot commented on IGNITE-1915: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1221 IGNITE-1915 .NET: Ignite as Entity Framework Second-Level Cache You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1915-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1221.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 #1221 commit 49cb9fd033b851329de123414cd0ef8c72984507 Author: Pavel Tupitsyn Date: 2016-11-09T13:15:45Z IGNITE-1915 .NET: Ignite as Entity Framework Second-Level Cache > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650902#comment-15650902 ] ASF GitHub Bot commented on IGNITE-1915: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1142 > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650872#comment-15650872 ] Pavel Tupitsyn commented on IGNITE-1915: Fixed. > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4200) ODBC: Integrate generation of the ODBC installer to build process.
Igor Sapego created IGNITE-4200: --- Summary: ODBC: Integrate generation of the ODBC installer to build process. Key: IGNITE-4200 URL: https://issues.apache.org/jira/browse/IGNITE-4200 Project: Ignite Issue Type: Task Components: build, odbc Affects Versions: 1.7 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.8 We are going to have ability to generate ODBC driver soon. We should add generation of such an installer as a build step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4182) Improve error output when query parsing failed.
[
https://issues.apache.org/jira/browse/IGNITE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-4182:
Fix Version/s: 1.8
> Improve error output when query parsing failed.
> ---
>
> Key: IGNITE-4182
> URL: https://issues.apache.org/jira/browse/IGNITE-4182
> Project: Ignite
> Issue Type: Task
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.8
>
>
> There is no enough information in the exception when SLQ query can not be
> parsed. In most cases we get something like this:
> {noformat}
> Failed to execute SQL query [reqId=2, req=OdbcQueryExecuteRequest
> [cacheName=cache, sqlQry=SELECT a FROM B, args=[]]]
> javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed
> to parse query: SELECT a FROM B
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:740)
> at
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.executeQuery(OdbcRequestHandler.java:193)
> at
> org.apache.ignite.internal.processors.odbc.OdbcRequestHandler.handle(OdbcRequestHandler.java:104)
> at
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:124)
> at
> org.apache.ignite.internal.processors.odbc.OdbcNioListener.onMessage(OdbcNioListener.java:33)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:270)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:95)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: Failed to parse query:
> SELECT a FROM B
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:749)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:728)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse
> query: SELECT a FROM B
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1695)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:742)
> ... 13 more
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
> parse query: SELECT a FROM B
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep0(IgniteH2Indexing.java:1887)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1793)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:744)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$2.applyx(GridQueryProcessor.java:742)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1672)
> ... 14 more
> {noformat}
> In this particular case, for example, we do not have table "B", nor we have
> column "a", but you can't get it from the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3138) IgniteDataStreamer: failures are not shown on the streaming side
[
https://issues.apache.org/jira/browse/IGNITE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650811#comment-15650811
]
Anton Vinogradov commented on IGNITE-3138:
--
Issue fixed by IGNITE-500
> IgniteDataStreamer: failures are not shown on the streaming side
>
>
> Key: IGNITE-3138
> URL: https://issues.apache.org/jira/browse/IGNITE-3138
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Anton Vinogradov
> Attachments: DataStreamerFailuresTest.java
>
>
> If an exception happens during the streaming, the side that streams the data
> won't printed out anything in its logs even if IGNITE_QUIET set to false.
> This makes it's inconvenient to see whether there an issue happened during
> the streaming or not.
> Suggested improvements:
> - print out errors that happened during the streaming on the streaming side;
> - Future that is returned from {{addData}} methods is not called in case of
> error. This must be fixed. So that the user is able to write a custom logic
> around this feature and process errors somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3138) IgniteDataStreamer: failures are not shown on the streaming side
[
https://issues.apache.org/jira/browse/IGNITE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-3138:
Assignee: Anton Vinogradov (was: Vladislav Pyatkov)
> IgniteDataStreamer: failures are not shown on the streaming side
>
>
> Key: IGNITE-3138
> URL: https://issues.apache.org/jira/browse/IGNITE-3138
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Anton Vinogradov
> Attachments: DataStreamerFailuresTest.java
>
>
> If an exception happens during the streaming, the side that streams the data
> won't printed out anything in its logs even if IGNITE_QUIET set to false.
> This makes it's inconvenient to see whether there an issue happened during
> the streaming or not.
> Suggested improvements:
> - print out errors that happened during the streaming on the streaming side;
> - Future that is returned from {{addData}} methods is not called in case of
> error. This must be fixed. So that the user is able to write a custom logic
> around this feature and process errors somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4199) Functionality to extract keys from values when sinking data from kafka topics
austin solomon created IGNITE-4199:
--
Summary: Functionality to extract keys from values when sinking
data from kafka topics
Key: IGNITE-4199
URL: https://issues.apache.org/jira/browse/IGNITE-4199
Project: Ignite
Issue Type: Improvement
Components: streaming
Affects Versions: 1.7
Environment: linux, centos 7
Reporter: austin solomon
Priority: Blocker
Fix For: 1.7
I have a use case where I am reading a text file using kafka's
FileStreamSource connector and sinking the data to Ignite's cache.
I got an error while doing this
Error: ERROR Failed to stream a record with null key!
(org.apache.ignite.stream.kafka.connect.IgniteSinkTask:96)
When I printed the streamed record i got the following result : key=null
SinkRecord{kafkaOffset=2, timestampType=CreateTime}
ConnectRecord{topic='ignitetest', kafkaPartition=2, key=null, value=k1,v1,
timestamp=1478690650016}
I wish to have a functionality to extracting keys from values or any work
around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4183) ODBC: empty value in a particular row breaks reading other rows in the column
[ https://issues.apache.org/jira/browse/IGNITE-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-4183: --- Assignee: Igor Sapego (was: Vladimir Ozerov) LGTM. > ODBC: empty value in a particular row breaks reading other rows in the column > - > > Key: IGNITE-4183 > URL: https://issues.apache.org/jira/browse/IGNITE-4183 > Project: Ignite > Issue Type: Bug > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > To reproduce, > * first create cache without empty values and ensure that all values are > properly exposed via ODBC > * next make some value(s) in original cache null, try it again and verify > whether ODBC exposes more null values than expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650777#comment-15650777
]
Anton Vinogradov edited comment on IGNITE-3748 at 11/9/16 12:21 PM:
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
if (part != null)
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
This code will allow another partitions to be evicted in proper way and, as
well, will log exception.
was (Author: avinogradov):
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
if (part != null)
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
This code will allow another partitions to be evicted in proper way and, as
well will log exception.
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650777#comment-15650777
]
Anton Vinogradov edited comment on IGNITE-3748 at 11/9/16 12:21 PM:
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
if (part != null)
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
This code will allow another partitions to be evicted in proper way and, as
well will log exception.
was (Author: avinogradov):
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
if (part != null)
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650777#comment-15650777
]
Anton Vinogradov edited comment on IGNITE-3748 at 11/9/16 12:19 PM:
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
if (part != null)
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
was (Author: avinogradov):
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650777#comment-15650777
]
Anton Vinogradov edited comment on IGNITE-3748 at 11/9/16 12:18 PM:
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{noformat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
was (Author: avinogradov):
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{nofirmat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650777#comment-15650777
]
Anton Vinogradov commented on IGNITE-3748:
--
Possible, problem at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader#evictPartitionAsync
{nofirmat}
if (part != null)
part.tryEvict();
{noformat}
should be replaced with
{noformat}
try {
part.tryEvict();
}
catch (Throwable ex) {
LT.error(log, ex, "Partition eviction failed, this can cause grid hang.");
}
{noformat}
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3748) Data rebalancing of large cache can hang out.
[
https://issues.apache.org/jira/browse/IGNITE-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-3748:
Assignee: Anton Vinogradov
> Data rebalancing of large cache can hang out.
> -
>
> Key: IGNITE-3748
> URL: https://issues.apache.org/jira/browse/IGNITE-3748
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Anton Vinogradov
> Attachments: Apache.config.xml, default-config.xml, logs.zip,
> thread_dump.zip
>
>
> After the node (_CO3SCH050520537_) disconnect from cluster and starts again,
> rebalacing partitions of cache works, until node will faill by timeout.
> In the log of node which joining:
> {noformat}
> [2016.08.17 03:28:52,754 PDT][INFO
> ][sys-#122%null%][GridDhtPartitionDemander] Completed
> (final) rebalancing [cache=cache_raw_gbievent,
> fromNode=14666739-08e3-4188-ace7-9e47940bed70,
> topology=AffinityTopologyVersion [topVer=205, minorTopVer=0], time=336336 ms]
> {noformat}
> In other server nodes:
> {noformat}
> [2016.08.17 03:29:04,413 PDT][WARN
> ][exchange-worker-#176%null%][GridDhtPartitionsExchangeFuture] Failed to wait
> for partition release future [topVer=AffinityTopologyVersion [topVer=205,
> minorTopVer=1], node=14666739-08e3-4188-ace7-9e47940bed70].
> {noformat}
> See [the thread for details |
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tt6252.html#a7171]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions
[ https://issues.apache.org/jira/browse/IGNITE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650767#comment-15650767 ] Andrew Mashenkov commented on IGNITE-4106: -- It seems that Every query thread read full node index and then filter data within its own partition subset. Thus, query splitted to several threads will induce full node index to be read once per partition subset. In current (1 thread per node) approach, all query threads work with its own smaller index. > SQL: parallelize sql queries over cache local partitions > > > Key: IGNITE-4106 > URL: https://issues.apache.org/jira/browse/IGNITE-4106 > Project: Ignite > Issue Type: Improvement > Components: SQL >Affects Versions: 1.6, 1.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Labels: performance > Attachments: 1node-4thread.jfr, 4node-1thread.jfr > > > If we run SQL query on cache partitioned over several cluster nodes, it will > be split into several queries running in parallel. But really we will have > one thread per query on each node. > So, for now, to improve SQL query performance we need to run more Ignite > instances or split caches manually. > It seems to be better to split local SQL queries over cache partitions, so we > would be able to parallelize SQL query on every single node and utilize CPU > more efficiently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3812) Add executors configuration validation.
[ https://issues.apache.org/jira/browse/IGNITE-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov reassigned IGNITE-3812: Assignee: Semen Boikov (was: Andrew Mashenkov) > Add executors configuration validation. > --- > > Key: IGNITE-3812 > URL: https://issues.apache.org/jira/browse/IGNITE-3812 > Project: Ignite > Issue Type: Task >Affects Versions: 1.6 >Reporter: Andrew Mashenkov >Assignee: Semen Boikov > Labels: newbie, trivial > > An IllegalArgumentException will be thrown from one of java standard > implementation of ThreadPool without any information about wrong parameter > if incorrect value provided (e.g. if set threadPoolSize <= 0). So, it is not > obvious which executor service initialization has failed. > See IgnitionEx.IgniteNamedInstance class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3812) Add executors configuration validation.
[ https://issues.apache.org/jira/browse/IGNITE-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander reassigned IGNITE-3812: - Assignee: Andrew Mashenkov (was: Alexander) > Add executors configuration validation. > --- > > Key: IGNITE-3812 > URL: https://issues.apache.org/jira/browse/IGNITE-3812 > Project: Ignite > Issue Type: Task >Affects Versions: 1.6 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Labels: newbie, trivial > > An IllegalArgumentException will be thrown from one of java standard > implementation of ThreadPool without any information about wrong parameter > if incorrect value provided (e.g. if set threadPoolSize <= 0). So, it is not > obvious which executor service initialization has failed. > See IgnitionEx.IgniteNamedInstance class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1051) node.js: create nodejs examples
[ https://issues.apache.org/jira/browse/IGNITE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-1051: Fix Version/s: (was: 1.8) 2.2 > node.js: create nodejs examples > --- > > Key: IGNITE-1051 > URL: https://issues.apache.org/jira/browse/IGNITE-1051 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Semen Boikov >Assignee: Andrey Gura > Fix For: 2.2 > > Attachments: ignite-961_ignite-1051.patch > > > Need to create examples for all implemented nodejs features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-962) node.js: provide json cache object implementation
[ https://issues.apache.org/jira/browse/IGNITE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-962: --- Fix Version/s: (was: 1.8) 2.2 > node.js: provide json cache object implementation > - > > Key: IGNITE-962 > URL: https://issues.apache.org/jira/browse/IGNITE-962 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 2.2 > > > * check if we can optimize strings store with storing byte arrays > * implement SQL indexing support for new object -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-966) node.js: documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-966: --- Fix Version/s: (was: 1.8) 2.2 > node.js: documentation on readme.io > --- > > Key: IGNITE-966 > URL: https://issues.apache.org/jira/browse/IGNITE-966 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 2.2 > > > http://apacheignite.readme.io/v1.2/docs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-965) node.js: provide npm package
[ https://issues.apache.org/jira/browse/IGNITE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-965: --- Fix Version/s: (was: 1.8) 2.2 > node.js: provide npm package > > > Key: IGNITE-965 > URL: https://issues.apache.org/jira/browse/IGNITE-965 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Assignee: Andrey Gura > Fix For: 2.2 > > > Need to investigate how packages are built and shared. > The result should be a script or automated procedure that build and share the > package -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2437) Zeppelin interperet doesn't import external dependencies
[
https://issues.apache.org/jira/browse/IGNITE-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-2437:
Fix Version/s: (was: 1.8)
> Zeppelin interperet doesn't import external dependencies
>
>
> Key: IGNITE-2437
> URL: https://issues.apache.org/jira/browse/IGNITE-2437
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
> Environment: zeppelin 0.5.5
> ignite 1.5.0.final
>Reporter: Konstantin Boudnik
>Assignee: Andrey Gura
>
> After configuring Ignite's interpreter for Zeppelin, tried to run the
> following
> {code}
> %dep
> z.load("/usr/lib/ignite/libs/ignite-cache-objects.jar")
> %ignite
> import io.company._
> console>:23: error: object company is not a member of package io
>import io.company._
> {code}
> same code works just fine in spark interpreter though.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3948) TTL manager continues to track evicted entries
[ https://issues.apache.org/jira/browse/IGNITE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650318#comment-15650318 ] ASF GitHub Bot commented on IGNITE-3948: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1101 > TTL manager continues to track evicted entries > -- > > Key: IGNITE-3948 > URL: https://issues.apache.org/jira/browse/IGNITE-3948 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Andrey Gura >Assignee: Vladimir Ozerov > Fix For: 1.8 > > > Cache uses only heap memory and has eviction and expiry policies. During > loading data into cache TTL manager consumes heap memory even if entries were > evicted because it still track this entries. > It's ok in case of offheap memory or/and swap are enabled but doesn't make > sense in case of using only heap memory. > See also > http://stackoverflow.com/questions/39447690/apache-ignite-cache-eviction-still-in-memory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[ https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650316#comment-15650316 ] ASF GitHub Bot commented on IGNITE-2355: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1153 > Hadoop client should be able to failover in case of server crash. > - > > Key: IGNITE-2355 > URL: https://issues.apache.org/jira/browse/IGNITE-2355 > Project: Ignite > Issue Type: Sub-task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > Fix For: 1.8 > > > Currently we explicitly specify a single IP address of Ignite server for map > reduce. > If it goes down, no jobs can be submitted anymore. > Looks like we should give user ability to specify multiple addresses, and > failover between them. Our thin client (which underlies Hadoop client) is > already able to accept multiple addresses. > Look at Hadoop HA first to get an ideas on how to configure multiple > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3645) IGFS: Local secondary: Implement update() operation.
[ https://issues.apache.org/jira/browse/IGNITE-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650312#comment-15650312 ] ASF GitHub Bot commented on IGNITE-3645: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1003 > IGFS: Local secondary: Implement update() operation. > > > Key: IGNITE-3645 > URL: https://issues.apache.org/jira/browse/IGNITE-3645 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.6 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3593) .NET: IgniteConfiguration.WorkDirectory has no effect
[ https://issues.apache.org/jira/browse/IGNITE-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650314#comment-15650314 ] ASF GitHub Bot commented on IGNITE-3593: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1145 > .NET: IgniteConfiguration.WorkDirectory has no effect > - > > Key: IGNITE-3593 > URL: https://issues.apache.org/jira/browse/IGNITE-3593 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov >Priority: Minor > Fix For: 1.8 > > > Temporary marshaller is created during startup, it sets the work dir, and it > can't be changed after that (static state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3163) IGFS: Add working directory notion.
[ https://issues.apache.org/jira/browse/IGNITE-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650315#comment-15650315 ] ASF GitHub Bot commented on IGNITE-3163: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1132 > IGFS: Add working directory notion. > --- > > Key: IGNITE-3163 > URL: https://issues.apache.org/jira/browse/IGNITE-3163 > Project: Ignite > Issue Type: Task > Components: IGFS >Affects Versions: 1.5.0.final >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: important > Fix For: 1.8 > > > Currently when user configure secondary file system, it provides URI. We do > not use path of this URI and rely only on authority component. For this > reason "file:///" and "file:///path/" setting will be processed in the same > We need to respect path component as well and append it so that use can use > relative paths easily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4060) RoundRobinLoadBalancingSpi doesn't work after client reconnect.
[
https://issues.apache.org/jira/browse/IGNITE-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650317#comment-15650317
]
ASF GitHub Bot commented on IGNITE-4060:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1157
> RoundRobinLoadBalancingSpi doesn't work after client reconnect.
> ---
>
> Key: IGNITE-4060
> URL: https://issues.apache.org/jira/browse/IGNITE-4060
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
> Attachments: RoundRodbinErrorReproducer.java
>
>
> If {{IgntieCompute.apply()}} is called on a client after reconnect, it fails.
> Reproducer code is attached. The problem is that
> {{RoundRobinLoadBalancingSpi}} (which is default one) is not notified about
> topology reset.
> Sample stack trace:
> {code}
> class org.apache.ignite.IgniteException: Task topology does not have alive
> nodes: [TcpDiscoveryNode [id=50f56f53-bbf6-4d66-bfc5-02d801241e14,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1476269284697, loc=false,
> ver=1.7.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.checkBalancerNodes(RoundRobinGlobalLoadBalancer.java:256)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinGlobalLoadBalancer.getBalancedNode(RoundRobinGlobalLoadBalancer.java:201)
> at
> org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpi.getBalancedNode(RoundRobinLoadBalancingSpi.java:307)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager.getBalancedNode(GridLoadBalancerManager.java:81)
> at
> org.apache.ignite.internal.managers.loadbalancer.GridLoadBalancerManager$1.getBalancedNode(GridLoadBalancerManager.java:99)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1616)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$T8.map(GridClosureProcessor.java:1587)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:519)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$2.call(GridTaskWorker.java:517)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6509)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:516)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:679)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:403)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:630)
> at
> org.apache.ignite.internal.IgniteComputeImpl.apply(IgniteComputeImpl.java:451)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3972) Continuous query events could be lost on backup node when primary leaves (atomic cache).
[
https://issues.apache.org/jira/browse/IGNITE-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650313#comment-15650313
]
ASF GitHub Bot commented on IGNITE-3972:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1133
> Continuous query events could be lost on backup node when primary leaves
> (atomic cache).
>
>
> Key: IGNITE-3972
> URL: https://issues.apache.org/jira/browse/IGNITE-3972
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.8
>
>
> Consider the following scenario:
> 1) One node in topology;
> 2) PARTITIONED cache with 1 backup;
> 3) Continuous query is set on the cache;
> If another node joins the cluster, it will handle some updates. If it leaves
> the topology, the first node must flush it's own events from backup queue
> thus ensuring that no events are lost.
> But this doesn't happen because
> {{GridContinuousProcessor.addBackupNotification}} method perform lookup only
> on remote infos map, while handler is local and hence located in local infos
> map.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4145) "No query result found for request" exception when running multiple queries concurrently.
[ https://issues.apache.org/jira/browse/IGNITE-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650161#comment-15650161 ] ASF GitHub Bot commented on IGNITE-4145: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1220 IGNITE-4145: "No query result found for request" exception when running multiple queries concurrently. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4145 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1220.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 #1220 commit a4c63ae113931615e940ada2411ebce32dba5db8 Author: iveselovskiy Date: 2016-09-30T07:45:13Z IGNITE-3998: IGFS: Enabled IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129. commit a12298c0baf19407f3110ba3c4f0aab88b67946d Author: Igor Sapego Date: 2016-09-30T08:00:51Z IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051. commit 5e7ef8644ad824b87d4797e59133eb783ff8b098 Author: vozerov-gridgain Date: 2016-10-03T07:37:25Z Merge branch 'ignite-1.6.9' into ignite-1.6.10 commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f Author: vozerov-gridgain Date: 2016-10-03T07:40:04Z IGNITE-2881: Fixed SPI queries. commit 0b66d2d7b695cf370a4b8a717844ad67742c6090 Author: sboikov Date: 2016-10-03T09:04:03Z ignite-3601 Do not check version on commit for read-only serializable transactions. commit 9f211e413332931f0fb1190744ddd7c7f38fd213 Author: tledkov-gridgain Date: 2016-10-03T09:26:12Z IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This closes #1003. commit fa698d6fcfde0006423ef009337dbef58ac62515 Author: vozerov-gridgain Date: 2016-10-03T10:33:12Z Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by multicast IP finder. commit bba019fd5076412ca43c10a32fd300b6031ccd0b Author: vozerov-gridgain Date: 2016-10-03T14:25:20Z IGNITE-3980: Processed failing tests in query suites. This closes #1137. commit a92f20b5cc75e6b80b2731da0192723526b0c1dc Author: vozerov-gridgain Date: 2016-10-04T11:10:26Z IGNITE-3597: Removed static work directory. commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1 Author: vozerov-gridgain Date: 2016-10-06T07:14:59Z IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130. commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497 Author: tledkov-gridgain Date: 2016-10-06T07:22:50Z IGNITE-3163 IGFS: Added working directory support to IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This closes #1132. commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701 Author: vozerov-gridgain Date: 2016-10-06T09:03:48Z IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This closes #903. This closes #1145. commit 952be8b995050b34379006dd6e739da3fe3b49e3 Author: Dmitriy Govorukhin Date: 2016-10-07T12:00:09Z Squashed commit of the following: commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1 Author: sboikov Date: Fri Oct 7 13:08:38 2016 +0300 minor commit 7fe88a1cb21f794ee55a176ab36d895cbf916528 Author: Dmitriy Govorukhin Date: Thu Oct 6 11:11:24 2016 +0300 ignite-update-notifier fix after review (cherry picked from commit a10d2ff) commit f2de749f958a3b18dc479f8a5517d7bf9362b933 Author: Dmitriy Govorukhin Date: Tue Oct 4 12:12:08 2016 +0300 ignite-2079-2 optimize import and change url path (cherry picked from commit 830a3cf) commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9 Author: Dmitriy Govorukhin Date: Thu Sep 29 19:54:54 2016 +0300 update-notifier remove parse xml, now parse like properties (cherry picked from commit 9ecaa29) commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b Author: Dmitriy Govorukhin Date: Tue Sep 27 17:07:21 2016 +0300 remove dom parser (cherry picked from commit d1653b2) commit b9c776a8423471706ecb1dc6176b38f23e799077 Author: Anton Vinogradov Date: 2016-10-10T08:52:57Z IGNITE-3235 Failed to initialize primitive boolean cache property of superclass commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06 Author: vozerov-gridgain Date: 2016-10-11T07:23:01Z IGNITE-4041: Created separate processor for thread pools and refactored IO manager. This closes #1150. commit 9a6cfce659df40b0a4624f19fd91c217b74bafea Author: nikolay_tikhonov Date: 2016-10-11T10:59:57Z IGNITE-4014 Fixed "Transaction hangs if entry processor failed during serialization". This closes #1148. commit 1938a17b01f
