[jira] [Commented] (IGNITE-6444) Validate that copyOnRead flag is configured with on-heap cache enabled
[ https://issues.apache.org/jira/browse/IGNITE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177565#comment-16177565 ] Roman Shtykh commented on IGNITE-6444: -- [~agoncharuk] Alex, I was looking at the issue, and I have a question. As I see, system caches such as _ignite-sys-cache_ are set to _copyOnRead == false_. Is it safe, considering they are off-heap? > Validate that copyOnRead flag is configured with on-heap cache enabled > -- > > Key: IGNITE-6444 > URL: https://issues.apache.org/jira/browse/IGNITE-6444 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Roman Shtykh > Labels: usability > Fix For: 2.3 > > > Link to the user-list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-1-0-CopyOnRead-Problem-td17009.html > It makes sense to validate the flag and print out a warning if on-heap cache > is disabled. I do not think that we should prevent node from startup because > this may break existing deployments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-898) Ignite does not starts from folder which name contains space
[ https://issues.apache.org/jira/browse/IGNITE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176697#comment-16176697 ] Aleksei Zaitsev edited comment on IGNITE-898 at 9/22/17 8:33 PM: - [~avinogradov], please review my changes. PR: https://github.com/apache/ignite/pull/2714 Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-351 was (Author: alexzaitzev): [~avinogradov], please review my changes. PR: https://github.com/apache/ignite/pull/2714 > Ignite does not starts from folder which name contains space > > > Key: IGNITE-898 > URL: https://issues.apache.org/jira/browse/IGNITE-898 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Aleksei Zaitsev >Priority: Trivial > Fix For: 2.3 > > > Observed: > In case folder name contains space character Ignite node cannot be started. > Expected: > Ingine node should be startable even when folder name contains space > character. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()
[
https://issues.apache.org/jira/browse/IGNITE-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-6485:
---
Assignee: Vladimir Ozerov
> Binary marshaller fails on deserialization of object with writeReplace()
>
>
> Key: IGNITE-6485
> URL: https://issues.apache.org/jira/browse/IGNITE-6485
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.3
>
>
> The problem found during testing vertx-ignite project with new version of
> Vert.x framework.
> Binary marshaller fails on deserialization of object with writeReplace()
> because deserialized object can't be assigned to field due to a type
> incompatibility.
> During setting field value the following checking will be failed in
> {{UnsafeObjectFieldAccessorImpl.set(Object var1, Object var2)}} method (see
> comment):
> {code:java}
> public void set(Object var1, Object var2) throws
> IllegalArgumentException, IllegalAccessException {
> this.ensureObj(var1);
> if (this.isFinal) {
> this.throwFinalFieldIllegalAccessException(var2);
> }
> // HERE: Field type isn't assignable from object type.
> if (var2 != null &&
> !this.field.getType().isAssignableFrom(var2.getClass())) {
> this.throwSetIllegalArgumentException(var2);
> }
> unsafe.putObject(var1, this.fieldOffset, var2);
> }
> {code}
> The following error will be logged:
> {noformat}
> class org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserialize(BinaryObjectImpl.java:639)
> at
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest.testUnmarshal(BinaryMarshallerReplaceObjectTest.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> read field [name=val]
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:168)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
> ... 14 more
> Caused by: java.lang.IllegalArgumentException: Can not set
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Intf
> field
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject.val
> to org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Cls
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
> at
> sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
> at java.lang.reflect.Field.set(Field.java:741)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:683)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
> ... 15 more
> {noformat}
> Minimal reproducer:
> {code:java}
> package org.apache.ignite.internal.binary;
> import java.io.Serializable;
> import java.util.Arrays;
> import java.util.Collection;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.binary.BinaryIdMapper;
> import org.apache.ignite.binary.Binar
[jira] [Created] (IGNITE-6489) Expiration Policies and Durable Memory Doc
Denis Magda created IGNITE-6489: --- Summary: Expiration Policies and Durable Memory Doc Key: IGNITE-6489 URL: https://issues.apache.org/jira/browse/IGNITE-6489 Project: Ignite Issue Type: Task Reporter: Denis Magda Assignee: Alexey Goncharuk Priority: Blocker We must make sure that the existing expiration policies documentation [1] makes sense for the off-heap space of the durable memory: https://apacheignite.readme.io/docs/expiry-policies -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-6325) Need to update the GitHub page
[ https://issues.apache.org/jira/browse/IGNITE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg resolved IGNITE-6325. - Resolution: Fixed Fixed. > Need to update the GitHub page > -- > > Key: IGNITE-6325 > URL: https://issues.apache.org/jira/browse/IGNITE-6325 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Dmitriy Setrakyan >Assignee: Prachi Garg > Fix For: 2.3 > > > GitHub is #1 referrer to our website and the content there is obsolete. You > need to update the readme.md with the latest content, reflecting persistence > and SQL database, etc. > Also, we should: > #Make sure that the Ignite logo links to the Ignite website > #Make sure that we have various sections in readme.md link to Ignite specific > pages, e.g. data grid, sql database, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-6325) Need to update the GitHub page
[ https://issues.apache.org/jira/browse/IGNITE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg closed IGNITE-6325. --- > Need to update the GitHub page > -- > > Key: IGNITE-6325 > URL: https://issues.apache.org/jira/browse/IGNITE-6325 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Dmitriy Setrakyan >Assignee: Prachi Garg > Fix For: 2.3 > > > GitHub is #1 referrer to our website and the content there is obsolete. You > need to update the readme.md with the latest content, reflecting persistence > and SQL database, etc. > Also, we should: > #Make sure that the Ignite logo links to the Ignite website > #Make sure that we have various sections in readme.md link to Ignite specific > pages, e.g. data grid, sql database, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5732) Provide API to test compatibility with old releases
[
https://issues.apache.org/jira/browse/IGNITE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176713#comment-16176713
]
ASF GitHub Bot commented on IGNITE-5732:
Github user daradurvs closed the pull request at:
https://github.com/apache/ignite/pull/2410
> Provide API to test compatibility with old releases
> ---
>
> Key: IGNITE-5732
> URL: https://issues.apache.org/jira/browse/IGNITE-5732
> Project: Ignite
> Issue Type: New Feature
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.3
>
>
> Need to provide an opportunity to test compatibility with old releases.
> The main idea is the method {code}startGrid(ver){code} in the testing
> framework, which would start an instance via downloaded "jar" from the Maven
> repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5810) Implement configuration import to xml
[
https://issues.apache.org/jira/browse/IGNITE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksei Zaitsev reassigned IGNITE-5810:
---
Assignee: Aleksei Zaitsev
> Implement configuration import to xml
> -
>
> Key: IGNITE-5810
> URL: https://issues.apache.org/jira/browse/IGNITE-5810
> Project: Ignite
> Issue Type: New Feature
>Reporter: Yakov Zhdanov
>Assignee: Aleksei Zaitsev
> Labels: usability
>
> When investigating failures having the entire grid configuration is a must.
> Now Ignite lacks this feature which would be very cool for deployments
> configured from code.
> I suggest to implement {{public String Ignite.configurationAsXml();}} and add
> ability to output files and gather them to MBeans and web console.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-898) Ignite does not starts from folder which name contains space
[ https://issues.apache.org/jira/browse/IGNITE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176697#comment-16176697 ] Aleksei Zaitsev commented on IGNITE-898: [~avinogradov], please review my changes. PR: https://github.com/apache/ignite/pull/2714 > Ignite does not starts from folder which name contains space > > > Key: IGNITE-898 > URL: https://issues.apache.org/jira/browse/IGNITE-898 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Aleksei Zaitsev >Priority: Trivial > Fix For: 2.3 > > > Observed: > In case folder name contains space character Ignite node cannot be started. > Expected: > Ingine node should be startable even when folder name contains space > character. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6484) Fix IgnitePdsThreadInterruptionTest failure with larger number of threads.
[ https://issues.apache.org/jira/browse/IGNITE-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176314#comment-16176314 ] Alexei Scherbakov edited comment on IGNITE-6484 at 9/22/17 4:18 PM: writeComplete conditional wait is made uninterruptable. was (Author: ascherbakov): writeComplete conditinal wait is made uninterruptable. > Fix IgnitePdsThreadInterruptionTest failure with larger number of threads. > -- > > Key: IGNITE-6484 > URL: https://issues.apache.org/jira/browse/IGNITE-6484 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 2.3 > > > Test fails on interruptions of conditional wait. > Related ticket IGNITE-6228 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6468) ODBC: Add tests for SQLGetInfo
[
https://issues.apache.org/jira/browse/IGNITE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176593#comment-16176593
]
ASF GitHub Bot commented on IGNITE-6468:
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2733
IGNITE-6468: Added tests. Fixed some issues
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6468
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2733.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 #2733
commit 91750e282bbbeda712f04a5edde0af839766
Author: Igor Sapego
Date: 2017-09-22T15:35:57Z
IGNITE-6468: Added tests. Fixed some issues
> ODBC: Add tests for SQLGetInfo
> --
>
> Key: IGNITE-6468
> URL: https://issues.apache.org/jira/browse/IGNITE-6468
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
>Affects Versions: 2.1
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 2.3
>
>
> Since we fully implemented {{SQLGetInfo}} (IGNITE-6099) we need proper tests
> for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6457:
---
Assignee: Taras Ledkov (was: Ilya Suntsov)
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.con
[jira] [Assigned] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6457:
---
Assignee: Ilya Suntsov (was: Vladimir Ozerov)
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.
[jira] [Commented] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176573#comment-16176573
]
Vladimir Ozerov commented on IGNITE-6457:
-
[~ustas], [~avolkov]
The problem is that you create a cache without a single query entity. Currently
we treat such caches as SQL-disabled, and do not create relevant schema. Please
add the following to config and it should work:
{code}
java.lang.Integer
java.lang.String
{code}
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Vladimir Ozerov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java
[jira] [Created] (IGNITE-6488) Add info message for index rebuild
Alexey Goncharuk created IGNITE-6488: Summary: Add info message for index rebuild Key: IGNITE-6488 URL: https://issues.apache.org/jira/browse/IGNITE-6488 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 2.1 Reporter: Alexey Goncharuk Assignee: Alexey Goncharuk Fix For: 2.3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6457:
---
Assignee: Vladimir Ozerov (was: Ilya Suntsov)
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Vladimir Ozerov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexi
[jira] [Commented] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176546#comment-16176546
]
Vladimir Ozerov commented on IGNITE-6457:
-
[~ustas], please provide details.
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.pro
[jira] [Assigned] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6457:
---
Assignee: Ilya Suntsov (was: Taras Ledkov)
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.con
[jira] [Commented] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology
[
https://issues.apache.org/jira/browse/IGNITE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176512#comment-16176512
]
Evgenii Zhuravlev commented on IGNITE-4173:
---
Agreed with Denis, I think we need to think how we can fix it.
[~vladisav], what do you think, is it a big change in code?
> IgniteSemaphore with failoverSafe enabled doesn't release permits in case
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology
[
https://issues.apache.org/jira/browse/IGNITE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176506#comment-16176506
]
Denis Mekhanikov commented on IGNITE-4173:
--
[~vladisav] currently if a node, that exclusively holds a semaphore, leaves,
then another node will not be able to acquire it. This is not an expected
behavior.
Judging by javadoc, semaphores should be released anyway, even if it was the
only node that held the semaphore instance.
> IgniteSemaphore with failoverSafe enabled doesn't release permits in case
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (IGNITE-6457) Incorrect exception when used schema name in lower case
[
https://issues.apache.org/jira/browse/IGNITE-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov reopened IGNITE-6457:
--
Re-tested on 5ca969dd. Wasn't fix.
> Incorrect exception when used schema name in lower case
>
>
> Key: IGNITE-6457
> URL: https://issues.apache.org/jira/browse/IGNITE-6457
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
> Environment: Cache configuration:
> {noformat}
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
> {noformat}
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Labels: usability
> Fix For: 2.3
>
>
> Scenario:
> 1. Start 1 node
> 2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
> {noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
> 3. Create table:
> {noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
> Result:
> {noformat}
> [16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed
> to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test,
> pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY,
> name VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to set schema for DB connection for thread [schema=test]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL
> statement:
> SET SCHEMA "test" [90079-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.engine.Database.getSchema(Database.java:1755)
> at org.h2.command.dml.Set.update(Set.java:408)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at
> org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
> at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(Ignite
[jira] [Reopened] (IGNITE-6448) Select * doesn't return new field name after concurrent ALTER TABLE
[
https://issues.apache.org/jira/browse/IGNITE-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov reopened IGNITE-6448:
--
Re-tesred. Works only for 1 connect.
> Select * doesn't return new field name after concurrent ALTER TABLE
>
>
> Key: IGNITE-6448
> URL: https://issues.apache.org/jira/browse/IGNITE-6448
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.3
>
>
> Steps for reproduce:
> 1. Start 3 nodes
> 2. Execute
> {noformat}CREATE TABLE person (id LONG, name VARCHAR, city_id LONG, PRIMARY
> KEY (id, city_id)) {noformat}
> to create table Person
> 3. Connect to grid via sqlline (https://github.com/julianhyde/sqlline)
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:thin://127.0.0.1/{noformat}
> 4. Create one more connection {noformat}!connect
> jdbc:ignite:thin://127.0.0.1/ {noformat}
> 5. Execute ALTER TABLE for both connections {noformat} !all alter table
> person add field1 varchar;{noformat}
> Result:
> 1. Got exception on coordinator:
> {noformat}[10:59:15,805][SEVERE][client-connector-#55%null%][JdbcRequestHandler]
> Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
> [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=alter table person add
> field1 varchar, args=[], stmtType=ANY_STATEMENT_TYPE]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Column
> already exists: FIELD1
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:329)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:273)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1383)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> 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)
> {noformat}
> 2. When I try to get all data from Person:
> {noformat}select * from person;{noformat}
> I get the table without new field but if try to get only this field from
> table it works.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6313) transaction hangs while node left cluster
[ https://issues.apache.org/jira/browse/IGNITE-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Lantukh reassigned IGNITE-6313: Assignee: Ilya Lantukh (was: Semen Boikov) > transaction hangs while node left cluster > - > > Key: IGNITE-6313 > URL: https://issues.apache.org/jira/browse/IGNITE-6313 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stanilovsky Evgeny >Assignee: Ilya Lantukh > Attachments: run.py, tpre.tar.gz, trun.tar.gz, > TxDeadLockOnNodeRestart.java > > > in attached reproducer there are 2 projects, > first - tpre simple fills cache > second - trun concurrently update cache values. > expected behavior 100 or sometimes 99 numbers in output, but after several > grid autorestart python script we found grid have no active transactions ... > try to find time for pure ignite reproducer, but for now it need be run like : > sequentially start: > *java -jar tpre-1.0-SNAPSHOT-jar-with-dependencies.jar 1000 > java -jar trun-1.0-SNAPSHOT-jar-with-dependencies.jar 1000 20 1 > run.py* > console with *trun* process will soon output something like : BBB that > signals no transactions found. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6487) During exchange affinity may return more backups than set
[ https://issues.apache.org/jira/browse/IGNITE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-6487: Summary: During exchange affinity may return more backups than set (was: Affinity may return more backups than set during exchange) > During exchange affinity may return more backups than set > -- > > Key: IGNITE-6487 > URL: https://issues.apache.org/jira/browse/IGNITE-6487 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.1 >Reporter: Dmitry Karachentsev > Attachments: GridCacheRebalanceBackupsTest.java > > > Reproducer is in attachment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6487) Affinity may return more backups than set during exchange
[ https://issues.apache.org/jira/browse/IGNITE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-6487: Summary: Affinity may return more backups than set during exchange (was: Affinity may return more backups that set during exchange) > Affinity may return more backups than set during exchange > - > > Key: IGNITE-6487 > URL: https://issues.apache.org/jira/browse/IGNITE-6487 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.1 >Reporter: Dmitry Karachentsev > Attachments: GridCacheRebalanceBackupsTest.java > > > Reproducer is in attachment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6474) Non-collocated IgniteSet stores duplicate values
[
https://issues.apache.org/jira/browse/IGNITE-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Mekhanikov updated IGNITE-6474:
-
Description:
Non-collocated IgniteSet shows multiple instances of the same objects when
populated from different nodes.
This code, when run twice on different nodes, results in more than 10 elements
in set:
{code:java}
CollectionConfiguration setCfg = new CollectionConfiguration();
setCfg.setCacheMode(PARTITIONED);
IgniteSet set = ignite.set("set", setCfg);
System.out.println("Set size before init: " + set.size());
for (int j = 0; j < 10; j++) {
set.add(j);
System.out.println(new ArrayList<>(set));
}
System.out.println("Set size after init: " + set.size());
{code}
Collocated set seems to work as expected. Populating from one node also doesn't
create duplicates.
was:
Here is the problem description in
[stackoverflow|https://stackoverflow.com/questions/46343833/unexpected-behavior-of-igniteset-in-official-example]
I tried to run org.apache.ignite.examples.datastructures.IgniteSetExample on
cluster(2 nodes) after adding some my debug code. Some of its source code like
following:
CollectionConfiguration setCfg = new CollectionConfiguration();
setCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
setCfg.setCacheMode(CacheMode.PARTITIONED);
// Initialize new set.
IgniteSet set = ignite.set(setName, setCfg);
System.out.println("Set size before initializing: " + set.size()); //added by
myslef
// Initialize set items.
for (int i = 0; i < 10; i++){
set.add(Integer.toString(i));
System.out.println("Set: " + Arrays.toString(set.toArray())); //added by
myslef
}
System.out.println("Set size after initializing: " + set.size());
In my opinion, the size of ignite set should be 10 after adding data but I got
a number which is great than 10 and typically 15. I found that there was some
reduplicate numbers been added to the set. The log is here:
[19:53:16] Topology snapshot [ver=29, servers=2, clients=0, CPUs=8, heap=3.4GB]
Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
Info: Topology snapshot [ver=29, servers=2, clients=0, CPUs=8, heap=3.4GB]
>>> Ignite set example started.
Set size before initializing: 0
Set: [0]
Set: [1, 1, 0]
Set: [2, 1, 2, 1, 0]
Set: [2, 1, 3, 2, 1, 0, 3]
Set: [2, 1, 3, 2, 1, 0, 4, 3]
Set: [2, 1, 3, 2, 1, 0, 5, 4, 3]
Set: [2, 1, 3, 2, 1, 0, 6, 5, 4, 3]
Set: [7, 2, 1, 3, 7, 2, 1, 0, 6, 5, 4, 3]
Set: [7, 2, 1, 3, 8, 7, 2, 1, 0, 6, 5, 4, 3]
Set: [7, 2, 1, 3, 9, 8, 7, 2, 1, 0, 6, 5, 4, 3]
Set size after initializing: 14
Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
Info: Class locally deployed: class
org.apache.ignite.examples.datastructures.IgniteSetExample$SetClosure
Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
Info: Class locally deployed: class
org.apache.ignite.configuration.CollectionConfiguration
Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
Info: Class locally deployed: class org.apache.ignite.cache.CacheAtomicityMode
Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
Info: Class locally deployed: class org.apache.ignite.cache.CacheMode
Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_0
Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_4
Set size after writing [expected=20, actual=30]
Iterate over set.
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_1
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_3
Set item: 7
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_4
Set item: 2
Set item: 1
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
Set item: 3
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_4
Set item: 2
Set item: 1
Set item: 0
Set item: 6
Set item: 5
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_0
Set item: 4
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
Set item: 3
Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_1
Set item: 9
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_2
Set item: 8
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_3
Set item: 7
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_4
Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_0
Set size before clearing: 30
Set size after clearing: 0
Set was removed: true
Expected exception - Set has been removed from cache: GridCacheSetImpl
[cache=GridDhtAtomicCache
[defRes=org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$1@482d776b,
near=null, super=GridDhtCacheAdapter
[multiTxHolder=java.lang.ThreadLocal@186978a6, stopping=false,
[jira] [Updated] (IGNITE-6487) Affinity may return more backups that set during exchange
[ https://issues.apache.org/jira/browse/IGNITE-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Karachentsev updated IGNITE-6487: Attachment: GridCacheRebalanceBackupsTest.java > Affinity may return more backups that set during exchange > - > > Key: IGNITE-6487 > URL: https://issues.apache.org/jira/browse/IGNITE-6487 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.1 >Reporter: Dmitry Karachentsev > Attachments: GridCacheRebalanceBackupsTest.java > > > Reproducer is in attachment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6487) Affinity may return more backups that set during exchange
Dmitry Karachentsev created IGNITE-6487: --- Summary: Affinity may return more backups that set during exchange Key: IGNITE-6487 URL: https://issues.apache.org/jira/browse/IGNITE-6487 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.1 Reporter: Dmitry Karachentsev Reproducer is in attachment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6484) Fix IgnitePdsThreadInterruptionTest failure with larger number of threads.
[ https://issues.apache.org/jira/browse/IGNITE-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-6484: - Component/s: persistence > Fix IgnitePdsThreadInterruptionTest failure with larger number of threads. > -- > > Key: IGNITE-6484 > URL: https://issues.apache.org/jira/browse/IGNITE-6484 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.1 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 2.3 > > > Test fails on interruptions of conditional wait. > Related ticket IGNITE-6228 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6474) Non-collocated IgniteSet stores duplicate values
[
https://issues.apache.org/jira/browse/IGNITE-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Mekhanikov updated IGNITE-6474:
-
Summary: Non-collocated IgniteSet stores duplicate values (was:
Unexpected behavior of IgniteSet in Official example running on cluster)
> Non-collocated IgniteSet stores duplicate values
> -
>
> Key: IGNITE-6474
> URL: https://issues.apache.org/jira/browse/IGNITE-6474
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.1
> Environment: a ignite cluster with 2 nodes
>Reporter: DL Ren
>
> Here is the problem description in
> [stackoverflow|https://stackoverflow.com/questions/46343833/unexpected-behavior-of-igniteset-in-official-example]
> I tried to run org.apache.ignite.examples.datastructures.IgniteSetExample on
> cluster(2 nodes) after adding some my debug code. Some of its source code
> like following:
> CollectionConfiguration setCfg = new CollectionConfiguration();
> setCfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> setCfg.setCacheMode(CacheMode.PARTITIONED);
> // Initialize new set.
> IgniteSet set = ignite.set(setName, setCfg);
> System.out.println("Set size before initializing: " + set.size()); //added by
> myslef
> // Initialize set items.
> for (int i = 0; i < 10; i++){
> set.add(Integer.toString(i));
> System.out.println("Set: " + Arrays.toString(set.toArray())); //added by
> myslef
> }
> System.out.println("Set size after initializing: " + set.size());
> In my opinion, the size of ignite set should be 10 after adding data but I
> got a number which is great than 10 and typically 15. I found that there was
> some reduplicate numbers been added to the set. The log is here:
> [19:53:16] Topology snapshot [ver=29, servers=2, clients=0, CPUs=8,
> heap=3.4GB]
> Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
> Info: Topology snapshot [ver=29, servers=2, clients=0, CPUs=8, heap=3.4GB]
> >>> Ignite set example started.
> Set size before initializing: 0
> Set: [0]
> Set: [1, 1, 0]
> Set: [2, 1, 2, 1, 0]
> Set: [2, 1, 3, 2, 1, 0, 3]
> Set: [2, 1, 3, 2, 1, 0, 4, 3]
> Set: [2, 1, 3, 2, 1, 0, 5, 4, 3]
> Set: [2, 1, 3, 2, 1, 0, 6, 5, 4, 3]
> Set: [7, 2, 1, 3, 7, 2, 1, 0, 6, 5, 4, 3]
> Set: [7, 2, 1, 3, 8, 7, 2, 1, 0, 6, 5, 4, 3]
> Set: [7, 2, 1, 3, 9, 8, 7, 2, 1, 0, 6, 5, 4, 3]
> Set size after initializing: 14
> Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
> Info: Class locally deployed: class
> org.apache.ignite.examples.datastructures.IgniteSetExample$SetClosure
> Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
> Info: Class locally deployed: class
> org.apache.ignite.configuration.CollectionConfiguration
> Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
> Info: Class locally deployed: class org.apache.ignite.cache.CacheAtomicityMode
> Sep 21, 2017 7:53:16 PM org.apache.ignite.logger.java.JavaLogger info
> Info: Class locally deployed: class org.apache.ignite.cache.CacheMode
> Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_0
> Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
> Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
> Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
> Set item has been added: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_4
> Set size after writing [expected=20, actual=30]
> Iterate over set.
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_1
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_3
> Set item: 7
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_4
> Set item: 2
> Set item: 1
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
> Set item: 3
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_3
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_4
> Set item: 2
> Set item: 1
> Set item: 0
> Set item: 6
> Set item: 5
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_0
> Set item: 4
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_1
> Set item: 3
> Set item: 7aa983e1-c358-4876-b58f-4f3b7bfa65f3_2
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_1
> Set item: 9
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_2
> Set item: 8
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_3
> Set item: 7
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_4
> Set item: 292c99a6-137b-433c-97d9-40ce0f8c0abc_0
> Set size before clearing: 30
> Set size after clearing: 0
> Set was removed: true
> Expected exception - Set has been removed from cache: GridCacheSetImpl
> [cache=GridDhtAtomicCache
> [defRes=org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$1@482d776b,
> near=null, super=GridDhtCacheAdapter
> [multiTxHolder=java.l
[jira] [Updated] (IGNITE-6434) Error in checkpointer during topology change
[
https://issues.apache.org/jira/browse/IGNITE-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-6434:
-
Affects Version/s: 2.1
> Error in checkpointer during topology change
>
>
> Key: IGNITE-6434
> URL: https://issues.apache.org/jira/browse/IGNITE-6434
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> {code}
> 2017-09-11 21:35:22.195
> [ERROR][db-checkpoint-thread-#101%node1%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=db-checkpoint-thread, igniteInstanceName=node1, finished=false,
> hashCode=1326137503, interrupted=false,
> runner=db-checkpoint-thread-#101%node1%]
> java.lang.IllegalStateException: Failed to add new partition to the
> partitions state (no enough space reserved) [partId=459, reserved=459]
> at
> org.apache.ignite.internal.pagemem.wal.record.CacheState.addPartitionState(CacheState.java:50)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2189)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1954)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1879)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_121]
> {code}
> After checkpoint thread died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6434) Error in checkpointer during topology change
[
https://issues.apache.org/jira/browse/IGNITE-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-6434:
-
Fix Version/s: 2.3
> Error in checkpointer during topology change
>
>
> Key: IGNITE-6434
> URL: https://issues.apache.org/jira/browse/IGNITE-6434
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> {code}
> 2017-09-11 21:35:22.195
> [ERROR][db-checkpoint-thread-#101%node1%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=db-checkpoint-thread, igniteInstanceName=node1, finished=false,
> hashCode=1326137503, interrupted=false,
> runner=db-checkpoint-thread-#101%node1%]
> java.lang.IllegalStateException: Failed to add new partition to the
> partitions state (no enough space reserved) [partId=459, reserved=459]
> at
> org.apache.ignite.internal.pagemem.wal.record.CacheState.addPartitionState(CacheState.java:50)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2189)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1954)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1879)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_121]
> {code}
> After checkpoint thread died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6434) Error in checkpointer during topology change
[
https://issues.apache.org/jira/browse/IGNITE-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-6434:
-
Component/s: persistence
> Error in checkpointer during topology change
>
>
> Key: IGNITE-6434
> URL: https://issues.apache.org/jira/browse/IGNITE-6434
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.3
>
>
> {code}
> 2017-09-11 21:35:22.195
> [ERROR][db-checkpoint-thread-#101%node1%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=db-checkpoint-thread, igniteInstanceName=node1, finished=false,
> hashCode=1326137503, interrupted=false,
> runner=db-checkpoint-thread-#101%node1%]
> java.lang.IllegalStateException: Failed to add new partition to the
> partitions state (no enough space reserved) [partId=459, reserved=459]
> at
> org.apache.ignite.internal.pagemem.wal.record.CacheState.addPartitionState(CacheState.java:50)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2189)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1954)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1879)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_121]
> {code}
> After checkpoint thread died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-6434) Error in checkpointer during topology change
[
https://issues.apache.org/jira/browse/IGNITE-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-6434.
--
Resolution: Fixed
Thanks, Eduard, merged your changes to master
> Error in checkpointer during topology change
>
>
> Key: IGNITE-6434
> URL: https://issues.apache.org/jira/browse/IGNITE-6434
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Critical
>
> {code}
> 2017-09-11 21:35:22.195
> [ERROR][db-checkpoint-thread-#101%node1%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=db-checkpoint-thread, igniteInstanceName=node1, finished=false,
> hashCode=1326137503, interrupted=false,
> runner=db-checkpoint-thread-#101%node1%]
> java.lang.IllegalStateException: Failed to add new partition to the
> partitions state (no enough space reserved) [partId=459, reserved=459]
> at
> org.apache.ignite.internal.pagemem.wal.record.CacheState.addPartitionState(CacheState.java:50)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2189)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1954)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1879)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> ~[ignite-core-2.1.4.jar:2.1.4]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_121]
> {code}
> After checkpoint thread died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6286) org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters
[ https://issues.apache.org/jira/browse/IGNITE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176383#comment-16176383 ] Sergey Chernolyas commented on IGNITE-6286: --- reproduced for BigDecimal type. [2017-09-22 16:02:53,609][ERROR][query-#644%query.IgniteSqlParameterizedQueryTest0%][GridMapQueryExecutor] Failed to execute local query. class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:972) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1031) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1010) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:660) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:506) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:206) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$2.onMessage(GridMapQueryExecutor.java:166) at org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2332) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183) at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126) at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.h2.jdbc.JdbcSQLException: Шестнадцатиричная строка содержит нешестнадцатиричные символы: "1000.001" Hexadecimal string contains non-hex character: "1000.001"; SQL statement: SELECT __Z0._VAL __C0_0 FROM "Bookmark".BOOKMARK __Z0 WHERE __Z0.SITEWEIGHT = ?1 [90004-195] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:179) at org.h2.message.DbException.get(DbException.java:155) at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:946) at org.h2.value.Value.convertTo(Value.java:957) at org.h2.expression.Comparison.getValue(Comparison.java:264) at org.h2.expression.Expression.getBooleanValue(Expression.java:178) at org.h2.command.dml.Select.isConditionMet(Select.java:299) at org.h2.command.dml.Select.access$600(Select.java:64) at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1455) at org.h2.result.LazyResult.hasNext(LazyResult.java:79) at org.h2.result.LazyResult.next(LazyResult.java:59) at org.h2.command.dml.Select.queryFlat(Select.java:519) at org.h2.command.dml.Select.queryWithoutCache(Select.java:625) at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114) at org.h2.command.dml.Query.query(Query.java:352) at org.h2.command.dml.Query.query(Query.java:333) at org.h2.command.CommandContainer.query(CommandContainer.java:113) at org.h2.command.Command.executeQuery(Command.java:201) at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:965) > org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters > -- > > Key: IGNITE-6286 > URL: https://issues.apache.org/jira/browse/IGNITE-6286 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1 >Reporter: Sergey Chernolyas >Assignee: Sergey Chernolyas > > Incorrect binding of parameter's value for SQL queries with parameters. > The incorrection leads to exception "org.h2.jdbc.JdbcSQLException: > Hexadecimal string with odd number of characters" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-6286) org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters
[ https://issues.apache.org/jira/browse/IGNITE-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chernolyas updated IGNITE-6286: -- Comment: was deleted (was: Reproduce exception by test IgniteSqlParameterQueryTest __ [2017-09-21 23:17:58,873][ERROR][query-#184%query.IgniteSqlParameterQueryTest0%][GridMapQueryExecutor] Failed to execute local query. class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query. at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:970) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1029) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:1008) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:660) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:506) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:206) at org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$2.onMessage(GridMapQueryExecutor.java:166) at org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2332) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183) at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126) at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.h2.jdbc.JdbcSQLException: Шестнадцатиричная строка содержит нечетное количество символов: "100" Hexadecimal string with odd number of characters: "100"; SQL statement: SELECT __Z0._VAL __C0_0 FROM "Bookmark".BOOKMARK __Z0 WHERE __Z0.STOCKCOUNT = ?1 [90003-195] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:179) at org.h2.message.DbException.get(DbException.java:155) at org.h2.util.StringUtils.convertHexToBytes(StringUtils.java:930) at org.h2.value.Value.convertTo(Value.java:957) at org.h2.expression.Comparison.getValue(Comparison.java:264) at org.h2.expression.Expression.getBooleanValue(Expression.java:178) at org.h2.command.dml.Select.isConditionMet(Select.java:299) at org.h2.command.dml.Select.access$600(Select.java:64) at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1455) at org.h2.result.LazyResult.hasNext(LazyResult.java:79) at org.h2.result.LazyResult.next(LazyResult.java:59) at org.h2.command.dml.Select.queryFlat(Select.java:519) at org.h2.command.dml.Select.queryWithoutCache(Select.java:625) at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114) at org.h2.command.dml.Query.query(Query.java:352) at org.h2.command.dml.Query.query(Query.java:333) at org.h2.command.CommandContainer.query(CommandContainer.java:113) at org.h2.command.Command.executeQuery(Command.java:201) at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:963) ) > org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters > -- > > Key: IGNITE-6286 > URL: https://issues.apache.org/jira/browse/IGNITE-6286 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1 >Reporter: Sergey Chernolyas >Assignee: Sergey Chernolyas > > Incorrect binding of parameter's value for SQL queries with parameters. > The incorrection leads to exception "org.h2.jdbc.JdbcSQLException: > Hexadecimal string with odd number of characters" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6154) Incorrect check checkpoint pages collection
[ https://issues.apache.org/jira/browse/IGNITE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176373#comment-16176373 ] ASF GitHub Bot commented on IGNITE-6154: Github user DmitriyGovorukhin closed the pull request at: https://github.com/apache/ignite/pull/2497 > Incorrect check checkpoint pages collection > --- > > Key: IGNITE-6154 > URL: https://issues.apache.org/jira/browse/IGNITE-6154 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.3 > > > There is incorrect check !F.empty(collection) in checkpoint thread. > There should be a full check all elements, because collection is collection > of GridMultiCollectionWrapper, and we must check all mutlicollections. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-2662) .NET Standard support
[ https://issues.apache.org/jira/browse/IGNITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176361#comment-16176361 ] David Kaya commented on IGNITE-2662: Hi [~ptupitsyn], is there any update on .NET Standard and Core 2.0 support? > .NET Standard support > - > > Key: IGNITE-2662 > URL: https://issues.apache.org/jira/browse/IGNITE-2662 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Labels: .net > > Ignite.NET should target .NET Standard so it is available on maximum number > of platforms, see > https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ > https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again > https://github.com/dotnet/core/blob/master/roadmap.md > This will allow us to run on Windows, OSX, and Linux, and target .NET Core in > additional to good old regular .NET. > Possible difficulties: > * JNI interop. Core has dllImport and it works on linux, and our C++ client > works on linux, so it should be possible > * Reflection. We use it a lot, and API has changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-2662) .NET Standard support
[ https://issues.apache.org/jira/browse/IGNITE-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176361#comment-16176361 ] David Kaya edited comment on IGNITE-2662 at 9/22/17 12:53 PM: -- Hi [~ptupitsyn], is there any update on .NET Standard and Core 2.0 support? Thanks was (Author: dkaya): Hi [~ptupitsyn], is there any update on .NET Standard and Core 2.0 support? > .NET Standard support > - > > Key: IGNITE-2662 > URL: https://issues.apache.org/jira/browse/IGNITE-2662 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Labels: .net > > Ignite.NET should target .NET Standard so it is available on maximum number > of platforms, see > https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ > https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again > https://github.com/dotnet/core/blob/master/roadmap.md > This will allow us to run on Windows, OSX, and Linux, and target .NET Core in > additional to good old regular .NET. > Possible difficulties: > * JNI interop. Core has dllImport and it works on linux, and our C++ client > works on linux, so it should be possible > * Reflection. We use it a lot, and API has changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5903) .NET: Add tests for CREATE/DROP table/index
[
https://issues.apache.org/jira/browse/IGNITE-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-5903:
--
Assignee: (was: Pavel Tupitsyn)
> .NET: Add tests for CREATE/DROP table/index
> ---
>
> Key: IGNITE-5903
> URL: https://issues.apache.org/jira/browse/IGNITE-5903
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> CREATE/DROP table/index functionality is available in .NET via
> {{QueryFields}}, no changes required. Add tests to make sure it works as
> expected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6335) .NET: Thin client: cache binary mode
[
https://issues.apache.org/jira/browse/IGNITE-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-6335:
--
Assignee: (was: Pavel Tupitsyn)
> .NET: Thin client: cache binary mode
>
>
> Key: IGNITE-6335
> URL: https://issues.apache.org/jira/browse/IGNITE-6335
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{WithKeepBinary}}, all operations in binary mode, {{IIgnite.GetBinary()}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6216) .NET: Add CheckpointWriteOrder enum in persistent store configuration
[ https://issues.apache.org/jira/browse/IGNITE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-6216: -- Assignee: (was: Pavel Tupitsyn) > .NET: Add CheckpointWriteOrder enum in persistent store configuration > - > > Key: IGNITE-6216 > URL: https://issues.apache.org/jira/browse/IGNITE-6216 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.1 >Reporter: Ivan Rakov > Labels: .NET, MakeTeamcityGreenAgain, usability > Fix For: 2.3 > > > Since 2.2 we have CheckpointWriteOrder property in > PersistentStoreConfiguration. It should be possible to set through .NET > configuration classes. > Default value should be CheckpointWriteOrder#SEQUENTIAL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5885) .NET: Add x86 tests on TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-5885: -- Assignee: (was: Pavel Tupitsyn) > .NET: Add x86 tests on TeamCity > --- > > Key: IGNITE-5885 > URL: https://issues.apache.org/jira/browse/IGNITE-5885 > Project: Ignite > Issue Type: Task > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 2.3 > > > Just copy a configuration and change NUnit bitness. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6486) .NET: ActiveOnStart does not work
[
https://issues.apache.org/jira/browse/IGNITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176326#comment-16176326
]
Pavel Tupitsyn edited comment on IGNITE-6486 at 9/22/17 12:12 PM:
--
IGNITE-5717 related {{TODO}} s has been removed, tests cleaned up: custom
memory configuration is no longer necessary.
Waiting for TeamCity.
was (Author: ptupitsyn):
IGNITE-5717 related {{TODO}} s has been removed, tests cleaned up: custom
memory configuration is no longer necessary.
> .NET: ActiveOnStart does not work
> -
>
> Key: IGNITE-6486
> URL: https://issues.apache.org/jira/browse/IGNITE-6486
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.2
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The
> following code causes an exception on {{GetOrCreateCache}}:
> {code}
> var cfg = new IgniteConfiguration
> {
> PersistentStoreConfiguration = new PersistentStoreConfiguration(),
> IsActiveOnStart = true
> };
> using (var ignite = Ignition.Start(cfg))
> {
> var cache = ignite.GetOrCreateCache("foo");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6486) .NET: ActiveOnStart does not work
[
https://issues.apache.org/jira/browse/IGNITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176326#comment-16176326
]
Pavel Tupitsyn commented on IGNITE-6486:
IGNITE-5717 related {{TODO}}s has been removed, tests cleaned up: custom memory
configuration is no longer necessary.
> .NET: ActiveOnStart does not work
> -
>
> Key: IGNITE-6486
> URL: https://issues.apache.org/jira/browse/IGNITE-6486
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.2
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The
> following code causes an exception on {{GetOrCreateCache}}:
> {code}
> var cfg = new IgniteConfiguration
> {
> PersistentStoreConfiguration = new PersistentStoreConfiguration(),
> IsActiveOnStart = true
> };
> using (var ignite = Ignition.Start(cfg))
> {
> var cache = ignite.GetOrCreateCache("foo");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6486) .NET: ActiveOnStart does not work
[
https://issues.apache.org/jira/browse/IGNITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176326#comment-16176326
]
Pavel Tupitsyn edited comment on IGNITE-6486 at 9/22/17 12:11 PM:
--
IGNITE-5717 related {{TODO}} s has been removed, tests cleaned up: custom
memory configuration is no longer necessary.
was (Author: ptupitsyn):
IGNITE-5717 related {{TODO}}s has been removed, tests cleaned up: custom memory
configuration is no longer necessary.
> .NET: ActiveOnStart does not work
> -
>
> Key: IGNITE-6486
> URL: https://issues.apache.org/jira/browse/IGNITE-6486
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.2
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The
> following code causes an exception on {{GetOrCreateCache}}:
> {code}
> var cfg = new IgniteConfiguration
> {
> PersistentStoreConfiguration = new PersistentStoreConfiguration(),
> IsActiveOnStart = true
> };
> using (var ignite = Ignition.Start(cfg))
> {
> var cache = ignite.GetOrCreateCache("foo");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5717) MemoryPolicy configuration and documentation improvements
[
https://issues.apache.org/jira/browse/IGNITE-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176325#comment-16176325
]
Pavel Tupitsyn commented on IGNITE-5717:
{{MaxSize}} changed from 80% to 20% as part of IGNITE-5884.
.NET tests cleaned up as part of IGNITE-6486.
> MemoryPolicy configuration and documentation improvements
> -
>
> Key: IGNITE-5717
> URL: https://issues.apache.org/jira/browse/IGNITE-5717
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Sergey Chugunov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> After introducing MemoryPolicy concept and related settings to Ignite there
> were several cases when users run into problems with default configuration.
> It seems that approach with allocating 80% of available physical memory
> causes confusion among users sitting on 32bit systems including versions of
> JMV (example [1]) and also hurts stability of TeamCity.
> We need to rethink these settings and make them easier to use.
> Also it turned out that memory allocation process differs in cases of PDS on
> and off; it must be properly documented.
> [1]
> http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6486) .NET: ActiveOnStart does not work
[
https://issues.apache.org/jira/browse/IGNITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176322#comment-16176322
]
ASF GitHub Bot commented on IGNITE-6486:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2729
IGNITE-6486 .NET: Update IsActiveOnStart documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-6486
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2729.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 #2729
commit ffd2cbcff6c71010a762f5bc37619103ce445f15
Author: Pavel Tupitsyn
Date: 2017-09-22T11:54:37Z
IGNITE-6486 .NET: ActiveOnStart does not work
> .NET: ActiveOnStart does not work
> -
>
> Key: IGNITE-6486
> URL: https://issues.apache.org/jira/browse/IGNITE-6486
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.2
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The
> following code causes an exception on {{GetOrCreateCache}}:
> {code}
> var cfg = new IgniteConfiguration
> {
> PersistentStoreConfiguration = new PersistentStoreConfiguration(),
> IsActiveOnStart = true
> };
> using (var ignite = Ignition.Start(cfg))
> {
> var cache = ignite.GetOrCreateCache("foo");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6486) .NET: ActiveOnStart does not work
[
https://issues.apache.org/jira/browse/IGNITE-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176321#comment-16176321
]
Pavel Tupitsyn commented on IGNITE-6486:
Turns out this behavior is expected. Javadoc and xmldoc updated.
> .NET: ActiveOnStart does not work
> -
>
> Key: IGNITE-6486
> URL: https://issues.apache.org/jira/browse/IGNITE-6486
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.2
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The
> following code causes an exception on {{GetOrCreateCache}}:
> {code}
> var cfg = new IgniteConfiguration
> {
> PersistentStoreConfiguration = new PersistentStoreConfiguration(),
> IsActiveOnStart = true
> };
> using (var ignite = Ignition.Start(cfg))
> {
> var cache = ignite.GetOrCreateCache("foo");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology
[
https://issues.apache.org/jira/browse/IGNITE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176312#comment-16176312
]
Vladisav Jelisavcic commented on IGNITE-4173:
-
Hi Evgenii, in order for the permits to be recovered after the failure of
acquiring semaphore, there must be at least one (other than the failing)
semaphore alive; If not, there is no one to do the recovery and the permits get
wasted (this is exactly what happens when you initialize second semaphore after
the first one is broken, as in your scenario). This specific test was made to
point out a bug (which was resolved) where semaphore was not able to recover
properly because of lazy initialization.
> IgniteSemaphore with failoverSafe enabled doesn't release permits in case
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6249) .NET: IgniteConfiguration.ConsistentId
[
https://issues.apache.org/jira/browse/IGNITE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176308#comment-16176308
]
Pavel Tupitsyn commented on IGNITE-6249:
Done, waiting for TeamCity.
> .NET: IgniteConfiguration.ConsistentId
> --
>
> Key: IGNITE-6249
> URL: https://issues.apache.org/jira/browse/IGNITE-6249
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, usability
> Fix For: 2.3
>
>
> Propagate {{IgniteConfiguration.ConsistentId}} to .NET.
> Java side requires {{Serializable}} there, and {{BinaryObject}} is
> {{Serializable}}, so we can provide any user-defined objects there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6249) .NET: IgniteConfiguration.ConsistentId
[
https://issues.apache.org/jira/browse/IGNITE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176307#comment-16176307
]
ASF GitHub Bot commented on IGNITE-6249:
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2727
IGNITE-6249 .NET: IgniteConfiguration.ConsistentId
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-6249
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2727.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 #2727
commit d091c5d147e471b892990e44cd82d2a90be4d9bc
Author: Pavel Tupitsyn
Date: 2017-09-22T10:09:56Z
IGNITE-6249 .NET: IgniteConfiguration.ConsistentId
commit 26f916faf0b503cb1794062b6f1a1202caba9e52
Author: Pavel Tupitsyn
Date: 2017-09-22T10:18:24Z
wip tests
commit 58e5bcf981ab78f289169a08abb2021c1ed5d8f2
Author: Pavel Tupitsyn
Date: 2017-09-22T10:22:56Z
Fix indexed properties handling
commit feb1cfbfb246335a2957d31f0cfe0346f55b0882
Author: Pavel Tupitsyn
Date: 2017-09-22T10:27:18Z
Schema done
commit fcd6cad958f0f3c8a40d452156db017971b84222
Author: Pavel Tupitsyn
Date: 2017-09-22T11:01:25Z
wip
commit 236506209a8548566829ecdd365d59f00fdf8e97
Author: Pavel Tupitsyn
Date: 2017-09-22T11:03:36Z
wip
commit 51331f40ca00bff966efd04dd265e01cbcefd04d
Author: Pavel Tupitsyn
Date: 2017-09-22T11:07:29Z
Merge remote-tracking branch 'upstream/master' into ignite-6249
commit 8ed47f1ea052756b86038d23d1d370a106d5233b
Author: Pavel Tupitsyn
Date: 2017-09-22T11:17:19Z
fix null consistentId
commit 389b30c5ed27f5f5e35b3afe385285f915d6fa23
Author: Pavel Tupitsyn
Date: 2017-09-22T11:42:40Z
wip tests
commit 241c11dab51b3116655627be1391fa9d88340773
Author: Pavel Tupitsyn
Date: 2017-09-22T11:46:17Z
Add ConsistentId test
> .NET: IgniteConfiguration.ConsistentId
> --
>
> Key: IGNITE-6249
> URL: https://issues.apache.org/jira/browse/IGNITE-6249
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET, usability
> Fix For: 2.3
>
>
> Propagate {{IgniteConfiguration.ConsistentId}} to .NET.
> Java side requires {{Serializable}} there, and {{BinaryObject}} is
> {{Serializable}}, so we can provide any user-defined objects there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6486) .NET: ActiveOnStart does not work
Pavel Tupitsyn created IGNITE-6486:
--
Summary: .NET: ActiveOnStart does not work
Key: IGNITE-6486
URL: https://issues.apache.org/jira/browse/IGNITE-6486
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.2
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.3
{{IgniteConfiguration.IsActiveOnStart}} seems to have no effect. The following
code causes an exception on {{GetOrCreateCache}}:
{code}
var cfg = new IgniteConfiguration
{
PersistentStoreConfiguration = new PersistentStoreConfiguration(),
IsActiveOnStart = true
};
using (var ignite = Ignition.Start(cfg))
{
var cache = ignite.GetOrCreateCache("foo");
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3939) Compact NULL values binary representation
[ https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3939: Summary: Compact NULL values binary representation (was: Compact long zero values binary representation) > Compact NULL values binary representation > - > > Key: IGNITE-3939 > URL: https://issues.apache.org/jira/browse/IGNITE-3939 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 1.7 >Reporter: Andrew Mashenkov >Assignee: Taras Ledkov > Labels: iep-2, performance > Fix For: 2.3 > > > We can use separate type for Long zero values and exclude 8-byte value from > binary representation. This will reduce memory footprint and network load. > Compatibility with previous versions MUST be preserved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()
[
https://issues.apache.org/jira/browse/IGNITE-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-6485:
Priority: Critical (was: Major)
> Binary marshaller fails on deserialization of object with writeReplace()
>
>
> Key: IGNITE-6485
> URL: https://issues.apache.org/jira/browse/IGNITE-6485
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Priority: Critical
> Fix For: 2.3
>
>
> The problem found during testing vertx-ignite project with new version of
> Vert.x framework.
> Binary marshaller fails on deserialization of object with writeReplace()
> because deserialized object can't be assigned to field due to a type
> incompatibility.
> During setting field value the following checking will be failed in
> {{UnsafeObjectFieldAccessorImpl.set(Object var1, Object var2)}} method (see
> comment):
> {code:java}
> public void set(Object var1, Object var2) throws
> IllegalArgumentException, IllegalAccessException {
> this.ensureObj(var1);
> if (this.isFinal) {
> this.throwFinalFieldIllegalAccessException(var2);
> }
> // HERE: Field type isn't assignable from object type.
> if (var2 != null &&
> !this.field.getType().isAssignableFrom(var2.getClass())) {
> this.throwSetIllegalArgumentException(var2);
> }
> unsafe.putObject(var1, this.fieldOffset, var2);
> }
> {code}
> The following error will be logged:
> {noformat}
> class org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
> object
> [typeName=org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject]
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
> at
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserialize(BinaryObjectImpl.java:639)
> at
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest.testUnmarshal(BinaryMarshallerReplaceObjectTest.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
> read field [name=val]
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:168)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
> ... 14 more
> Caused by: java.lang.IllegalArgumentException: Can not set
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Intf
> field
> org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject.val
> to org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Cls
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
> at
> sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
> at java.lang.reflect.Field.set(Field.java:741)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:683)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
> ... 15 more
> {noformat}
> Minimal reproducer:
> {code:java}
> package org.apache.ignite.internal.binary;
> import java.io.Serializable;
> import java.util.Arrays;
> import java.util.Collection;
> import org.apache.ignite.IgniteCheckedException;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.binary.BinaryIdMapper;
> import org.apache.ignite.binary.BinaryNameMapper;
> import org.apache.ignite
[jira] [Updated] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()
[
https://issues.apache.org/jira/browse/IGNITE-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-6485:
Description:
The problem found during testing vertx-ignite project with new version of
Vert.x framework.
Binary marshaller fails on deserialization of object with writeReplace()
because deserialized object can't be assigned to field due to a type
incompatibility.
During setting field value the following checking will be failed in
{{UnsafeObjectFieldAccessorImpl.set(Object var1, Object var2)}} method (see
comment):
{code:java}
public void set(Object var1, Object var2) throws IllegalArgumentException,
IllegalAccessException {
this.ensureObj(var1);
if (this.isFinal) {
this.throwFinalFieldIllegalAccessException(var2);
}
// HERE: Field type isn't assignable from object type.
if (var2 != null &&
!this.field.getType().isAssignableFrom(var2.getClass())) {
this.throwSetIllegalArgumentException(var2);
}
unsafe.putObject(var1, this.fieldOffset, var2);
}
{code}
The following error will be logged:
{noformat}
class org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
object
[typeName=org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject]
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserialize(BinaryObjectImpl.java:639)
at
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest.testUnmarshal(BinaryMarshallerReplaceObjectTest.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to read
field [name=val]
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:168)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
... 14 more
Caused by: java.lang.IllegalArgumentException: Can not set
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Intf field
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject.val
to org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Cls
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
at
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:741)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:683)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
... 15 more
{noformat}
Minimal reproducer:
{code:java}
package org.apache.ignite.internal.binary;
import java.io.Serializable;
import java.util.Arrays;
import java.util.Collection;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.IgniteException;
import org.apache.ignite.binary.BinaryIdMapper;
import org.apache.ignite.binary.BinaryNameMapper;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.binary.BinarySerializer;
import org.apache.ignite.binary.BinaryTypeConfiguration;
import org.apache.ignite.configuration.BinaryConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.managers.discovery.GridDiscoveryManager;
import org.apache.ignite.internal.util.IgniteUtils;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.logger.NullLogger;
import org.apache.ignite.marshaller.MarshallerContextTestImpl;
import org.ap
[jira] [Created] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()
Andrey Gura created IGNITE-6485:
---
Summary: Binary marshaller fails on deserialization of object with
writeReplace()
Key: IGNITE-6485
URL: https://issues.apache.org/jira/browse/IGNITE-6485
Project: Ignite
Issue Type: Bug
Reporter: Andrey Gura
Fix For: 2.3
Binary marshaller fails on deserialization of object with writeReplace()
because deserialized object can't be assigned to field due to a type
incompatibility.
During setting field value the following checking will be failed in
{{UnsafeObjectFieldAccessorImpl.set(Object var1, Object var2)}} method (see
comment):
{code:java}
public void set(Object var1, Object var2) throws IllegalArgumentException,
IllegalAccessException {
this.ensureObj(var1);
if (this.isFinal) {
this.throwFinalFieldIllegalAccessException(var2);
}
// HERE: Field type isn't assignable from object type.
if (var2 != null &&
!this.field.getType().isAssignableFrom(var2.getClass())) {
this.throwSetIllegalArgumentException(var2);
}
unsafe.putObject(var1, this.fieldOffset, var2);
}
{code}
The following error will be logged:
{noformat}
class org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
object
[typeName=org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject]
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserialize(BinaryObjectImpl.java:639)
at
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest.testUnmarshal(BinaryMarshallerReplaceObjectTest.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to read
field [name=val]
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:168)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
... 14 more
Caused by: java.lang.IllegalArgumentException: Can not set
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Intf field
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject.val
to org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Cls
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
at
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:741)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:683)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
... 15 more
{noformar}
Minimal reproducer:
{code:java}
package org.apache.ignite.internal.binary;
import java.io.Serializable;
import java.util.Arrays;
import java.util.Collection;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.IgniteException;
import org.apache.ignite.binary.BinaryIdMapper;
import org.apache.ignite.binary.BinaryNameMapper;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.binary.BinarySerializer;
import org.apache.ignite.binary.BinaryTypeConfiguration;
import org.apache.ignite.configuration.BinaryConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.managers.discovery.GridDiscoveryManager;
import org.apache.ignite.internal.util.IgniteUtils;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.logger.NullLo
[jira] [Updated] (IGNITE-6485) Binary marshaller fails on deserialization of object with writeReplace()
[
https://issues.apache.org/jira/browse/IGNITE-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-6485:
Description:
Binary marshaller fails on deserialization of object with writeReplace()
because deserialized object can't be assigned to field due to a type
incompatibility.
During setting field value the following checking will be failed in
{{UnsafeObjectFieldAccessorImpl.set(Object var1, Object var2)}} method (see
comment):
{code:java}
public void set(Object var1, Object var2) throws IllegalArgumentException,
IllegalAccessException {
this.ensureObj(var1);
if (this.isFinal) {
this.throwFinalFieldIllegalAccessException(var2);
}
// HERE: Field type isn't assignable from object type.
if (var2 != null &&
!this.field.getType().isAssignableFrom(var2.getClass())) {
this.throwSetIllegalArgumentException(var2);
}
unsafe.putObject(var1, this.fieldOffset, var2);
}
{code}
The following error will be logged:
{noformat}
class org.apache.ignite.binary.BinaryObjectException: Failed to deserialize
object
[typeName=org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject]
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:797)
at
org.apache.ignite.internal.binary.BinaryObjectImpl.deserialize(BinaryObjectImpl.java:639)
at
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest.testUnmarshal(BinaryMarshallerReplaceObjectTest.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to read
field [name=val]
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:168)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:843)
... 14 more
Caused by: java.lang.IllegalArgumentException: Can not set
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Intf field
org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$TestObject.val
to org.apache.ignite.internal.binary.BinaryMarshallerReplaceObjectTest$Cls
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164)
at
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168)
at
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
at java.lang.reflect.Field.set(Field.java:741)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:683)
at
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:164)
... 15 more
{noformat}
Minimal reproducer:
{code:java}
package org.apache.ignite.internal.binary;
import java.io.Serializable;
import java.util.Arrays;
import java.util.Collection;
import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.IgniteException;
import org.apache.ignite.binary.BinaryIdMapper;
import org.apache.ignite.binary.BinaryNameMapper;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.binary.BinarySerializer;
import org.apache.ignite.binary.BinaryTypeConfiguration;
import org.apache.ignite.configuration.BinaryConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.managers.discovery.GridDiscoveryManager;
import org.apache.ignite.internal.util.IgniteUtils;
import org.apache.ignite.internal.util.typedef.internal.U;
import org.apache.ignite.logger.NullLogger;
import org.apache.ignite.marshaller.MarshallerContextTestImpl;
import org.apache.ignite.spi.discovery.DiscoverySpiCustomMessage;
import org.apache.ignite.spi.discovery.tc
[jira] [Updated] (IGNITE-6484) Fix IgnitePdsThreadInterruptionTest failure with larger number of threads.
[ https://issues.apache.org/jira/browse/IGNITE-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-6484: -- Description: Test fails on interruptions of conditional wait. Related ticket IGNITE-6228 was:Test fails on interruptions of conditional wait. > Fix IgnitePdsThreadInterruptionTest failure with larger number of threads. > -- > > Key: IGNITE-6484 > URL: https://issues.apache.org/jira/browse/IGNITE-6484 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov > Fix For: 2.3 > > > Test fails on interruptions of conditional wait. > Related ticket IGNITE-6228 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6484) Fix IgnitePdsThreadInterruptionTest failure with larger number of threads.
Alexei Scherbakov created IGNITE-6484: - Summary: Fix IgnitePdsThreadInterruptionTest failure with larger number of threads. Key: IGNITE-6484 URL: https://issues.apache.org/jira/browse/IGNITE-6484 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Alexei Scherbakov Assignee: Alexei Scherbakov Fix For: 2.3 Test fails on interruptions of conditional wait. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6480) Incorrect server node filter in GridDiscoveryManager
[ https://issues.apache.org/jira/browse/IGNITE-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176238#comment-16176238 ] ASF GitHub Bot commented on IGNITE-6480: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2726 > Incorrect server node filter in GridDiscoveryManager > > > Key: IGNITE-6480 > URL: https://issues.apache.org/jira/browse/IGNITE-6480 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin > Fix For: 2.3 > > > GridDiscoveryManager.serverTopologyNodes return collection nodes with daemon > node inside. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6397) .NET: Thin client: basic cache operations
[ https://issues.apache.org/jira/browse/IGNITE-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176234#comment-16176234 ] Pavel Tupitsyn commented on IGNITE-6397: All done, [~vozerov] please have a look. > .NET: Thin client: basic cache operations > - > > Key: IGNITE-6397 > URL: https://issues.apache.org/jira/browse/IGNITE-6397 > Project: Ignite > Issue Type: Bug > Components: clients, platforms >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.3 > > > We need to implement base cache operations, such as "remove", "replace", > "putIfAbsent". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6483) Entries count in caches' MX Beans not immediately available
[
https://issues.apache.org/jira/browse/IGNITE-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-6483:
Attachment: IgniteCacheMxBeansTest.java
Reproducer test
> Entries count in caches' MX Beans not immediately available
> ---
>
> Key: IGNITE-6483
> URL: https://issues.apache.org/jira/browse/IGNITE-6483
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Kasnacheev
> Attachments: IgniteCacheMxBeansTest.java
>
>
> When querying properties like
> {code}
> cache.mxBean().getOffHeapPrimaryEntriesCount()
> {code}
> The value is often 0 (zero) initially, even if cache is not empty and located
> in offheap.
> Local MX Bean returns correct value.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6483) Entries count in caches' MX Beans not immediately available
Ilya Kasnacheev created IGNITE-6483:
---
Summary: Entries count in caches' MX Beans not immediately
available
Key: IGNITE-6483
URL: https://issues.apache.org/jira/browse/IGNITE-6483
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Ilya Kasnacheev
When querying properties like
{code}
cache.mxBean().getOffHeapPrimaryEntriesCount()
{code}
The value is often 0 (zero) initially, even if cache is not empty and located
in offheap.
Local MX Bean returns correct value.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution
[
https://issues.apache.org/jira/browse/IGNITE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-5919.
Resolution: Fixed
> .NET: EntryProcessorExample closes immediately after execution
> --
>
> Key: IGNITE-5919
> URL: https://issues.apache.org/jira/browse/IGNITE-5919
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
>
> EntryProcessorExample closes immediately after execution. Please, add:
> {code}
> Console.WriteLine();
> Console.WriteLine(">>> Example finished, press any key to exit ...");
> Console.ReadKey();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution
[
https://issues.apache.org/jira/browse/IGNITE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176217#comment-16176217
]
Pavel Tupitsyn commented on IGNITE-5919:
Fixed in master: {{9f662cc4b524305af3126af49ccace7dab40216e}}.
Examples test updated to catch these.
> .NET: EntryProcessorExample closes immediately after execution
> --
>
> Key: IGNITE-5919
> URL: https://issues.apache.org/jira/browse/IGNITE-5919
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
>
> EntryProcessorExample closes immediately after execution. Please, add:
> {code}
> Console.WriteLine();
> Console.WriteLine(">>> Example finished, press any key to exit ...");
> Console.ReadKey();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution
[
https://issues.apache.org/jira/browse/IGNITE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-5919:
---
Description:
EntryProcessorExample closes immediately after execution. Please, add:
{code}
Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit ...");
Console.ReadKey();
{code}
was:
EntryProcessorExample closes immediately after execution. Please, add:
Console.WriteLine();
Console.WriteLine(">>> Example finished, press any key to exit ...");
Console.ReadKey();
> .NET: EntryProcessorExample closes immediately after execution
> --
>
> Key: IGNITE-5919
> URL: https://issues.apache.org/jira/browse/IGNITE-5919
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
>
> EntryProcessorExample closes immediately after execution. Please, add:
> {code}
> Console.WriteLine();
> Console.WriteLine(">>> Example finished, press any key to exit ...");
> Console.ReadKey();
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6482) Add support for groups count
Pavel Konstantinov created IGNITE-6482: -- Summary: Add support for groups count Key: IGNITE-6482 URL: https://issues.apache.org/jira/browse/IGNITE-6482 Project: Ignite Issue Type: Improvement Components: yardstick Reporter: Pavel Konstantinov Assignee: Pavel Konstantinov Priority: Minor Current implementation supports only one group for caches. We need improve it to support more then one group. Each group will have / caches inside. Applicable only if option -cc (caches count) is set. Default groups count = 1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6008) CacheRemoveAllSelfTest.testRemoveAll fails sometimes
[
https://issues.apache.org/jira/browse/IGNITE-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176211#comment-16176211
]
Aleksei Zaitsev commented on IGNITE-6008:
-
Launched four times in version 2.1 - no failures. In other branches test also
"green"
> CacheRemoveAllSelfTest.testRemoveAll fails sometimes
>
>
> Key: IGNITE-6008
> URL: https://issues.apache.org/jira/browse/IGNITE-6008
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Aleksei Zaitsev
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> {noformat}
> [2017-08-09 01:18:15,172][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Local size: 58
> On heap: 58
> Off heap: 58
> Primary: 58
> Backup: 14 expected:<0> but was:<58>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at
> org.apache.ignite.internal.processors.cache.CacheRemoveAllSelfTest.testRemoveAll(CacheRemoveAllSelfTest.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5919) .NET: EntryProcessorExample closes immediately after execution
[
https://issues.apache.org/jira/browse/IGNITE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-5919:
--
Assignee: Pavel Tupitsyn
> .NET: EntryProcessorExample closes immediately after execution
> --
>
> Key: IGNITE-5919
> URL: https://issues.apache.org/jira/browse/IGNITE-5919
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.9
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
>
> EntryProcessorExample closes immediately after execution. Please, add:
> Console.WriteLine();
> Console.WriteLine(">>> Example finished, press any key to exit ...");
> Console.ReadKey();
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6334) Throttle writing threads during ongoing checkpoint with token bucket algorithm
[ https://issues.apache.org/jira/browse/IGNITE-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176192#comment-16176192 ] ASF GitHub Bot commented on IGNITE-6334: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2710 > Throttle writing threads during ongoing checkpoint with token bucket algorithm > -- > > Key: IGNITE-6334 > URL: https://issues.apache.org/jira/browse/IGNITE-6334 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.1 >Reporter: Ivan Rakov >Assignee: Ivan Rakov > Fix For: 2.3 > > Attachments: opsec3.jpg > > > We've received several negative pieces of feedback about LFS performance with > enabled persistence. Ignite node stops responding to user operations under > intensive load. Typical operations/second graph is attached. > Zero dropdowns happen during ongoing checkpoint when checkpoint buffer > (memory segment that accumulates old versions of dirty pages that are not yet > written in current checkpoint) is overflowed. > In general, performance decrease is inevitable - writing in memory is always > faster than writing to disk. Though, we can avoid zero dropdowns if we'll > throttle threads that generate dirty pages. > We can manage amount of throttle time with tocken bucket algorithm: > 1) Before checkpoint start, we calculate ratio K = (number of checkpoint > pages) / (size of checkpoint buffer) and initialize non-negative atomic > marker counter > 2) Every checkpointing thread increments marker counter once per K written > pages > 3) Any thread that makes page dirty should decrement marker counter. Thread > should wait if marker counter is zero. > Such algorithm makes buffer overflow impossible. If activity is intensive and > constant, user threads will write at the speed of the disk. On the other > hand, user threads will write at maximum speed in case of burst activity. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (IGNITE-4730) .NET: Propagate IgniteConfiguration.OdbcConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn closed IGNITE-4730.
--
> .NET: Propagate IgniteConfiguration.OdbcConfiguration
> -
>
> Key: IGNITE-4730
> URL: https://issues.apache.org/jira/browse/IGNITE-4730
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> ODBC can be enabled via {{IgniteConfiguration.odbcConfiguration}} in Java.
> Propagate this property to .NET.
> https://apacheignite.readme.io/docs/odbc-driver
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-4730) .NET: Propagate IgniteConfiguration.OdbcConfiguration
[
https://issues.apache.org/jira/browse/IGNITE-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-4730.
Resolution: Won't Fix
Won't fix. {{OdbcConfiguration}} has been deprecated in favor of
{{ClientConnectorConfiguration}}, which has been propagated as part of
IGNITE-6399.
> .NET: Propagate IgniteConfiguration.OdbcConfiguration
> -
>
> Key: IGNITE-4730
> URL: https://issues.apache.org/jira/browse/IGNITE-4730
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> ODBC can be enabled via {{IgniteConfiguration.odbcConfiguration}} in Java.
> Propagate this property to .NET.
> https://apacheignite.readme.io/docs/odbc-driver
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6481) JDBC v2: must not use a cache to query Ignite
Taras Ledkov created IGNITE-6481:
Summary: JDBC v2: must not use a cache to query Ignite
Key: IGNITE-6481
URL: https://issues.apache.org/jira/browse/IGNITE-6481
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.1
Reporter: Taras Ledkov
Fix For: 2.3
Now the {{cache}} parameter is required for the JDBC v2 driver.
But Ignite internal API allows execute SQL query with nothing cache specified.
{{cache}} parameter must be optional (for compatibility with previous versions)
{{schema}} parameter must be added to allow specify the schema at the
connection string.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6480) Incorrect server node filter in GridDiscoveryManager
[ https://issues.apache.org/jira/browse/IGNITE-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176164#comment-16176164 ] ASF GitHub Bot commented on IGNITE-6480: GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2726 IGNITE-6480 fix serverTopologyNodes method You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6480 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2726.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 #2726 commit 2d77153465b098805954d825610e8afae413511d Author: Dmitriy Govorukhin Date: 2017-09-22T09:28:53Z IGNITE-6480 fix serverTopologyNodes method > Incorrect server node filter in GridDiscoveryManager > > > Key: IGNITE-6480 > URL: https://issues.apache.org/jira/browse/IGNITE-6480 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin > Fix For: 2.3 > > > GridDiscoveryManager.serverTopologyNodes return collection nodes with daemon > node inside. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-6303) .NET: GetAll should close query cursor
[
https://issues.apache.org/jira/browse/IGNITE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-6303.
Resolution: Not A Bug
Actually we don't need to do anything. Java-side cursor is closed, and we link
from .NET to Java via {{PlatformJniTarget}}, which does not need explicit
release.
> .NET: GetAll should close query cursor
> --
>
> Key: IGNITE-6303
> URL: https://issues.apache.org/jira/browse/IGNITE-6303
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> {{QueryCursor}} in Java is closed automatically on {{getAll}} call, we should
> do the same in Ignite.NET.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6213) Unexpected setting local deployment owner anyone node
[
https://issues.apache.org/jira/browse/IGNITE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176148#comment-16176148
]
ASF GitHub Bot commented on IGNITE-6213:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2723
> Unexpected setting local deployment owner anyone node
> -
>
> Key: IGNITE-6213
> URL: https://issues.apache.org/jira/browse/IGNITE-6213
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Dmitriy Govorukhin
> Fix For: 2.3
>
>
> In my test I have seen, when one node tune up {{locDepOwner}} flag suddenly.
> {noformat}
> 16:55:47.868
> [ DEBUG]
> [ o.a.i.i.p.c.GridCacheDeploymentManager]
> [ T:] - Prepared grid cache deployable
> [ dep=GridDeploymentInfoBean
> [ clsLdrId=aefa3c4fd51-12bb727e-4815-4ab2-8f8c-cc6fd52c8553, depMode=SHARED,
> userVer=0, locDepOwner=true, participants=null],
> deployable=GridNearAtomicSingleUpdateRequest
> [ key=UserKeyCacheObjectImpl
> [ part=111, val=4翿翿, hasValBytes=true],
> super=GridNearAtomicSingleUpdateRequest
> [ key=UserKeyCacheObjectImpl
> [ part=111, val=4翿翿, hasValBytes=true],
> parent=GridNearAtomicAbstractSingleUpdateRequest
> [ nodeId=45acc827-8a2d-47d3-aa04-94936ad25ac2, futId=81921,
> topVer=AffinityTopologyVersion
> [ topVer=4, minorTopVer=0], parent=GridNearAtomicAbstractUpdateRequest
> [ res=null, flags=]
> {noformat}
> By the reason global participant was been registered:
> {noformat}
> 16:55:47.871
> [ DEBUG]
> [ o.a.i.i.m.d.GridDeploymentPerVersionStore]
> [ T:] - Explicitly added participant
> [ dep=SharedDeployment
> [ rmv=false, super=GridDeployment
> [ ts=1503050146264, depMode=SHARED, clsLdr=GridDeploymentClassLoader
> [ id=acaa3c4fd51-45acc827-8a2d-47d3-aa04-94936ad25ac2, singleNode=false,
> nodeLdrMap={12bb727e-4815-4ab2-8f8c-cc6fd52c8553=aefa3c4fd51-12bb727e-4815-4ab2-8f8c-cc6fd52c8553,
>
> 101abc71-83b4-4a87-bb07-14e4cbc7226e=2c044c4fd51-101abc71-83b4-4a87-bb07-14e4cbc7226e,
>
> 9d30737f-44d2-4414-b84d-25f032484290=e70b3c4fd51-9d30737f-44d2-4414-b84d-25f032484290},
> p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false],
> clsLdrId=acaa3c4fd51-45acc827-8a2d-47d3-aa04-94936ad25ac2, userVer=0,
> loc=false, sampleClsName=com.sbt.dpl.gridgain.index.InvokeIndexAdder,
> pendingUndeploy=false, undeployed=false, usage=0]],
> nodeId=12bb727e-4815-4ab2-8f8c-cc6fd52c8553,
> ldrId=aefa3c4fd51-12bb727e-4815-4ab2-8f8c-cc6fd52c8553]
> {noformat}
> And after that I am geting the Exception when try to get class from node
> where the class was not located:
> {noformat}
> 16:55:50.684 [ERROR] [o.a.i.i.p.job.GridJobProcessor] [T:] - Task was not
> deployed or was redeployed since task execution
> [taskName=com.sbt.azimuth_psi.publisher.forms.computing.parallelBatchCollectForm$TestMapFunction,
>
> taskClsName=com.sbt.azimuth_psi.publisher.forms.computing.parallelBatchCollectForm$TestMapFunction,
> codeVer=0, clsLdrId=2c044c4fd51-101abc71-83b4-4a87-bb07-14e4cbc7226e,
> seqNum=1503050088642, depMode=SHARED, dep=null]
> org.apache.ignite.IgniteDeploymentException: Task was not deployed or was
> redeployed since task execution
> [taskName=com.sbt.azimuth_psi.publisher.forms.computing.parallelBatchCollectForm$TestMapFunction,
>
> taskClsName=com.sbt.azimuth_psi.publisher.forms.computing.parallelBatchCollectForm$TestMapFunction,
> codeVer=0, clsLdrId=2c044c4fd51-101abc71-83b4-4a87-bb07-14e4cbc7226e,
> seqNum=1503050088642, depMode=SHARED, dep=null]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1160)
> ~[ignite-core-2.1.3.jar:2.1.3]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908)
> [ignite-core-2.1.3.jar:2.1.3]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> [ignite-core-2.1.3.jar:2.1.3]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> [ignite-core-2.1.3.jar:2.1.3]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> [ignite-core-2.1.3.jar:2.1.3]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
> [ignite-core-2.1.3.jar:2.1.3]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_80]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_80]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#6
[jira] [Created] (IGNITE-6480) Incorrect server node filter in GridDiscoveryManager
Dmitriy Govorukhin created IGNITE-6480: -- Summary: Incorrect server node filter in GridDiscoveryManager Key: IGNITE-6480 URL: https://issues.apache.org/jira/browse/IGNITE-6480 Project: Ignite Issue Type: Bug Reporter: Dmitriy Govorukhin Assignee: Dmitriy Govorukhin Fix For: 2.3 GridDiscoveryManager.serverTopologyNodes return collection nodes with daemon node inside. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6478) IndexOutOfBoundsException jdbc2
[
https://issues.apache.org/jira/browse/IGNITE-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-6478:
---
Assignee: Taras Ledkov
> IndexOutOfBoundsException jdbc2
> ---
>
> Key: IGNITE-6478
> URL: https://issues.apache.org/jira/browse/IGNITE-6478
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Assignee: Taras Ledkov
> Fix For: 2.3
>
>
> I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
> {noformat}
> when I tried to get list of tables I got exception:
> {noformat}
> 0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
> java.lang.IndexOutOfBoundsException: Index: 0
> at java.util.Collections$EmptyList.get(Collections.java:4454)
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
> at sqlline.Rows.isPrimaryKey(Rows.java:68)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
> at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
> at sqlline.SqlLine.print(SqlLine.java:1648)
> at sqlline.Commands.metadata(Commands.java:199)
> at sqlline.Commands.tables(Commands.java:332)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6181) Tx is not rolled back on timeout leading to potential whole grid hang
[
https://issues.apache.org/jira/browse/IGNITE-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-6181:
Assignee: Semen Boikov (was: Alexei Scherbakov)
> Tx is not rolled back on timeout leading to potential whole grid hang
> -
>
> Key: IGNITE-6181
> URL: https://issues.apache.org/jira/browse/IGNITE-6181
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Alexei Scherbakov
>Assignee: Semen Boikov
> Fix For: 2.3
>
>
> Incorrectly handled transactions (not calling commit, rollback or close) are
> staying in grid forever, potentially holding locks and preventing exchange
> start.
> Unit test reproducer:
> {noformat}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one or more
> * contributor license agreements. See the NOTICE file distributed with
> * this work for additional information regarding copyright ownership.
> * The ASF licenses this file to You under the Apache License, Version 2.0
> * (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.ignite.cache;
> import java.util.concurrent.CountDownLatch;
> import java.util.concurrent.TimeUnit;
> import java.util.concurrent.atomic.AtomicBoolean;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.TransactionConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> /**
> * Tests ability to rollback not properly closed transaction.
> */
> public class IgniteTxTimeoutTest extends GridCommonAbstractTest {
> /** */
> private static final long TX_TIMEOUT = 3_000L;
> /** */
> private static final String CACHE_NAME = "test";
> /** IP finder. */
> private static final TcpDiscoveryVmIpFinder IP_FINDER = new
> TcpDiscoveryVmIpFinder(true);
> /** */
> private final CountDownLatch l = new CountDownLatch(1);
> /** */
> private final Object mux = new Object();
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setDiscoverySpi(new TcpDiscoverySpi().setIpFinder(IP_FINDER));
> TransactionConfiguration txCfg = new TransactionConfiguration();
> txCfg.setDefaultTxTimeout(TX_TIMEOUT);
> cfg.setTransactionConfiguration(txCfg);
> CacheConfiguration ccfg = new CacheConfiguration(CACHE_NAME);
> ccfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** */
> public void testTxTimeoutHandling() throws Exception {
> try {
> final Ignite ignite = startGrid(0);
> final AtomicBoolean released = new AtomicBoolean();
> multithreadedAsync(new Runnable() {
> @Override public void run() {
> // Start tx with default settings.
> try (Transaction tx = ignite.transactions().txStart()) {
> ignite.cache(CACHE_NAME).put(1, 1);
> l.countDown();
> // Wait longer than default timeout.
> synchronized (mux) {
> while (!released.get()) {
> try {
> mux.wait();
> }
> catch (InterruptedException e) {
> throw new IgniteException(e);
> }
> }
> }
>
[jira] [Commented] (IGNITE-6397) .NET: Thin client: basic cache operations
[ https://issues.apache.org/jira/browse/IGNITE-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176132#comment-16176132 ] ASF GitHub Bot commented on IGNITE-6397: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2725 IGNITE-6397 .NET: Thin client: basic cache operations You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6397 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2725.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 #2725 commit 198f844473b6a54927b8aacaefe3181e8059e0bf Author: Pavel Tupitsyn Date: 2017-09-22T08:50:54Z IGNITE-6397 .NET: Thin client: basic cache operations > .NET: Thin client: basic cache operations > - > > Key: IGNITE-6397 > URL: https://issues.apache.org/jira/browse/IGNITE-6397 > Project: Ignite > Issue Type: Bug > Components: clients, platforms >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.3 > > > We need to implement base cache operations, such as "remove", "replace", > "putIfAbsent". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Deleted] (IGNITE-6479) IndexOutOfBoundsException jdbc2
[
https://issues.apache.org/jira/browse/IGNITE-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn deleted IGNITE-6479:
---
> IndexOutOfBoundsException jdbc2
> ---
>
> Key: IGNITE-6479
> URL: https://issues.apache.org/jira/browse/IGNITE-6479
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Suntsov
>
> I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
> {noformat}
> when I tried to get list of tables I got exception:
> {noformat}
> 0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
> java.lang.IndexOutOfBoundsException: Index: 0
> at java.util.Collections$EmptyList.get(Collections.java:4454)
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
> at sqlline.Rows.isPrimaryKey(Rows.java:68)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
> at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
> at sqlline.SqlLine.print(SqlLine.java:1648)
> at sqlline.Commands.metadata(Commands.java:199)
> at sqlline.Commands.tables(Commands.java:332)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6479) IndexOutOfBoundsException jdbc2
[
https://issues.apache.org/jira/browse/IGNITE-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Chetaev updated IGNITE-6479:
Description:
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
was:
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
> IndexOutOfBoundsException jdbc2
> ---
>
> Key: IGNITE-6479
> URL: https://issues.apache.org/jira/browse/IGNITE-6479
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
> Fix For: 2.3
>
>
> I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
> {noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
> --verbose=true --showWarnings=true --showNestedErrs=true -u
> jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
> {noformat}
> when I tried to get list of tables I got exception:
> {noformat}
> 0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
> java.lang.IndexOutOfBoundsException: Index: 0
> at java.util.Collections$EmptyList.get(Collections.java:4454)
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
> at sqlline.Rows.isPrimaryKey(Rows.java:68)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
> at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
> at sqlline.TableOutputFormat.print(TableOutpu
[jira] [Created] (IGNITE-6479) IndexOutOfBoundsException jdbc2
Ilya Suntsov created IGNITE-6479:
Summary: IndexOutOfBoundsException jdbc2
Key: IGNITE-6479
URL: https://issues.apache.org/jira/browse/IGNITE-6479
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.1
Reporter: Ilya Suntsov
Fix For: 2.3
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6478) IndexOutOfBoundsException jdbc2
Ilya Suntsov created IGNITE-6478:
Summary: IndexOutOfBoundsException jdbc2
Key: IGNITE-6478
URL: https://issues.apache.org/jira/browse/IGNITE-6478
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.1
Reporter: Ilya Suntsov
Fix For: 2.3
I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true
--verbose=true --showWarnings=true --showNestedErrs=true -u
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6444) Validate that copyOnRead flag is configured with on-heap cache enabled
[ https://issues.apache.org/jira/browse/IGNITE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh reassigned IGNITE-6444: Assignee: Roman Shtykh > Validate that copyOnRead flag is configured with on-heap cache enabled > -- > > Key: IGNITE-6444 > URL: https://issues.apache.org/jira/browse/IGNITE-6444 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Roman Shtykh > Labels: usability > Fix For: 2.3 > > > Link to the user-list discussion: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-1-0-CopyOnRead-Problem-td17009.html > It makes sense to validate the flag and print out a warning if on-heap cache > is disabled. I do not think that we should prevent node from startup because > this may break existing deployments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6477) Add cache index metric to represent index size
Alexander Belyak created IGNITE-6477: Summary: Add cache index metric to represent index size Key: IGNITE-6477 URL: https://issues.apache.org/jira/browse/IGNITE-6477 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.1, 2.0, 1.9, 1.8 Reporter: Alexander Belyak Priority: Minor Fix For: 2.2 Now we can't estimate space used by particular cache index. Let's add it! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
