[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[
https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997980#comment-16997980
]
Ignite TC Bot commented on IGNITE-12424:
{panel:title=Branch: [pull/7122/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4840568]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4835464&buildTypeId=IgniteTests24Java8_RunAll]
> Fix default query timeout behavior for thin JDBC
>
>
> Key: IGNITE-12424
> URL: https://issues.apache.org/jira/browse/IGNITE-12424
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Blocker
> Fix For: 2.8
>
>
> After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver.
> Thin JDBC handles explicit query timeout on a client side. Default query
> timeout is tracked on a server side. As a server is not aware of explicit
> client timeout it is not possible to override a default timeout with longer
> explicit timeout (effectively a query will be cancelled after a default
> timeout expiration).
> The expected behavior is that an explicit query timeout always overrides a
> default one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997982#comment-16997982 ] Ivan Pavlukhin commented on IGNITE-12424: - There are same problems for Cache 6 suite in master as well (https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E&buildTypeTab=overview). Should be addressed separately. > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin resolved IGNITE-12424. - Resolution: Fixed Merged to master. > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12458) Rename Affinity Awareness to Partition Awareness
Pavel Tupitsyn created IGNITE-12458: --- Summary: Rename Affinity Awareness to Partition Awareness Key: IGNITE-12458 URL: https://issues.apache.org/jira/browse/IGNITE-12458 Project: Ignite Issue Type: Task Components: platforms Affects Versions: 2.8 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.8 Rename Affinity Awareness to Partition Awareness in all product components -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12458) Rename Affinity Awareness to Partition Awareness
[ https://issues.apache.org/jira/browse/IGNITE-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12458: Description: Rename Affinity Awareness to Partition Awareness in all product components. Affinity Awareness was not released yet, so there are no breaking changes. was:Rename Affinity Awareness to Partition Awareness in all product components > Rename Affinity Awareness to Partition Awareness > > > Key: IGNITE-12458 > URL: https://issues.apache.org/jira/browse/IGNITE-12458 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 2.8 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Blocker > Fix For: 2.8 > > > Rename Affinity Awareness to Partition Awareness in all product components. > Affinity Awareness was not released yet, so there are no breaking changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-8552: --- Fix Version/s: (was: 2.8) 2.9 Priority: Major (was: Blocker) > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Priority: Major > Fix For: 2.9 > > Attachments: IGNITE-8552_implemented.patch > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998114#comment-16998114 ] Ivan Pavlukhin edited comment on IGNITE-8552 at 12/17/19 11:41 AM: --- Moved fix to next versions. was (Author: pavlukhin): Move fix to next versions. > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Priority: Major > Fix For: 2.9 > > Attachments: IGNITE-8552_implemented.patch > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-8552) Unable to use date as primary key
[ https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998114#comment-16998114 ] Ivan Pavlukhin commented on IGNITE-8552: Move fix to next versions. > Unable to use date as primary key > - > > Key: IGNITE-8552 > URL: https://issues.apache.org/jira/browse/IGNITE-8552 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Pavel Vinokurov >Priority: Major > Fix For: 2.9 > > Attachments: IGNITE-8552_implemented.patch > > > It' is unable to create cache via ddl: > create table tab(id date primary key, date_field date); > Result: > ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to > rollback cache start routine. [cacheName=SQL_PUBLIC_T3] > class org.apache.ignite.IgniteCheckedException: Failed to find value class in > the node classpath (use default marshaller to enable binary objects) : > SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409 > at > org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-2176:
---
Fix Version/s: (was: 2.8)
2.9
Priority: Major (was: Blocker)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUt
[jira] [Created] (IGNITE-12459) Searching checkpoint record in WAL doesn't work with segment compaction
Anton Kalashnikov created IGNITE-12459: -- Summary: Searching checkpoint record in WAL doesn't work with segment compaction Key: IGNITE-12459 URL: https://issues.apache.org/jira/browse/IGNITE-12459 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov During iteration over WAL we have two invariants about result(Tuple): * WALPointer equal to WALRecord.position() when segment is uncompacted * WALPointer not equal to WALRecord.position() when the segment is compacted Unfortunately, the second variant is broken in FileWriteAheadLogManager#read(WALPointer ptr) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12459) Searching checkpoint record in WAL doesn't work with segment compaction
[ https://issues.apache.org/jira/browse/IGNITE-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov updated IGNITE-12459: --- Description: During iteration over WAL we have two invariants about result(Tuple): * WALPointer equal to WALRecord.position() when segment is uncompacted * WALPointer not equal to WALRecord.position() when the segment is compacted Unfortunately, the second variant is broken in FileWriteAheadLogManager#read(WALPointer ptr) was: During iteration over WAL we have two invariants about result(Tuple): * WALPointer equal to WALRecord.position() when segment is uncompacted * WALPointer not equal to WALRecord.position() when the segment is compacted Unfortunately, the second variant is broken in FileWriteAheadLogManager#read(WALPointer ptr) > Searching checkpoint record in WAL doesn't work with segment compaction > --- > > Key: IGNITE-12459 > URL: https://issues.apache.org/jira/browse/IGNITE-12459 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > > During iteration over WAL we have two invariants about > result(Tuple): > * WALPointer equal to WALRecord.position() when segment is uncompacted > * WALPointer not equal to WALRecord.position() when the segment is compacted > Unfortunately, the second variant is broken in > FileWriteAheadLogManager#read(WALPointer ptr) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-2176.
Resolution: Fixed
I confirm that the issue was fixed in scope of IGNITE-12061
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330
[jira] [Issue Comment Deleted] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-2176:
---
Comment: was deleted
(was: I confirm that the issue was fixed in scope of IGNITE-12061)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.jav
[jira] [Resolved] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-2176.
Resolution: Duplicate
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUti
[jira] [Assigned] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-2176:
--
Assignee: Ivan Pavlukhin
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.B
[jira] [Reopened] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reopened IGNITE-2176:
Assignee: (was: Alexey Goncharuk)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(Binar
[jira] [Reopened] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reopened IGNITE-2176:
Assignee: Alexey Goncharuk (was: Ivan Pavlukhin)
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.
[jira] [Resolved] (IGNITE-9489) CorruptedTreeException on index create.
[
https://issues.apache.org/jira/browse/IGNITE-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin resolved IGNITE-9489.
Assignee: Ivan Pavlukhin
Resolution: Duplicate
I confirm that the issue was fixed in scope of IGNITE-12061
> CorruptedTreeException on index create.
> ---
>
> Key: IGNITE-9489
> URL: https://issues.apache.org/jira/browse/IGNITE-9489
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.4, 2.5, 2.6
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: Test.java
>
>
> Currently on dynamic index drop with enabled persistence H2TreeIndex
> instances aren't destroyed. That means that their root pages aren't removed
> from meta tree (see
> {{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
> and reused on subsequent dynamic index create that leads
> CorruptedTreeException on initial index rebuild because there are some items
> with broken links on the root page.
> Reproducer attached.
> Error log:
> {noformat}
> Error during parallel index create/rebuild.
> org.h2.message.DbException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:295)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:251)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.apply(IgniteH2Indexing.java:890)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4320)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:244)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:207)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:166)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.access$100(SchemaIndexCacheVisitorImpl.java:50)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl$AsyncWorker.body(SchemaIndexCacheVisitorImpl.java:317)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.getJdbcS
[jira] [Updated] (IGNITE-9489) CorruptedTreeException on index create.
[
https://issues.apache.org/jira/browse/IGNITE-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-9489:
---
Fix Version/s: (was: 2.8)
2.7.6
> CorruptedTreeException on index create.
> ---
>
> Key: IGNITE-9489
> URL: https://issues.apache.org/jira/browse/IGNITE-9489
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.4, 2.5, 2.6
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Blocker
> Fix For: 2.7.6
>
> Attachments: Test.java
>
>
> Currently on dynamic index drop with enabled persistence H2TreeIndex
> instances aren't destroyed. That means that their root pages aren't removed
> from meta tree (see
> {{org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#getOrAllocateForTree}})
> and reused on subsequent dynamic index create that leads
> CorruptedTreeException on initial index rebuild because there are some items
> with broken links on the root page.
> Reproducer attached.
> Error log:
> {noformat}
> Error during parallel index create/rebuild.
> org.h2.message.DbException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:295)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:251)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.apply(IgniteH2Indexing.java:890)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4320)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:244)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:207)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartitions(SchemaIndexCacheVisitorImpl.java:166)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.access$100(SchemaIndexCacheVisitorImpl.java:50)
> at
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl$AsyncWorker.body(SchemaIndexCacheVisitorImpl.java:317)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@7745722d[ key:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$KeyClass
> [idHash=2038596277, hash=-1388553726, id=1], val:
> org.apache.ignite.internal.processors.cache.index.AbstractSchemaSelfTest$ValueClass
> [idHash=2109544797, hash=-898815788, field1=val1], ver: GridCacheVersion
> [topVer=147733489, order=1536253488473, nodeOrder=2] ][ 1, val1, null ]"
> [5-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> ... 12 more
> Cau
[jira] [Commented] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)
[
https://issues.apache.org/jira/browse/IGNITE-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998135#comment-16998135
]
Ivan Pavlukhin commented on IGNITE-2176:
Moved fix to next versions.
> Not valid exceptions in case when example can't works with remote node
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.5.0.final, 2.7.5
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.9
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
> at
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
> at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
> at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
> 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: java.lang.ClassNotFoundException:
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
> at
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
> ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
> at
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:133
[jira] [Commented] (IGNITE-12424) Fix default query timeout behavior for thin JDBC
[ https://issues.apache.org/jira/browse/IGNITE-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998141#comment-16998141 ] Ivan Pavlukhin commented on IGNITE-12424: - Cherry-picked to 2.8 as https://github.com/apache/ignite/commit/4836d3cafd2cc53332f15c9b257b481f5c69883f > Fix default query timeout behavior for thin JDBC > > > Key: IGNITE-12424 > URL: https://issues.apache.org/jira/browse/IGNITE-12424 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > After IGNITE-7285 there appeared a buggy behavior for thin JDBC driver. > Thin JDBC handles explicit query timeout on a client side. Default query > timeout is tracked on a server side. As a server is not aware of explicit > client timeout it is not possible to override a default timeout with longer > explicit timeout (effectively a query will be cancelled after a default > timeout expiration). > The expected behavior is that an explicit query timeout always overrides a > default one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12370) WAL history reservation may fail due to an incorrect determination of the existence of an archived WAL segment (under race condition).
[
https://issues.apache.org/jira/browse/IGNITE-12370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-12370:
-
Assignee: Pavel Pereslegin
> WAL history reservation may fail due to an incorrect determination of the
> existence of an archived WAL segment (under race condition).
> --
>
> Key: IGNITE-12370
> URL: https://issues.apache.org/jira/browse/IGNITE-12370
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.8
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> For now, {{FileWriteAheadLogManager#hasIndex}} firstly determines that the
> WAL segment *not exists* in an archive ({{File.exists}}) and then determines
> that index *was* in the archive (using {{Files.list}}). If the archive file
> was created between these operations {{hasIndex}} will return the
> false-negative result and the partition map exchange will fail on this node.
> Reproducer:
> {code:java}
> public class IgniteWalHistoryReservationsWithLoadTest extends
> GridCommonAbstractTest {
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String gridName)
> throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(gridName);
> cfg.setConsistentId("NODE$" + gridName.charAt(gridName.length() - 1));
> DataStorageConfiguration memCfg = new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(
> new DataRegionConfiguration()
> .setMaxSize(200L * 1024 * 1024)
> .setPersistenceEnabled(true))
> .setWalMode(WALMode.LOG_ONLY)
> .setWalSegmentSize(512 * 1024)
> .setCheckpointFrequency(500);
> cfg.setDataStorageConfiguration(memCfg);
> CacheConfiguration ccfg1 = new CacheConfiguration();
> ccfg1.setName("cache1");
> ccfg1.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> ccfg1.setAffinity(new RendezvousAffinityFunction(false, 32));
> cfg.setCacheConfiguration(ccfg1);
> return cfg;
> }
> @Test
> public void testReservationWithConstantLoad() throws Exception {
> final IgniteEx node = startGrid(0);
> node.cluster().active(true);
> AtomicLong cntr = new AtomicLong(100_000);
> ConstantLoader ldr = new ConstantLoader(node.cache("cache1"), cntr);
> IgniteInternalFuture fut =
> GridTestUtils.runMultiThreadedAsync(ldr, 1, "loader");
> U.sleep(500);
> forceCheckpoint(node);
> // Reserve history from the beginning.
>
> node.context().cache().context().database().reserveHistoryForExchange();
> long endTime = U.currentTimeMillis() + 60_000;
> GridCacheContext ctx = node.cachex("cache1").context();
> int grpId = ctx.groupId();
> int parts = ctx.topology().partitions();
> try {
> while (U.currentTimeMillis() < endTime &&
> !Thread.currentThread().isInterrupted()) {
> try {
> for (int p = 0; p < parts; p++) {
> boolean reserved =
> node.context().cache().context().database().reserveHistoryForPreloading(grpId,
> p, cntr.get());
> assertTrue("Unable to reserve history [p=" + p + ",
> cntr=" + cntr.get() + "]", reserved);
> }
> } finally {
>
> node.context().cache().context().database().releaseHistoryForPreloading();
> }
> }
> }
> finally {
>
> node.context().cache().context().database().releaseHistoryForExchange();
> ldr.stop();
> }
> fut.get(10_000);
> }
> static class ConstantLoader implements Callable {
> private final IgniteCache cache;
> private final AtomicLong cntr;
> private volatile boolean stop;
> ConstantLoader(IgniteCache cache, AtomicLong cntr) {
> this.cache = cache;
> this.cntr = cntr;
> }
> @Override public Void call() throws Exception {
> while (!stop && !Thread.currentThread().isInterrupted()) {
> long n = cntr.getAndIncrement();
> cache.put(n, n);
> if (n % 100_000 == 0)
> log.info("Loaded " + n);
> }
> return null;
> }
> public void stop() {
> stop = true;
> }
> }
> /** {@inheritDoc} */
> @Override protected void beforeTestsStarted() throws Exception {
> stopAllGrids();
> cleanPersistenceDir();
> }
>
[jira] [Commented] (IGNITE-12403) Throttle page difference output in PageMemoryTracker
[ https://issues.apache.org/jira/browse/IGNITE-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998149#comment-16998149 ] Ilya Kasnacheev commented on IGNITE-12403: -- [~DmitriyGovorukhin] please review proposed test framework fix. > Throttle page difference output in PageMemoryTracker > > > Key: IGNITE-12403 > URL: https://issues.apache.org/jira/browse/IGNITE-12403 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, PageMemoryTracker's dumpBytes will print a line for every byte, > possibly gigabytes of them. Let's limit it up to 64k different bytes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12395) Client nodes fail on SPARC: No session found at TcpCommunicationSpi.createNioSession
[ https://issues.apache.org/jira/browse/IGNITE-12395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12395: - Fix Version/s: 2.9 > Client nodes fail on SPARC: No session found at > TcpCommunicationSpi.createNioSession > > > Key: IGNITE-12395 > URL: https://issues.apache.org/jira/browse/IGNITE-12395 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > This happens when running client nodes from tests with startClient(), since > it does not do optimize() and this causes socket binding issues on Sparc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12395) Client nodes fail on SPARC: No session found at TcpCommunicationSpi.createNioSession
[ https://issues.apache.org/jira/browse/IGNITE-12395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12395: - Labels: test (was: ) > Client nodes fail on SPARC: No session found at > TcpCommunicationSpi.createNioSession > > > Key: IGNITE-12395 > URL: https://issues.apache.org/jira/browse/IGNITE-12395 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Fix For: 2.9 > > Time Spent: 0.5h > Remaining Estimate: 0h > > This happens when running client nodes from tests with startClient(), since > it does not do optimize() and this causes socket binding issues on Sparc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12408) Metrics and SystemView documentation
[ https://issues.apache.org/jira/browse/IGNITE-12408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998159#comment-16998159 ] Artem Budnikov commented on IGNITE-12408: - [~nizhikov] As far as I can see, the most important parts are missing: how to configure exporters; how to get metrics (complete examples); how to use SQL views, how to configure OpenCensus exporter. Users read documentation because they want to find a way to _use_ the functionality. Let's say I want to monitor the number of keys in a specific cache, what should I do to achieve this? It would be nice to have a step by step instruction. > Metrics and SystemView documentation > > > Key: IGNITE-12408 > URL: https://issues.apache.org/jira/browse/IGNITE-12408 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Blocker > Labels: IEP-35 > Fix For: 2.8 > > > We should provide the following documentation > - metric description. > - system view descirption. > - metrics exporter configuration guide. > - system view exporter configuration guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12397) Apache spark - org.apache.ignite.IgniteIllegalStateException
[ https://issues.apache.org/jira/browse/IGNITE-12397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998163#comment-16998163 ] Nikolay Izhikov commented on IGNITE-12397: -- Hello, [~shensonj] Currently, Ignite 2.7 doesn't support Spark 2.4. We provide initial support of Spark 2.4 in Ignite 2.8 Please, see a corresponding ticket IGNITE-12247 I'm closing this ticket as invalid. If you have additional questions don't hesitate to reopen it. > Apache spark - org.apache.ignite.IgniteIllegalStateException > > > Key: IGNITE-12397 > URL: https://issues.apache.org/jira/browse/IGNITE-12397 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7 >Reporter: Shenson Joseph >Priority: Blocker > > Running spark application with apache ignite-2.7.0 throws following exception > This causes spark applications to die.Do we have a work around for this > problem > 9/11/26 16:38:50 INFO CoarseGrainedExecutorBackend: Got assigned task > 1568109/11/26 16:38:50 INFO CoarseGrainedExecutorBackend: Got assigned task > 15681019/11/26 16:38:50 INFO Executor: Running task 0.2 in stage 1564.0 (TID > 156810)19/11/26 16:38:50 ERROR Executor: Exception in task 0.2 in stage > 1564.0 (TID 156810)class org.apache.ignite.IgniteIllegalStateException: > Ignite instance with provided name doesn't exist. Did you call > Ignition.start(..) to start an Ignite instance? [name=shared-grid] at > org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1390) at > org.apache.ignite.Ignition.ignite(Ignition.java:531) at > org.apache.ignite.spark.impl.package$.ignite(package.scala:86) at > org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:226) > at > org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:223) > at org.apache.ignite.spark.Once.apply(IgniteContext.scala:224) at > org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:145) at > org.apache.ignite.spark.impl.IgniteSQLDataFrameRDD.compute(IgniteSQLDataFrameRDD.scala:65) > at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99) at > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:55) at > org.apache.spark.scheduler.Task.run(Task.scala:123) at > org.apache.spark.executor.Executor$TaskRunner$$anonfun$10.apply(Executor.scala:408) > at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360) at > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:414) 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)19/11/26 16:38:50 INFO > CoarseGrainedExecutorBackend: Got assigned task 15681119/11/26 16:38:50 INFO > Executor: Running task 0.3 in stage 1562.0 (TID 156811)19/11/26 16:38:50 > ERROR Executor: Exception in task 0.3 in stage 1562.0 (TID 156811)class > org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided > name doesn't exist. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12397) Apache spark - org.apache.ignite.IgniteIllegalStateException
[ https://issues.apache.org/jira/browse/IGNITE-12397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov resolved IGNITE-12397. -- Resolution: Invalid > Apache spark - org.apache.ignite.IgniteIllegalStateException > > > Key: IGNITE-12397 > URL: https://issues.apache.org/jira/browse/IGNITE-12397 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.7 >Reporter: Shenson Joseph >Priority: Blocker > > Running spark application with apache ignite-2.7.0 throws following exception > This causes spark applications to die.Do we have a work around for this > problem > 9/11/26 16:38:50 INFO CoarseGrainedExecutorBackend: Got assigned task > 1568109/11/26 16:38:50 INFO CoarseGrainedExecutorBackend: Got assigned task > 15681019/11/26 16:38:50 INFO Executor: Running task 0.2 in stage 1564.0 (TID > 156810)19/11/26 16:38:50 ERROR Executor: Exception in task 0.2 in stage > 1564.0 (TID 156810)class org.apache.ignite.IgniteIllegalStateException: > Ignite instance with provided name doesn't exist. Did you call > Ignition.start(..) to start an Ignite instance? [name=shared-grid] at > org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1390) at > org.apache.ignite.Ignition.ignite(Ignition.java:531) at > org.apache.ignite.spark.impl.package$.ignite(package.scala:86) at > org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:226) > at > org.apache.ignite.spark.impl.IgniteRelationProvider$$anonfun$configProvider$1$2.apply(IgniteRelationProvider.scala:223) > at org.apache.ignite.spark.Once.apply(IgniteContext.scala:224) at > org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:145) at > org.apache.ignite.spark.impl.IgniteSQLDataFrameRDD.compute(IgniteSQLDataFrameRDD.scala:65) > at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:52) at > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:324) at > org.apache.spark.rdd.RDD.iterator(RDD.scala:288) at > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99) at > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:55) at > org.apache.spark.scheduler.Task.run(Task.scala:123) at > org.apache.spark.executor.Executor$TaskRunner$$anonfun$10.apply(Executor.scala:408) > at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360) at > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:414) 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)19/11/26 16:38:50 INFO > CoarseGrainedExecutorBackend: Got assigned task 15681119/11/26 16:38:50 INFO > Executor: Running task 0.3 in stage 1562.0 (TID 156811)19/11/26 16:38:50 > ERROR Executor: Exception in task 0.3 in stage 1562.0 (TID 156811)class > org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided > name doesn't exist. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998179#comment-16998179
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov], I made the changes:
GridClient - {{GridClientConfiguration}} received parameter {{Map userAttrs}}. Attributes are passed in the {{GridClientMessage}}.
IgniteClient - {{ClientConfiguration}} received parameter {{Map
userAttrs}}. Attributes are passed through {{TcpClientChannel}}.
JDBC - {{ConnectionProperties}} received parameter {{userAttributes}}, which
should be filled with {{factory>}} name. Attributes are
passed through {{BinaryWriter}} as other message.
ODBC - TODO. I'd like to make it in a separate ticket.
Can you take a look?
> Allow custom authenticators to use SSL certificates
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add SSL certificates to AuthenticationContext, so, authenticators can make
> additional checks based on SSL certificates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12387) .NET Thin Client: Handle unsupported features on older server nodes gracefully
[ https://issues.apache.org/jira/browse/IGNITE-12387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998209#comment-16998209 ] Pavel Tupitsyn commented on IGNITE-12387: - [~ashapkin] PR is ready, please have a look > .NET Thin Client: Handle unsupported features on older server nodes gracefully > -- > > Key: IGNITE-12387 > URL: https://issues.apache.org/jira/browse/IGNITE-12387 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Critical > Labels: .NET > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Right now we don't check server version before doing requests for newer > features like Affinity Awareness and Cluster API. This causes exceptions like > "Invalid re > quest op code: 5000", which are cryptic for the user. > Fix this: > * Affinity Awareness: disable it automatically if there is no server support; > log a warning to the log (add logging by adding > IgniteClientConfiguration.Logger property) > * Individual methods and features like Cluster API - throw an exception with > user-friendly explanation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12453) Cache operations metrics on affinity nodes
[ https://issues.apache.org/jira/browse/IGNITE-12453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-12453: - Labels: IEP-35 (was: ) > Cache operations metrics on affinity nodes > -- > > Key: IGNITE-12453 > URL: https://issues.apache.org/jira/browse/IGNITE-12453 > Project: Ignite > Issue Type: New Feature >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35 > > We should add histogram metrics that measure cache operations times on > affinity nodes: > - get > - put > - remove > - commit > - rollback -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998240#comment-16998240 ] Anton Kalashnikov commented on IGNITE-12227: [~mmuzaf] It's almost finished. I'm just waiting for the tests finishing. > Default auto-adjust baseline enabled flag calculated incorrectly in some cases > -- > > Key: IGNITE-12227 > URL: https://issues.apache.org/jira/browse/IGNITE-12227 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > baselineAutoAdjustEnabled can be been different on different nodes because of > the calculation of default value happening locally on each node and including > only local configuration. It issue can happen by the following reasons: > * If IGNITE_BASELINE_AUTO_ADJUST_ENABLED flag set to a different value on > different nodes it leads to cluster hanging due to baseline calculation > finishing with the unpredictable state on each node. > * if cluster in mixed mode(included in-memory and persistent nodes) sometimes > flag is set to a different value due to calculation doesn't consider remote > nodes configuration. > Possible solution(both points required): > * Get rid of IGNITE_BASELINE_AUTO_ADJUST_ENABLED and replace it by the > explicit call of IgniteCluster#baselineAutoAdjustEnabled where it > required(test only). > * Calculating default value on the first started node as early as > possible(instead of activation) and this value always should be set to > distributed metastorage(unlike it happening now). It means that instead of > awaiting activation, the default value would be calculated by the first > started node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11282) NullPointerException if transaction enabled and using byte[] for key/value
[
https://issues.apache.org/jira/browse/IGNITE-11282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998262#comment-16998262
]
Igor Akkuratov commented on IGNITE-11282:
-
Resolved with https://issues.apache.org/jira/browse/IGNITE-12116
> NullPointerException if transaction enabled and using byte[] for key/value
> --
>
> Key: IGNITE-11282
> URL: https://issues.apache.org/jira/browse/IGNITE-11282
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Courtney
>Assignee: Igor Akkuratov
>Priority: Blocker
> Attachments: Screen Shot 2019-02-10 at 15.02.19.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> I have debugged this and found the problem is because of hashCode comparison
> failure. You can see in the screenshot below.
> {code:java}
> txMap == null ? null : txMap.get(key)
> {code}
> this will fail to get the entry but they the key is in fact in the map, it's
> the only entry and if a proper array comparison is done e.g. using
> `Arrays.equals` as shown in the eval window then the key would match. !Screen
> Shot 2019-02-10 at 15.02.19.png!
> If running without `-ea` then the exception is
> {code:java}
> java.util.concurrent.CompletionException: java.lang.NullPointerException
> at
> java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)
> at
> java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:346)
> at
> java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:632)
> at
> java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at
> java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088)
> at
> io.hypi.arc.ignite.ArcIgniteUtils.lambda$asFuture$f0cf812f$1(ArcIgniteUtils.java:21)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:215)
> at
> org.apache.ignite.internal.util.future.IgniteFutureImpl$InternalFutureListener.apply(IgniteFutureImpl.java:179)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:300)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:287)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:464)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:81)
> at
> org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.ja
[jira] [Created] (IGNITE-12460) Cluster fails to find the node by consistent ID
Anton Kalashnikov created IGNITE-12460: -- Summary: Cluster fails to find the node by consistent ID Key: IGNITE-12460 URL: https://issues.apache.org/jira/browse/IGNITE-12460 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov Steps to reproduce 1: * Start cluster of three nodes * Navigate to Baseline screen * Start one more node * Include it into baseline * Hit 'Save' btn Expected: * Success alert, node enters baseline Actual: * Exception is thrown and is displayed Steps to reproduce 2: # Start topology with 2 nodes. # Activate cluster. # Start third node. # Stop second node. # Try to add third node to baseline in Web console. Also reproduced with *control.sh --baseline set* command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11320) JDBC Thin: add support for individual reconnect in case of best effort affinity mode.
[ https://issues.apache.org/jira/browse/IGNITE-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-11320: -- Parent: IGNITE-11287 Issue Type: Sub-task (was: Task) > JDBC Thin: add support for individual reconnect in case of best effort > affinity mode. > - > > Key: IGNITE-11320 > URL: https://issues.apache.org/jira/browse/IGNITE-11320 > Project: Ignite > Issue Type: Sub-task > Components: jdbc >Reporter: Alexander Lapin >Priority: Major > Labels: iep-23 > Fix For: 2.9 > > > Currently in case of best effort affinity mode we either connect to all nodes > specified by user or throw SQLException. Given logic needs to be improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12462) JDBC thin: add timeouts as the parameters for connection string
Andrey Mashenkov created IGNITE-12462: - Summary: JDBC thin: add timeouts as the parameters for connection string Key: IGNITE-12462 URL: https://issues.apache.org/jira/browse/IGNITE-12462 Project: Ignite Issue Type: Task Components: thin client Reporter: Andrey Mashenkov We've added two new timeouts ([1], [2]) but they're available from java code only and both should be add as the connection string parameters. 1. https://issues.apache.org/jira/browse/IGNITE-5438 2. https://issues.apache.org/jira/browse/IGNITE-5234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12461) Jdbc Thin: Failover connections support for JDBC thin driver.
[ https://issues.apache.org/jira/browse/IGNITE-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-12461: -- Parent: (was: IGNITE-11287) Issue Type: Task (was: Sub-task) > Jdbc Thin: Failover connections support for JDBC thin driver. > - > > Key: IGNITE-12461 > URL: https://issues.apache.org/jira/browse/IGNITE-12461 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > > We need to to support failover connections for JDBC driver. > In case user defined few connection points and server became unavailable > during request, driver should try send the same request to another server. > Please be aware we can do it only for idempotent requests like a SELECT > without transaction context. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11320) JDBC Thin: add support for individual reconnect in case of best effort affinity mode.
[ https://issues.apache.org/jira/browse/IGNITE-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-11320: - Assignee: Andrey Mashenkov > JDBC Thin: add support for individual reconnect in case of best effort > affinity mode. > - > > Key: IGNITE-11320 > URL: https://issues.apache.org/jira/browse/IGNITE-11320 > Project: Ignite > Issue Type: Sub-task > Components: jdbc >Reporter: Alexander Lapin >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-23 > Fix For: 2.9 > > > Currently in case of best effort affinity mode we either connect to all nodes > specified by user or throw SQLException. Given logic needs to be improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12461) Jdbc Thin: Failover connections support for JDBC thin driver.
Andrey Mashenkov created IGNITE-12461: - Summary: Jdbc Thin: Failover connections support for JDBC thin driver. Key: IGNITE-12461 URL: https://issues.apache.org/jira/browse/IGNITE-12461 Project: Ignite Issue Type: Sub-task Components: jdbc Reporter: Andrey Mashenkov We need to to support failover connections for JDBC driver. In case user defined few connection points and server became unavailable during request, driver should try send the same request to another server. Please be aware we can do it only for idempotent requests like a SELECT without transaction context. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12463) Inconsistancy of checkpoint progress future with its state
Anton Kalashnikov created IGNITE-12463: -- Summary: Inconsistancy of checkpoint progress future with its state Key: IGNITE-12463 URL: https://issues.apache.org/jira/browse/IGNITE-12463 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Assignee: Anton Kalashnikov It needs to reorganize checkpoint futures(start, finish) so they should be matched to states. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11320) JDBC Thin: add support for individual reconnect in case of best effort affinity mode.
[ https://issues.apache.org/jira/browse/IGNITE-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-11320: -- Ignite Flags: (was: Docs Required) > JDBC Thin: add support for individual reconnect in case of best effort > affinity mode. > - > > Key: IGNITE-11320 > URL: https://issues.apache.org/jira/browse/IGNITE-11320 > Project: Ignite > Issue Type: Bug > Components: jdbc >Reporter: Alexander Lapin >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-23 > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently in case of best effort affinity mode we either connect to all nodes > specified by user or throw SQLException. Given logic needs to be improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11320) JDBC Thin: add support for individual reconnect in case of best effort affinity mode.
[ https://issues.apache.org/jira/browse/IGNITE-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-11320: -- Parent: (was: IGNITE-11287) Issue Type: Bug (was: Sub-task) > JDBC Thin: add support for individual reconnect in case of best effort > affinity mode. > - > > Key: IGNITE-11320 > URL: https://issues.apache.org/jira/browse/IGNITE-11320 > Project: Ignite > Issue Type: Bug > Components: jdbc >Reporter: Alexander Lapin >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-23 > Fix For: 2.9 > > > Currently in case of best effort affinity mode we either connect to all nodes > specified by user or throw SQLException. Given logic needs to be improved. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12462) JDBC thin: add timeouts as the parameters for connection string
[ https://issues.apache.org/jira/browse/IGNITE-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-12462: -- Fix Version/s: 2.9 > JDBC thin: add timeouts as the parameters for connection string > --- > > Key: IGNITE-12462 > URL: https://issues.apache.org/jira/browse/IGNITE-12462 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > > We've added two new timeouts ([1], [2]) but they're available from java code > only and both should be add as the connection string parameters. > 1. https://issues.apache.org/jira/browse/IGNITE-5438 > 2. https://issues.apache.org/jira/browse/IGNITE-5234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12461) Jdbc Thin: Failover connections support for JDBC thin driver.
[ https://issues.apache.org/jira/browse/IGNITE-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-12461: -- Fix Version/s: 2.9 > Jdbc Thin: Failover connections support for JDBC thin driver. > - > > Key: IGNITE-12461 > URL: https://issues.apache.org/jira/browse/IGNITE-12461 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > > We need to to support failover connections for JDBC driver. > In case user defined few connection points and server became unavailable > during request, driver should try send the same request to another server. > Please be aware we can do it only for idempotent requests like a SELECT > without transaction context. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12461) Jdbc Thin: Failover connections support for JDBC thin driver.
[ https://issues.apache.org/jira/browse/IGNITE-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-12461: - Assignee: Andrey Mashenkov > Jdbc Thin: Failover connections support for JDBC thin driver. > - > > Key: IGNITE-12461 > URL: https://issues.apache.org/jira/browse/IGNITE-12461 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > > We need to to support failover connections for JDBC driver. > In case user defined few connection points and server became unavailable > during request, driver should try send the same request to another server. > Please be aware we can do it only for idempotent requests like a SELECT > without transaction context. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11705) Jdbc Thin: add ability to control affinity cache size.
[ https://issues.apache.org/jira/browse/IGNITE-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-11705: - Assignee: Andrey Mashenkov > Jdbc Thin: add ability to control affinity cache size. > -- > > Key: IGNITE-11705 > URL: https://issues.apache.org/jira/browse/IGNITE-11705 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Alexander Lapin >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-24 > Fix For: 2.9 > > > Within AffinityCache there are two properties DISTRIBUTIONS_CACHE_LIMIT and > SQL_CACHE_LIMIT that are hard coded. We should add an ability to control > given parameters within some sort of configuration. IgniteSystemProperties is > not an option however. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12462) JDBC thin: add timeouts as the parameters for connection string
[ https://issues.apache.org/jira/browse/IGNITE-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-12462: - Assignee: Andrey Mashenkov > JDBC thin: add timeouts as the parameters for connection string > --- > > Key: IGNITE-12462 > URL: https://issues.apache.org/jira/browse/IGNITE-12462 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > > We've added two new timeouts ([1], [2]) but they're available from java code > only and both should be add as the connection string parameters. > 1. https://issues.apache.org/jira/browse/IGNITE-5438 > 2. https://issues.apache.org/jira/browse/IGNITE-5234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-12049: Summary: Add user attributes to thin clients (was: Allow custom authenticators to use SSL certificates) > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add SSL certificates to AuthenticationContext, so, authenticators can make > additional checks based on SSL certificates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-12049: Description: Add user attributes to thin clients (like node attributes for server nodes). Make sure that custom authenticators can use these attributes. (was: Add SSL certificates to AuthenticationContext, so, authenticators can make additional checks based on SSL certificates.) > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12387) .NET Thin Client: Handle unsupported features on older server nodes gracefully
[
https://issues.apache.org/jira/browse/IGNITE-12387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998365#comment-16998365
]
Ignite TC Bot commented on IGNITE-12387:
{panel:title=Branch: [pull/7149/head] Base: [master] : Possible Blockers
(11)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4847539]]
* ZookeeperDiscoverySpiTestSuite2:
IgniteClientReconnectCacheTest.testReconnectExchangeInProgress - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Long Running){color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=4847589]]
* exe: 0.0") - History for base branch is absent.
* exe: 1.0") - History for base branch is absent.
* exe: 1.0") - History for base branch is absent.
* exe: 2.0") - History for base branch is absent.
* exe:
ClientReconnectCompatibilityTest.TestReconnectToOldNodeDisablesPartitionAwareness
- History for base branch is absent.
* exe: 2.0") - History for base branch is absent.
* exe: 2.0") - History for base branch is absent.
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4847591]]
* IgniteBinaryCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 1,1% and is not flaky
{color:#d04437}Client Nodes{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4847506]]
* IgniteClientReconnectTestSuite:
IgniteClientReconnectContinuousProcessorTest.testMessageListenerReconnectAndStopFromServer
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cassandra Store{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4847612]]
* IgniteCassandraStoreTestSuite:
CassandraDirectPersistenceTest.pojoStrategyTransactionTest - Test has low fail
rate in base branch 1,0% and is not flaky
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4847615&buildTypeId=IgniteTests24Java8_RunAll]
> .NET Thin Client: Handle unsupported features on older server nodes gracefully
> --
>
> Key: IGNITE-12387
> URL: https://issues.apache.org/jira/browse/IGNITE-12387
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Labels: .NET
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now we don't check server version before doing requests for newer
> features like Affinity Awareness and Cluster API. This causes exceptions like
> "Invalid re
> quest op code: 5000", which are cryptic for the user.
> Fix this:
> * Affinity Awareness: disable it automatically if there is no server support;
> log a warning to the log (add logging by adding
> IgniteClientConfiguration.Logger property)
> * Individual methods and features like Cluster API - throw an exception with
> user-friendly explanation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12398) Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting down if we connect Ignite Visor Command Line Interface
[
https://issues.apache.org/jira/browse/IGNITE-12398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998366#comment-16998366
]
Maxim Muzafarov commented on IGNITE-12398:
--
[~uday]
Hello, can you help with this one?
It seems this issue is related to IGNITE-7054 (not sure). I can investigate but
have no experience with {{DiscoveryS3IpFinder}} and an environment to check the
fix.
> Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting down if we
> connect Ignite Visor Command Line Interface
> -
>
> Key: IGNITE-12398
> URL: https://issues.apache.org/jira/browse/IGNITE-12398
> Project: Ignite
> Issue Type: Bug
> Components: aws, general, s3, visor
>Affects Versions: 2.7
> Environment: Production
>Reporter: Ravi Kumar Powli
>Priority: Blocker
> Fix For: None, 2.8
>
>
> We have Apache Ignite 3 node cluster setup with Amazon S3 Based Discovery. If
> we connect any one cluster node using Ignite Visor Command Line Interface it
> got hang and automatically cluster nodes(all the three nodes) are going down.
> Please find the below exception stacktrace.
> [SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][] Critical system
> error detected. Will be handled accordingly to configured handler
> [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]
> java.lang.NullPointerException
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.key(TcpDiscoveryS3IpFinder.java:247)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.registerAddresses(TcpDiscoveryS3IpFinder.java:205)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddFinishedMessage(ServerImpl.java:4616)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4232)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2816)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2611)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7188)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:36:54,600][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: GridWorker
> [name=tcp-disco-msg-worker, igniteInstanceName=DataStoreIgniteCache,
> finished=true, heartbeatTs=1574332614423]]]
> class org.apache.ignite.IgniteException: GridWorker
> [name=tcp-disco-msg-worker, igniteInstanceName=DataStoreIgniteCache,
> finished=true, heartbeatTs=1574332614423]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onStopped(WorkersRegistry.java:169)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:153)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:36:59] Ignite node stopped OK [name=DataStoreIgniteCache,
> uptime=00:01:13.934]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12464) Service metrics
Nikolay Izhikov created IGNITE-12464: Summary: Service metrics Key: IGNITE-12464 URL: https://issues.apache.org/jira/browse/IGNITE-12464 Project: Ignite Issue Type: Improvement Affects Versions: 2.7.6 Reporter: Nikolay Izhikov We should provide the following metrics for each deployed service: * Count of executions * Histogram of executions duration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12456) Cluster Data Store grid gets Corrupted for Load test
[ https://issues.apache.org/jira/browse/IGNITE-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Kumar Powli updated IGNITE-12456: -- Reviewer: Maxim Muzafarov > Cluster Data Store grid gets Corrupted for Load test > > > Key: IGNITE-12456 > URL: https://issues.apache.org/jira/browse/IGNITE-12456 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7 >Reporter: Ravi Kumar Powli >Priority: Blocker > Fix For: 2.8 > > Attachments: default-config.xml > > > We have Apache Ignite 3 node cluster setup with Amazon S3 Based Discovery.we > are into AWS cloud environment with Microservice model with 8 > microservices.we are using Ignite for session data store.While performing > load test we are facing data grid issues if the number of clients reached 40 > , Once data grid got corrupted we will lost the session store data and > Application will not respond due to session data also corrupted and all the > instances will auto scaled down to initial size 8.We need to restart Apache > Ignite to make the Application up.Please find the attached Apache Ignite > Configuration for your reference. > Apache Ignite Version : 2.7.0 > 07:24:46,678][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][G] > Blocked system-critical thread has been detected. This can lead to > cluster-wide undefined behaviour [threadName=sys-stripe-5, > blockedFor=21s]07:24:46,678][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][G] > Blocked system-critical thread has been detected. This can lead to > cluster-wide undefined behaviour [threadName=sys-stripe-5, > blockedFor=21s][07:24:46,680][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][] > Critical system error detected. Will be handled accordingly to configured > handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler > [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext > [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker > [name=sys-stripe-5, igniteInstanceName=DataStoreIgniteCache, finished=false, > heartbeatTs=1575271465499]]]class org.apache.ignite.IgniteException: > GridWorker [name=sys-stripe-5, igniteInstanceName=DataStoreIgniteCache, > finished=false, heartbeatTs=1575271465499] at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826) > at > org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233) > at > org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2663) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7181) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119) > at > org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)[07:24:52,692][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][G] > Blocked system-critical thread has been detected. This can lead to > cluster-wide undefined behaviour [threadName=ttl-cleanup-worker, > blockedFor=27s][07:24:52,692][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][] > Critical system error detected. Will be handled accordingly to configured > handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler > [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext > [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker > [name=ttl-cleanup-worker, igniteInstanceName=DataStoreIgniteCache, > finished=false, heartbeatTs=1575271465044]]]class > org.apache.ignite.IgniteException: GridWorker [name=ttl-cleanup-worker, > igniteInstanceName=DataStoreIgniteCache, finished=false, > heartbeatTs=1575271465044] at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826) > at > org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233) > at > org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2663) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7181) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700) > at > org.a
[jira] [Created] (IGNITE-12465) Extend test coverage [IGNITE-11995] control.sh if experimental command disabled - don't show help for experemental commands
Kirill Tkalenko created IGNITE-12465: Summary: Extend test coverage [IGNITE-11995] control.sh if experimental command disabled - don't show help for experemental commands Key: IGNITE-12465 URL: https://issues.apache.org/jira/browse/IGNITE-12465 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.8 Extend test coverage for IGNITE-11995 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[
https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998878#comment-16998878
]
Ignite TC Bot commented on IGNITE-12193:
{panel:title=Branch: [pull/6960/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4847357&buildTypeId=IgniteTests24Java8_RunAll]
> [Phase-1] Rebalancing cache group keys metric counters
> --
>
> Key: IGNITE-12193
> URL: https://issues.apache.org/jira/browse/IGNITE-12193
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Maxim Muzafarov
>Assignee: Nikolai Kulagin
>Priority: Critical
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Implement metrics counters related to the cache group:
> * rebalancingPartitionsLeft long metric
> * rebalancingReceivedKeys long metric
> * rebalancingReceivedBytes long metric
> * rebalancingStartTime long metric
> * rebalancingFinishTime long metric
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12194) [Phase-2] Calculate expected rebalancing cache group keys
[ https://issues.apache.org/jira/browse/IGNITE-12194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolai Kulagin reassigned IGNITE-12194: Assignee: Nikolai Kulagin > [Phase-2] Calculate expected rebalancing cache group keys > - > > Key: IGNITE-12194 > URL: https://issues.apache.org/jira/browse/IGNITE-12194 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Critical > Labels: IEP-35 > Fix For: 2.8 > > > We need to implement expected to be rebalanced cache group keys and total > bytes. Currently, 'estimatedKeysCount' cache metric returns '-1' for some of > the cases (see comments IGNITE-11330). > * rebalancingExpectedKeys long metric > * rebalancingExpectedBytes long metric > * rebalancingEvictedPartitionsLeft long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12344) Remote listener of IgniteMessaging has to run with appropriate SecurityContext.
[ https://issues.apache.org/jira/browse/IGNITE-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus reassigned IGNITE-12344: Assignee: Denis Garus > Remote listener of IgniteMessaging has to run with appropriate > SecurityContext. > --- > > Key: IGNITE-12344 > URL: https://issues.apache.org/jira/browse/IGNITE-12344 > Project: Ignite > Issue Type: Bug >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-38 > > Remote listener of IgniteMessaging has to run on a remote node with the > SecurityContext of the initiator node. -- This message was sent by Atlassian Jira (v8.3.4#803005)
