[jira] [Updated] (IGNITE-8799) Web agent hides connection exceptions
[ https://issues.apache.org/jira/browse/IGNITE-8799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8799: - Component/s: (was: visor) wizards > Web agent hides connection exceptions > - > > Key: IGNITE-8799 > URL: https://issues.apache.org/jira/browse/IGNITE-8799 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Major > Fix For: 2.7 > > > Web agent hides connection exceptions and this discourage analysis of > connection problems -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8799) Web agent hides connection exceptions
[ https://issues.apache.org/jira/browse/IGNITE-8799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-8799: - Fix Version/s: 2.7 > Web agent hides connection exceptions > - > > Key: IGNITE-8799 > URL: https://issues.apache.org/jira/browse/IGNITE-8799 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Major > Fix For: 2.7 > > > Web agent hides connection exceptions and this discourage analysis of > connection problems -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8799) Web agent hides connection exceptions
[ https://issues.apache.org/jira/browse/IGNITE-8799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8799. > Web agent hides connection exceptions > - > > Key: IGNITE-8799 > URL: https://issues.apache.org/jira/browse/IGNITE-8799 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Mikhail Cherkasov >Assignee: Mikhail Cherkasov >Priority: Major > Fix For: 2.7 > > > Web agent hides connection exceptions and this discourage analysis of > connection problems -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7752) Update Ignite KafkaStreamer to use new KafkaConsmer configuration.
[ https://issues.apache.org/jira/browse/IGNITE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564759#comment-16564759 ] Andrew Mashenkov commented on IGNITE-7752: -- [~roman_s], * *Now PR looks good for me. * Looks like there was a bug with consumer reconnection in earlier versions. Ok. Let's left this as is. * Sorry, I missed smth, there is no loop. All look good. > Update Ignite KafkaStreamer to use new KafkaConsmer configuration. > -- > > Key: IGNITE-7752 > URL: https://issues.apache.org/jira/browse/IGNITE-7752 > Project: Ignite > Issue Type: Task > Components: streaming >Reporter: Andrew Mashenkov >Assignee: Roman Shtykh >Priority: Major > Labels: newbie, streaming > Fix For: 2.7 > > > Seems, for now it is impossible to use new style KafkaConsumer configuration > in KafkaStreamer. > The issue here is Ignite use > kafka.consumer.Consumer.createJavaConsumerConnector() method which creates > old consumer (ZookeeperConsumerConnector). > We should create a new KafkaConsumer instead which looks like support both, > old and new style configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9143: - Description: Create a new notebook. Start writing a new query (it is better to input string like "12345"). !screenshot-1.png! was: Create a new notebook. Start writing a new query. !screenshot-1.png! > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query (it is better to input string like "12345"). > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9143: - Fix Version/s: (was: 2.7) > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query (it is better to input string like "12345"). > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9143: Assignee: Ilya Borisov (was: Alexey Kuznetsov) [~Klaster_1], Could you investigate this issue? It seems that this issue reproduced only under FireFox. For some reason changes in sql input do not trigger digest cycle. > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9143: - Fix Version/s: 2.7 > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7752) Update Ignite KafkaStreamer to use new KafkaConsmer configuration.
[
https://issues.apache.org/jira/browse/IGNITE-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564713#comment-16564713
]
Roman Shtykh commented on IGNITE-7752:
--
[~amashenkov] Thank you for having a look.
* Added javadoc comments.
* Honestly, I am not aware of this (resubscribing).
The _poll_ method says {color:#629755}@throws
{color}{color:#629755}org.apache.kafka.common.KafkaException for any other
unrecoverable errors{color}. I don't think we can do something here, just fail
(I will add an error message to log). Normally you have several brokers with
_n_ replication, so having your whole Kafka cluster is a rare case.
Do you recommend to resubscribe? (Looks like it's a consumer's job)
* I can't find any infinite loop. Can you explain?
> Update Ignite KafkaStreamer to use new KafkaConsmer configuration.
> --
>
> Key: IGNITE-7752
> URL: https://issues.apache.org/jira/browse/IGNITE-7752
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Reporter: Andrew Mashenkov
>Assignee: Roman Shtykh
>Priority: Major
> Labels: newbie, streaming
> Fix For: 2.7
>
>
> Seems, for now it is impossible to use new style KafkaConsumer configuration
> in KafkaStreamer.
> The issue here is Ignite use
> kafka.consumer.Consumer.createJavaConsumerConnector() method which creates
> old consumer (ZookeeperConsumerConnector).
> We should create a new KafkaConsumer instead which looks like support both,
> old and new style configs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov closed IGNITE-9136.
--
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
[ https://issues.apache.org/jira/browse/IGNITE-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9150: --- Component/s: wizards > Web console: incorrect text of cluster acivation component in corner case > -- > > Key: IGNITE-9150 > URL: https://issues.apache.org/jira/browse/IGNITE-9150 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > # deactivate a cluster > # switch to cluster w\o persistent > # switch back to the first cluster > - component prints 'Activating' but should 'Deactivating' > The reason is that Ignite has no it own state 'activating(deactivating) in > progress' and the current implementation on frontend is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
[ https://issues.apache.org/jira/browse/IGNITE-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9150: --- Description: # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation on frontend is a workaround only. was: # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation on fronend is a workaround only. > Web console: incorrect text of cluster acivation component in corner case > -- > > Key: IGNITE-9150 > URL: https://issues.apache.org/jira/browse/IGNITE-9150 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > # deactivate a cluster > # switch to cluster w\o persistent > # switch back to the first cluster > - component prints 'Activating' but should 'Deactivating' > The reason is that Ignite has no it own state 'activating(deactivating) in > progress' and the current implementation on frontend is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
[ https://issues.apache.org/jira/browse/IGNITE-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9150: --- Description: # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation on fronend is a workaround only. was: # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation is a workaround only. > Web console: incorrect text of cluster acivation component in corner case > -- > > Key: IGNITE-9150 > URL: https://issues.apache.org/jira/browse/IGNITE-9150 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > # deactivate a cluster > # switch to cluster w\o persistent > # switch back to the first cluster > - component prints 'Activating' but should 'Deactivating' > The reason is that Ignite has no it own state 'activating(deactivating) in > progress' and the current implementation on fronend is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564706#comment-16564706
]
Pavel Konstantinov commented on IGNITE-9136:
A new issue created https://issues.apache.org/jira/browse/IGNITE-9150
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
[ https://issues.apache.org/jira/browse/IGNITE-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9150: --- Ignite Flags: (was: Docs Required) > Web console: incorrect text of cluster acivation component in corner case > -- > > Key: IGNITE-9150 > URL: https://issues.apache.org/jira/browse/IGNITE-9150 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Priority: Major > > # deactivate a cluster > # switch to cluster w\o persistent > # switch back to the first cluster > - component prints 'Activating' but should 'Deactivating' > The reason is that Ignite has no it own state 'activating(deactivating) in > progress' and the current implementation is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9150) Web console: incorrect text of cluster acivation component in corner case
Pavel Konstantinov created IGNITE-9150: -- Summary: Web console: incorrect text of cluster acivation component in corner case Key: IGNITE-9150 URL: https://issues.apache.org/jira/browse/IGNITE-9150 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov # deactivate a cluster # switch to cluster w\o persistent # switch back to the first cluster - component prints 'Activating' but should 'Deactivating' The reason is that Ignite has no it own state 'activating(deactivating) in progress' and the current implementation is a workaround only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-9136:
Assignee: Pavel Konstantinov (was: Alexey Kuznetsov)
The root cause of last error is not connected to latest changes.
The main reason - it is hard to detect whether cluster in activating or
deactivating (no such state on cluster itself).
If you wish, you could create separate issue to store "inProgress" state for
each cluster, but this will work only if user will not refresh page in browser
and not open different tab.
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller
[ https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564686#comment-16564686 ] Calvin Wong commented on IGNITE-9054: - Hi, Can we include this in next release? Thanks, Calvin > ScanQuery responses are serialized with Optimized Marshaller > > > Key: IGNITE-9054 > URL: https://issues.apache.org/jira/browse/IGNITE-9054 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Priority: Major > Labels: easyfix > Attachments: 22530.diff > > > When you do ContinuousQuery on a cache, its initial query sends results via > OptimizedMarshaller (which has binary compatibility implications) but its > continuous part uses BinaryMarshaller. They should both be using > BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9137: Assignee: Pavel Konstantinov (was: Dmitriy Shabalin) Fixed. > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9137: - Ignite Flags: (was: Docs Required) > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9137: -- Assignee: Dmitriy Shabalin (was: Pavel Konstantinov) > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564644#comment-16564644 ] Pavel Konstantinov edited comment on IGNITE-9137 at 8/1/18 2:28 AM: !screenshot-2.png! please make the width of the 'Node IP' and 'Grid Name' columns a bit more and OS info a bit less. was (Author: pkonstantinov): !screenshot-2.png! please make the width of the first and second columns a bit more and OS info a bit less. > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564644#comment-16564644 ] Pavel Konstantinov commented on IGNITE-9137: !screenshot-2.png! please make the width of the first and second columns a bit more and OS info a bit less. > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9137: --- Attachment: screenshot-2.png > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png, screenshot-2.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reopened IGNITE-9136:
Assignee: Alexey Kuznetsov (was: Pavel Konstantinov)
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564630#comment-16564630
]
Pavel Konstantinov commented on IGNITE-9136:
One little error still exists -
# deactivate a cluster
# switch to cluster w\o persistent
# switch back to the first cluster
- component prints 'Activating' but should 'Deactivating'
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8939) Transaction string reprsentation unhandled exception
[
https://issues.apache.org/jira/browse/IGNITE-8939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564178#comment-16564178
]
Stanilovsky Evgeny commented on IGNITE-8939:
looks good for me
> Transaction string reprsentation unhandled exception
>
>
> Key: IGNITE-8939
> URL: https://issues.apache.org/jira/browse/IGNITE-8939
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Reporter: Evgenii Zagumennov
>Assignee: Stanilovsky Evgeny
>Priority: Major
>
> IgniteTxHandler.finishDhtLocal() (IgniteTxHandler.java:957)
> {code:java}
> U.error(log, "Failed completing transaction [commit=" + req.commit() + ",
> tx=" + *tx* + ']', e);{code}
> tx.toString() can lead to excepion (in GridToStringBuilder.toStringImpl()),
> and original exception in transaction will be lost. We need to log original
> exception and catch probable tx.toString() exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-9149:
Summary: Get rid of logging remaining supplier nodes rebalance time (was:
Get rid of logging remaining supllier nodes rebalance time)
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7165) Re-balancing is cancelled if client node joins
[ https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563969#comment-16563969 ] Maxim Muzafarov edited comment on IGNITE-7165 at 7/31/18 4:53 PM: -- *Improvements created* IGNITE-9149 – Get rid of logging remaining supplier nodes rebalance time IGNITE-9119 – Missed dumpDebugInfo for rebalance was (Author: mmuzaf): *Improvements created* IGNITE-9149 – Get rid of logging remaining supllier nodes rebalance time IGNITE-9119 – Missed dumpDebugInfo for rebalance > Re-balancing is cancelled if client node joins > -- > > Key: IGNITE-7165 > URL: https://issues.apache.org/jira/browse/IGNITE-7165 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Labels: rebalance > Fix For: 2.7 > > > Re-balancing is canceled if client node joins. Re-balancing can take hours > and each time when client node joins it starts again: > [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, > 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, > /172.31.16.213:0], discPort=0, order=36, intOrder=24, > lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, > isClient=true] > [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, > customEvt=null, allowMerge=true] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, > minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > err=null] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false] > [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion > [topVer=36, minorTopVer=0], evt=NODE_JOINED, > node=979cf868-1c37-424a-9ad1-12db501f32ef] > [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion > [topVer=35, minorTopVer=0]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing scheduled [order=[statementp]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing started [top=null, evt=NODE_JOINED, > node=a8be3c14-9add-48c3-b099-3fd304cfdbf4] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > so in clusters with a big amount of data and
[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins
[ https://issues.apache.org/jira/browse/IGNITE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563969#comment-16563969 ] Maxim Muzafarov commented on IGNITE-7165: - *Improvements created* IGNITE-9149 – Get rid of logging remaining supllier nodes rebalance time IGNITE-9119 – Missed dumpDebugInfo for rebalance > Re-balancing is cancelled if client node joins > -- > > Key: IGNITE-7165 > URL: https://issues.apache.org/jira/browse/IGNITE-7165 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Cherkasov >Assignee: Maxim Muzafarov >Priority: Critical > Labels: rebalance > Fix For: 2.7 > > > Re-balancing is canceled if client node joins. Re-balancing can take hours > and each time when client node joins it starts again: > [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, > 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, > /172.31.16.213:0], discPort=0, order=36, intOrder=24, > lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, > isClient=true] > [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] > Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, > customEvt=null, allowMerge=true] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, > minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > err=null] > [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished > exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], > crd=false] > [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion > [topVer=36, minorTopVer=0], evt=NODE_JOINED, > node=979cf868-1c37-424a-9ad1-12db501f32ef] > [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion > [topVer=35, minorTopVer=0]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing scheduled [order=[statementp]] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] > Rebalancing started [top=null, evt=NODE_JOINED, > node=a8be3c14-9add-48c3-b099-3fd304cfdbf4] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] > Starting rebalancing [mode=ASYNC, > fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, > topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], > updateSeq=-1754630006] > so in clusters with a big amount of data and the frequent client left/join > events this means that a new server will never receive its partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563971#comment-16563971 ] Oleg Ignatenko commented on IGNITE-9146: https://github.com/gridgain/apache-ignite/tree/ignite-9146 > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9149) Get rid of logging remaining supllier nodes rebalance time
Maxim Muzafarov created IGNITE-9149:
---
Summary: Get rid of logging remaining supllier nodes rebalance time
Key: IGNITE-9149
URL: https://issues.apache.org/jira/browse/IGNITE-9149
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Logging rebalance execution time in section of each supplier node have no sence
and provides no helpfull info for analyzing logs. It also overcomplicates
{{GridDhtPartitionDemander}}.
I'm suggesting remove it by simplifying {{Map>}} to {{Map}}.
{code:java}
/** Remaining. T2: startTime, partitions */
private final Map> remaining =
new HashMap<>();
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9134) ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME
[
https://issues.apache.org/jira/browse/IGNITE-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Biryukov updated IGNITE-9134:
-
Description:
{noformat}
java.lang.OutOfMemoryError: Java heap space
at java.lang.reflect.Array.newInstance(Array.java:75)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1671)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at
org.apache.ignite.internal.util.IgniteUtils.readMap(IgniteUtils.java:5179)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperClusterNode.readExternal(ZookeeperClusterNode.java:365)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:139)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalZip(ZookeeperDiscoveryImpl.java:3925)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalJoinData(ZookeeperDiscoveryImpl.java:1824)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2779)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2628)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2603)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.access$2000(ZookeeperDiscoveryImpl.java:108)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl$ZkWatcher.processResult(ZookeeperDiscoveryImpl.java:4113)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient$DataCallbackWrapper.processResult(ZookeeperClient.java:1219)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)
{noformat}
was:
java.lang.OutOfMemoryError: Java heap space
at java.lang.reflect.Array.newInstance(Array.java:75)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1671)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at
org.apache.ignite.internal.util.IgniteUtils.readMap(IgniteUtils.java:5179)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperClusterNode.readExternal(ZookeeperClusterNode.java:365)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:139)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalZip(ZookeeperDiscoveryImpl.java:3925)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalJoinData(ZookeeperDiscoveryImpl.java:1824)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2779)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2628)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2603)
at
[jira] [Updated] (IGNITE-9134) ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME
[ https://issues.apache.org/jira/browse/IGNITE-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaliy Biryukov updated IGNITE-9134: - Description: java.lang.OutOfMemoryError: Java heap space at java.lang.reflect.Array.newInstance(Array.java:75) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1671) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) at org.apache.ignite.internal.util.IgniteUtils.readMap(IgniteUtils.java:5179) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperClusterNode.readExternal(ZookeeperClusterNode.java:365) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) at org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:139) at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalZip(ZookeeperDiscoveryImpl.java:3925) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalJoinData(ZookeeperDiscoveryImpl.java:1824) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2779) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2628) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2603) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.access$2000(ZookeeperDiscoveryImpl.java:108) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl$ZkWatcher.processResult(ZookeeperDiscoveryImpl.java:4113) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient$DataCallbackWrapper.processResult(ZookeeperClient.java:1219) at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561) at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) > ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME > - > > Key: IGNITE-9134 > URL: https://issues.apache.org/jira/browse/IGNITE-9134 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > java.lang.OutOfMemoryError: Java heap space > at java.lang.reflect.Array.newInstance(Array.java:75) > at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1671) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) > at > org.apache.ignite.internal.util.IgniteUtils.readMap(IgniteUtils.java:5179) > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperClusterNode.readExternal(ZookeeperClusterNode.java:365) > at > java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1842) > at > java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1799) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) > at > java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924) > at > java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) > at > org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:139) > at > org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94) > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.unmarshalZip(ZookeeperDiscoveryImpl.java:3925) > at >
[jira] [Created] (IGNITE-9148) Split Cache 3 TC configuration.
Pavel Pereslegin created IGNITE-9148: Summary: Split Cache 3 TC configuration. Key: IGNITE-9148 URL: https://issues.apache.org/jira/browse/IGNITE-9148 Project: Ignite Issue Type: Improvement Reporter: Pavel Pereslegin Assignee: Pavel Pereslegin Cache 3 TC configuration takes too long time to complete (>1.5h) and should be split into two. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8365) Introduce service failure events
[
https://issues.apache.org/jira/browse/IGNITE-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Daradur reassigned IGNITE-8365:
--
Assignee: Vyacheslav Daradur
> Introduce service failure events
>
>
> Key: IGNITE-8365
> URL: https://issues.apache.org/jira/browse/IGNITE-8365
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
>Reporter: Denis Mekhanikov
>Assignee: Vyacheslav Daradur
>Priority: Major
> Labels: iep-17
>
> When a deployed service is propagated to a new node, and it fails to
> initialize, then a corresponding system event should be triggered in the
> cluster.
> This way a user will be able to handle situations, when services can't be
> deployed on joining nodes.
> Also, exceptions thrown from {{Service#execute}} method should trigger
> corresponding events.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-9146: --- Ignite Flags: (was: Docs Required) > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9124) Remove some dead code in math.exceptions and optimization packages of ML module
[ https://issues.apache.org/jira/browse/IGNITE-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-9124: --- Ignite Flags: (was: Docs Required) > Remove some dead code in math.exceptions and optimization packages of ML > module > --- > > Key: IGNITE-9124 > URL: https://issues.apache.org/jira/browse/IGNITE-9124 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Doing code coverage analysis discovered a bit of unused code: > # in package > [math.exceptions|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/math/exceptions] > - classes ConvergenceException / MathIllegalStateException, > InsufficientDataException, MathIllegalNumberException / > NumberIsTooSmallException, NonPositiveDefiniteMatrixException, > NonSymmetricMatrixException, NullArgumentException, SingularMatrixException, > UnknownProviderException. In very early releases of ML these exceptions were > used by some linear algebra code. This code has been very deeply reworked > since but outdated exceptions were left hanging unattended, making rather > confusing impression of the current API. > # in > [optimization|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/optimization] > - interface Updater and two classes implementing it: BarzilaiBorweinUpdater > and SimpleUpdater. This code has left hanging after cleanup that was made for > release 2.5 (IGNITE-8232). Per my discussion with [~dmitrievanthony] (who > most actively maintains this package) it would be better to remove this code. > This task is to remove code mentioned above. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9146) Analyse and improve code coverage in ML module
[
https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563792#comment-16563792
]
Oleg Ignatenko edited comment on IGNITE-9146 at 7/31/18 3:32 PM:
-
Attached preliminary coverage report: [^20180731-ml-coverage.zip] (note it
accounts for removal of some dead code that was performed per IGNITE-9124)
This data is supposed to be a combined coverage obtained by running examples
from
[IgniteExamplesMLTestSuite|https://github.com/apache/ignite/blob/master/examples/src/test/java/org/apache/ignite/testsuites/IgniteExamplesMLTestSuite.java]
and [unit and performance tests in ML
module|https://github.com/apache/ignite/tree/master/modules/ml/src/test].
Overall it looks fairly okay and needing only relatively minor improvements.
Per brief study of this data it looks like the following things need to be done:
# Ensure that {{IgniteExamplesMLTestSuite}} launches all examples that are
possible to run automatically. Currently it looks like missing some (eg
{{tutorial}} and {{tree}} examples), which is not good because as a result
Teamcity build can't reliably tell whether all examples can run out of the box
or not. Examples not invoked from this test suite need to be discovered and
either integrated into it or somehow documented in test suite comments with the
explanation of why these should not be run from it.
# Ensure that in unit tests, invoking
[IgniteMLTestSuite|https://github.com/apache/ignite/blob/master/modules/ml/src/test/java/org/apache/ignite/ml/IgniteMLTestSuite.java]
provides as much coverage as possible:
## If some unit tests aren't yet invoked from the test suite, these need to be
integrated
## If some tests can't be executed from this test suite, these need to be
documented in comments (eg tests in package
{{org.apache.ignite.ml.nn.performance}})
## If some important unit tests are missing these need to be added (eg for
{{org.apache.ignite.ml.optimization.LossFunctions}}).
Note consider that for really important functionality it may be insufficient to
have it covered only in examples but also a proper verification in module unit
tests should be added.
was (Author: oignatenko):
attached preliminary coverage report: [^20180731-ml-coverage.zip] (note it
accounts for removal of some dead code that was performed per IGNITE-9124)
> Analyse and improve code coverage in ML module
> --
>
> Key: IGNITE-9146
> URL: https://issues.apache.org/jira/browse/IGNITE-9146
> Project: Ignite
> Issue Type: Task
> Components: ml
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: 20180731-ml-coverage.zip
>
>
> Run code coverage analysis, study results and add missing tests where needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9147) When server node left cluster on high load, cluster take hang on PartitionalExchange
[ https://issues.apache.org/jira/browse/IGNITE-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563840#comment-16563840 ] ARomantsov commented on IGNITE-9147: I restarted the test 7 times, two of them repeated this situation > When server node left cluster on high load, cluster take hang on > PartitionalExchange > > > Key: IGNITE-9147 > URL: https://issues.apache.org/jira/browse/IGNITE-9147 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.5 >Reporter: ARomantsov >Priority: Critical > Fix For: 2.7 > > > I ran a simple test > 1) Start 15 servers node > 2) Start client with long transaction > 3) Additional start 5 client with loading in many caches (near 2 thousand) > 4) Stop 1 server node, wait 1 minute and start it back > Cluster freenze on more than hour, then license end -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9147) When server node left cluster on high load, cluster take hang on PartitionalExchange
ARomantsov created IGNITE-9147: -- Summary: When server node left cluster on high load, cluster take hang on PartitionalExchange Key: IGNITE-9147 URL: https://issues.apache.org/jira/browse/IGNITE-9147 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 I ran a simple test 1) Start 15 servers node 2) Start client with long transaction 3) Additional start 5 client with loading in many caches (near 2 thousand) 4) Stop 1 server node, wait 1 minute and start it back Cluster freenze on more than hour, then license end -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563792#comment-16563792 ] Oleg Ignatenko commented on IGNITE-9146: attached preliminary coverage report: [^20180731-ml-coverage.zip] (note it accounts for removal of some dead code that was performed per IGNITE-9124) > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko updated IGNITE-9146: --- Attachment: 20180731-ml-coverage.zip > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > Attachments: 20180731-ml-coverage.zip > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9146) Analyse and improve code coverage in ML module
[ https://issues.apache.org/jira/browse/IGNITE-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Ignatenko reassigned IGNITE-9146: -- Assignee: Oleg Ignatenko Fix Version/s: 2.7 > Analyse and improve code coverage in ML module > -- > > Key: IGNITE-9146 > URL: https://issues.apache.org/jira/browse/IGNITE-9146 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8180) ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563786#comment-16563786
]
ASF GitHub Bot commented on IGNITE-8180:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4203
> ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
> ---
>
> Key: IGNITE-8180
> URL: https://issues.apache.org/jira/browse/IGNITE-8180
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails on TC with the following stack trace:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testQuorumRestore(ZookeeperDiscoverySpiTest.java:1077)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:40921,127.0.0.1:35014,127.0.0.1:38754,
> joinTimeout=0, sesTimeout=15000, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 20 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> ... 22 more
> Caused by:
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClientFailedException:
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /apacheIgnite
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.onZookeeperError(ZookeeperClient.java:758)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.exists(ZookeeperClient.java:276)
> at
>
[jira] [Created] (IGNITE-9146) Analyse and improve code coverage in ML module
Oleg Ignatenko created IGNITE-9146: -- Summary: Analyse and improve code coverage in ML module Key: IGNITE-9146 URL: https://issues.apache.org/jira/browse/IGNITE-9146 Project: Ignite Issue Type: Task Components: ml Affects Versions: 2.6 Reporter: Oleg Ignatenko Run code coverage analysis, study results and add missing tests where needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8180) ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8180:
---
Fix Version/s: 2.7
> ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
> ---
>
> Key: IGNITE-8180
> URL: https://issues.apache.org/jira/browse/IGNITE-8180
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails on TC with the following stack trace:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testQuorumRestore(ZookeeperDiscoverySpiTest.java:1077)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:40921,127.0.0.1:35014,127.0.0.1:38754,
> joinTimeout=0, sesTimeout=15000, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 20 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> ... 22 more
> Caused by:
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClientFailedException:
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /apacheIgnite
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.onZookeeperError(ZookeeperClient.java:758)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.exists(ZookeeperClient.java:276)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:789)
> ... 27 more
> Caused by:
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[
https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563776#comment-16563776
]
ASF GitHub Bot commented on IGNITE-9130:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4458
> ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
>
>
> Key: IGNITE-9130
> URL: https://issues.apache.org/jira/browse/IGNITE-9130
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Fail:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> A new error that throws instead of the old one:
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
> statement:
> CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
> BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
> VARCHAR, HOSTNAMES VARCHAR) ENGINE
> "org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
> [42101-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.command.ddl.CreateTable.update(CreateTable.java:117)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
> at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
> at
> org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine.registerView(SqlSystemTableEngine.java:48)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2608)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8582) MVCC TX: Cache store read-through support
[ https://issues.apache.org/jira/browse/IGNITE-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563740#comment-16563740 ] Ivan Pavlukhin commented on IGNITE-8582: Currently all 3rd-party persistence track was postponed as it requires careful rethinking. > MVCC TX: Cache store read-through support > - > > Key: IGNITE-8582 > URL: https://issues.apache.org/jira/browse/IGNITE-8582 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Sergey Kalashnikov >Assignee: Ivan Pavlukhin >Priority: Major > Labels: mvcc, sql > > Add support for read-through cache store for mvcc caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9114) Fail fast in org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
[ https://issues.apache.org/jira/browse/IGNITE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563737#comment-16563737 ] ASF GitHub Bot commented on IGNITE-9114: Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/4460 > Fail fast in > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > - > > Key: IGNITE-9114 > URL: https://issues.apache.org/jira/browse/IGNITE-9114 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > has infinite loop with exit condition on success, thus failure to make > reservation on partition can "hang" query. Exception should be thrown and > method should return if cycle does not succeed in reasonable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9124) Remove some dead code in math.exceptions and optimization packages of ML module
[ https://issues.apache.org/jira/browse/IGNITE-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563739#comment-16563739 ] ASF GitHub Bot commented on IGNITE-9124: GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/4462 IGNITE-9124 Remove some dead code in ML module You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9124 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4462.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4462 commit 6a92b001d65c8f39f88edf53c2487c4f32929f42 Author: Oleg Ignatenko Date: 2018-07-30T15:55:20Z IGNITE-9124 Remove some dead code in math.exceptions and optimization packages of ML module - draft removal -- verified with diffs overview and clean rebuild commit 566b8e35e92d4aa39c5a79ff12f1defae9552d1e Author: Oleg Ignatenko Date: 2018-07-31T14:00:09Z IGNITE-9124 Remove some dead code in math.exceptions and optimization packages of ML module - removal completed -- verified with diffs overview and clean rebuild commit d71ddd0c9a987d98d10b38f9cf47b5ed237977e0 Author: Oleg Ignatenko Date: 2018-07-31T14:02:00Z Merge branch 'master-ml' into ignite-9124 > Remove some dead code in math.exceptions and optimization packages of ML > module > --- > > Key: IGNITE-9124 > URL: https://issues.apache.org/jira/browse/IGNITE-9124 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Doing code coverage analysis discovered a bit of unused code: > # in package > [math.exceptions|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/math/exceptions] > - classes ConvergenceException / MathIllegalStateException, > InsufficientDataException, MathIllegalNumberException / > NumberIsTooSmallException, NonPositiveDefiniteMatrixException, > NonSymmetricMatrixException, NullArgumentException, SingularMatrixException, > UnknownProviderException. In very early releases of ML these exceptions were > used by some linear algebra code. This code has been very deeply reworked > since but outdated exceptions were left hanging unattended, making rather > confusing impression of the current API. > # in > [optimization|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/optimization] > - interface Updater and two classes implementing it: BarzilaiBorweinUpdater > and SimpleUpdater. This code has left hanging after cleanup that was made for > release 2.5 (IGNITE-8232). Per my discussion with [~dmitrievanthony] (who > most actively maintains this package) it would be better to remove this code. > This task is to remove code mentioned above. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9145) [ML] Add different strategies to index labels in StringEncoderTrainer
Aleksey Zinoviev created IGNITE-9145: Summary: [ML] Add different strategies to index labels in StringEncoderTrainer Key: IGNITE-9145 URL: https://issues.apache.org/jira/browse/IGNITE-9145 Project: Ignite Issue Type: Improvement Components: ml Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.7 The main idea to add a few strategies of indexing: sorting and so on. Currently it supports only one strategy (most popular with zero and less popular with the max index size). There are can be a few options * 'frequencyDesc': descending order by label frequency (most frequent label assigned 0) * 'frequencyAsc': ascending order by label frequency (least frequent label assigned 0) * 'alphabetDesc': descending alphabetical order * 'alphabetAsc': ascending alphabetical order Please, update the method **transformFrequenciesToEncodingValues and add the strategy as a parameter of trainer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9100) Split Basic and Cache TC configurations on pure in-memory and with disk usage one
[ https://issues.apache.org/jira/browse/IGNITE-9100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-9100: -- Description: Discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Splitting-cache-and-basic-TC-configuration-on-pure-in-memory-and-persistent-one-td33133.html > Split Basic and Cache TC configurations on pure in-memory and with disk usage > one > - > > Key: IGNITE-9100 > URL: https://issues.apache.org/jira/browse/IGNITE-9100 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.7 > > > Discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Splitting-cache-and-basic-TC-configuration-on-pure-in-memory-and-persistent-one-td33133.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8179) ZookeeperDiscoverySpiTest#testCommunicationFailureResolve_KillRandom always fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563718#comment-16563718
]
Pavel Kovalenko commented on IGNITE-8179:
-
[~VitaliyB] I placed several comments regarding code style in Upsource review.
After resolving PR can be merged without objections.
> ZookeeperDiscoverySpiTest#testCommunicationFailureResolve_KillRandom always
> fails on TC
> ---
>
> Key: IGNITE-8179
> URL: https://issues.apache.org/jira/browse/IGNITE-8179
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails on TC with the following stack trace:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGridsMultiThreaded(GridAbstractTest.java:710)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:497)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testCommunicationFailureResolve_KillRandom(ZookeeperDiscoverySpiTest.java:2742)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:40921,127.0.0.1:35014,127.0.0.1:38754,
> joinTimeout=0, sesTimeout=2000, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 23 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> ... 25 more
> Caused by:
>
[jira] [Commented] (IGNITE-8180) ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
[
https://issues.apache.org/jira/browse/IGNITE-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563717#comment-16563717
]
Pavel Kovalenko commented on IGNITE-8180:
-
[~NSAmelchev] If timeout works and test passed 100 times, I think it can be
merged.
> ZookeeperDiscoverySpiTest#testQuorumRestore fails on TC
> ---
>
> Key: IGNITE-8180
> URL: https://issues.apache.org/jira/browse/IGNITE-8180
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Amelchev Nikita
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> Test fails on TC with the following stack trace:
> {noformat}
> class org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1698)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1007)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1977)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1720)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1148)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:646)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:882)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:845)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:833)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:799)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:683)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testQuorumRestore(ZookeeperDiscoverySpiTest.java:1077)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: ZookeeperDiscoverySpi [zkRootPath=/apacheIgnite,
> zkConnectionString=127.0.0.1:40921,127.0.0.1:35014,127.0.0.1:38754,
> joinTimeout=0, sesTimeout=15000, clientReconnectDisabled=false,
> internalLsnr=null]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:905)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1693)
> ... 20 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to
> initialize Zookeeper nodes
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:827)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoin(ZookeeperDiscoveryImpl.java:957)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.joinTopology(ZookeeperDiscoveryImpl.java:775)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.startJoinAndWait(ZookeeperDiscoveryImpl.java:693)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStart(ZookeeperDiscoverySpi.java:471)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
> ... 22 more
> Caused by:
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClientFailedException:
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /apacheIgnite
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.onZookeeperError(ZookeeperClient.java:758)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient.exists(ZookeeperClient.java:276)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.initZkNodes(ZookeeperDiscoveryImpl.java:789)
> ... 27
[jira] [Commented] (IGNITE-9034) [ML] Add Estimator API support to TensorFlow cluster on top of Apache Ignite
[ https://issues.apache.org/jira/browse/IGNITE-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563708#comment-16563708 ] ASF GitHub Bot commented on IGNITE-9034: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4402 > [ML] Add Estimator API support to TensorFlow cluster on top of Apache Ignite > > > Key: IGNITE-9034 > URL: https://issues.apache.org/jira/browse/IGNITE-9034 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.7 > > Attachments: TFI.pdf > > > TensorFlow distributed training historically has been based on workers, > parameter servers and manual assignments, but new TensorFlow API (Estimator > API) allows to run distributed training with minimal changes compare to > single device execution. Take a look [this > presentation|https://www.youtube.com/watch?v=bRMGoPqsn20] for more > information. > Estimator API requires the following configuration: > * TF_CONFIG environment variable that contains json with cluster description > (see [this > tutorial|https://cloud.google.com/ml-engine/docs/tensorflow/distributed-training-details]), > * tf.contrib.distribute.MirroredStrategy(workers) that defines distribution > strategy. > The goal of this task is to allow: > * to start and maintain TensorFlow cluster on top of Apache Ignite that > contains workers and chief job, > * submit job into such cluster using command line interface. > Current architecture is in attachment (see [^TFI.pdf]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[
https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563697#comment-16563697
]
Vitaliy Biryukov commented on IGNITE-9130:
--
[~dpavlov], Done.
> ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
>
>
> Key: IGNITE-9130
> URL: https://issues.apache.org/jira/browse/IGNITE-9130
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Fail:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> A new error that throws instead of the old one:
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
> statement:
> CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
> BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
> VARCHAR, HOSTNAMES VARCHAR) ENGINE
> "org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
> [42101-195]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.command.ddl.CreateTable.update(CreateTable.java:117)
> at org.h2.command.CommandContainer.update(CommandContainer.java:101)
> at org.h2.command.Command.executeUpdate(Command.java:260)
> at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
> at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
> at
> org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine.registerView(SqlSystemTableEngine.java:48)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2608)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9138) ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails if zk cluster was stpped before nodes.
[
https://issues.apache.org/jira/browse/IGNITE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563694#comment-16563694
]
ASF GitHub Bot commented on IGNITE-9138:
Github user BiryukovVA closed the pull request at:
https://github.com/apache/ignite/pull/4459
> ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails if zk cluster
> was stpped before nodes.
> -
>
> Key: IGNITE-9138
> URL: https://issues.apache.org/jira/browse/IGNITE-9138
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
>
> {noformat}
> junit.framework.AssertionFailedError: Expected: but was:
> ZkCommunicationErrorProcessFuture
> [impl=org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl@180b3819,
> endTime=1532545453881, id=9e083d2d461-645a2360-f5bb-43d3-8327-83d0a4a00124,
> state=WAIT_TIMEOUT, resolveTopVer=0, resErr=null, collectResFut=null]
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.checkInternalStructuresCleanup(ZookeeperDiscoverySpiTest.java:517)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.afterTest(ZookeeperDiscoverySpiTest.java:476)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9100) Split Basic and Cache TC configurations on pure in-memory and with disk usage one
[ https://issues.apache.org/jira/browse/IGNITE-9100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563684#comment-16563684 ] Dmitriy Pavlov commented on IGNITE-9100: [~EdShangGG] please fill ticket description, you may also refer to some dev.list dicsussion. > Split Basic and Cache TC configurations on pure in-memory and with disk usage > one > - > > Key: IGNITE-9100 > URL: https://issues.apache.org/jira/browse/IGNITE-9100 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[
https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Biryukov updated IGNITE-9130:
-
Description:
Fail:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNotNull(Assert.java:256)
at junit.framework.Assert.assertNotNull(Assert.java:248)
at junit.framework.TestCase.assertNotNull(TestCase.java:417)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
at java.lang.Thread.run(Thread.java:748)
{noformat}
A new error that throes instead of the old one:
{noformat}
Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
statement:
CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
VARCHAR, HOSTNAMES VARCHAR) ENGINE
"org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
[42101-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.command.ddl.CreateTable.update(CreateTable.java:117)
at org.h2.command.CommandContainer.update(CommandContainer.java:101)
at org.h2.command.Command.executeUpdate(Command.java:260)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
at
org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine.registerView(SqlSystemTableEngine.java:48)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2608)
{noformat}
> ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
>
>
> Key: IGNITE-9130
> URL: https://issues.apache.org/jira/browse/IGNITE-9130
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Fail:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> A new error that throes instead of the old one:
> {noformat}
> Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
> statement:
> CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
> BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
> VARCHAR, HOSTNAMES VARCHAR) ENGINE
> "org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
> [42101-195]
> at
[jira] [Updated] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[
https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Biryukov updated IGNITE-9130:
-
Description:
Fail:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNotNull(Assert.java:256)
at junit.framework.Assert.assertNotNull(Assert.java:248)
at junit.framework.TestCase.assertNotNull(TestCase.java:417)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
at java.lang.Thread.run(Thread.java:748)
{noformat}
A new error that throws instead of the old one:
{noformat}
Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
statement:
CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
VARCHAR, HOSTNAMES VARCHAR) ENGINE
"org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
[42101-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.command.ddl.CreateTable.update(CreateTable.java:117)
at org.h2.command.CommandContainer.update(CommandContainer.java:101)
at org.h2.command.Command.executeUpdate(Command.java:260)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
at
org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine.registerView(SqlSystemTableEngine.java:48)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2608)
{noformat}
was:
Fail:
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertNotNull(Assert.java:256)
at junit.framework.Assert.assertNotNull(Assert.java:248)
at junit.framework.TestCase.assertNotNull(TestCase.java:417)
at
org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testDuplicatedNodeId(ZookeeperDiscoverySpiTest.java:2565)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
at java.lang.Thread.run(Thread.java:748)
{noformat}
A new error that throes instead of the old one:
{noformat}
Caused by: org.h2.jdbc.JdbcSQLException: Table "NODES" already exists; SQL
statement:
CREATE TABLE NODES(ID UUID, CONSISTENT_ID VARCHAR, VERSION VARCHAR, IS_LOCAL
BOOLEAN, IS_CLIENT BOOLEAN, IS_DAEMON BOOLEAN, NODE_ORDER INTEGER, ADDRESSES
VARCHAR, HOSTNAMES VARCHAR) ENGINE
"org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine"
[42101-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.command.ddl.CreateTable.update(CreateTable.java:117)
at org.h2.command.CommandContainer.update(CommandContainer.java:101)
at org.h2.command.Command.executeUpdate(Command.java:260)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
at
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[ https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563678#comment-16563678 ] Dmitriy Pavlov commented on IGNITE-9130: [~VitaliyB] could you also please close irrelevant PRs? Having 2 open PRs brings a lot of confusion during review. It is also required by https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Note: Existing pull request should be updated instead of creation of new one. Creation of more than one pull request for one issue forbidden. > ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails > > > Key: IGNITE-9130 > URL: https://issues.apache.org/jira/browse/IGNITE-9130 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[ https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563674#comment-16563674 ] Dmitriy Pavlov commented on IGNITE-9130: [~VitaliyB] could you please fill description of ticket? You may provide references to failues, stacktraces, what caused that problem. > ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails > > > Key: IGNITE-9130 > URL: https://issues.apache.org/jira/browse/IGNITE-9130 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9124) Remove some dead code in math.exceptions and optimization packages of ML module
[ https://issues.apache.org/jira/browse/IGNITE-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563666#comment-16563666 ] Oleg Ignatenko edited comment on IGNITE-9124 at 7/31/18 1:36 PM: - (!) re-running coverage after cleaning up initially listed dead code helped to discover yet another piece of dead code that needs to be deleted: [LabeledVectorDouble|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/structures/LabeledVectorDouble.java] This class was initially created per IGNITE-5218 for use in ColumnDecisionTreeTrainerTest and BaseDecisionTreeTest that were in turn removed per IGNITE-8059 was (Author: oignatenko): re-running coverage after cleaning up initially listed dead code helped to discover yet another piece of dead code: [LabeledVectorDouble|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/structures/LabeledVectorDouble.java]. This class was initially created per IGNITE-5218 for use in ColumnDecisionTreeTrainerTest and BaseDecisionTreeTest that were in turn removed per IGNITE-8059 > Remove some dead code in math.exceptions and optimization packages of ML > module > --- > > Key: IGNITE-9124 > URL: https://issues.apache.org/jira/browse/IGNITE-9124 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Doing code coverage analysis discovered a bit of unused code: > # in package > [math.exceptions|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/math/exceptions] > - classes ConvergenceException / MathIllegalStateException, > InsufficientDataException, MathIllegalNumberException / > NumberIsTooSmallException, NonPositiveDefiniteMatrixException, > NonSymmetricMatrixException, NullArgumentException, SingularMatrixException, > UnknownProviderException. In very early releases of ML these exceptions were > used by some linear algebra code. This code has been very deeply reworked > since but outdated exceptions were left hanging unattended, making rather > confusing impression of the current API. > # in > [optimization|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/optimization] > - interface Updater and two classes implementing it: BarzilaiBorweinUpdater > and SimpleUpdater. This code has left hanging after cleanup that was made for > release 2.5 (IGNITE-8232). Per my discussion with [~dmitrievanthony] (who > most actively maintains this package) it would be better to remove this code. > This task is to remove code mentioned above. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9124) Remove some dead code in math.exceptions and optimization packages of ML module
[ https://issues.apache.org/jira/browse/IGNITE-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563666#comment-16563666 ] Oleg Ignatenko commented on IGNITE-9124: re-running coverage after cleaning up initially listed dead code helped to discover yet another piece of dead code: [LabeledVectorDouble|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/structures/LabeledVectorDouble.java]. This class was initially created per IGNITE-5218 for use in ColumnDecisionTreeTrainerTest and BaseDecisionTreeTest that were in turn removed per IGNITE-8059 > Remove some dead code in math.exceptions and optimization packages of ML > module > --- > > Key: IGNITE-9124 > URL: https://issues.apache.org/jira/browse/IGNITE-9124 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Doing code coverage analysis discovered a bit of unused code: > # in package > [math.exceptions|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/math/exceptions] > - classes ConvergenceException / MathIllegalStateException, > InsufficientDataException, MathIllegalNumberException / > NumberIsTooSmallException, NonPositiveDefiniteMatrixException, > NonSymmetricMatrixException, NullArgumentException, SingularMatrixException, > UnknownProviderException. In very early releases of ML these exceptions were > used by some linear algebra code. This code has been very deeply reworked > since but outdated exceptions were left hanging unattended, making rather > confusing impression of the current API. > # in > [optimization|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/optimization] > - interface Updater and two classes implementing it: BarzilaiBorweinUpdater > and SimpleUpdater. This code has left hanging after cleanup that was made for > release 2.5 (IGNITE-8232). Per my discussion with [~dmitrievanthony] (who > most actively maintains this package) it would be better to remove this code. > This task is to remove code mentioned above. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9100) Split Basic and Cache TC configurations on pure in-memory and with disk usage one
[ https://issues.apache.org/jira/browse/IGNITE-9100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura updated IGNITE-9100: Fix Version/s: 2.7 > Split Basic and Cache TC configurations on pure in-memory and with disk usage > one > - > > Key: IGNITE-9100 > URL: https://issues.apache.org/jira/browse/IGNITE-9100 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9124) Remove some dead code in math.exceptions and optimization packages of ML module
[ https://issues.apache.org/jira/browse/IGNITE-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563654#comment-16563654 ] Oleg Ignatenko commented on IGNITE-9124: https://github.com/gridgain/apache-ignite/tree/ignite-9124 > Remove some dead code in math.exceptions and optimization packages of ML > module > --- > > Key: IGNITE-9124 > URL: https://issues.apache.org/jira/browse/IGNITE-9124 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.6 >Reporter: Oleg Ignatenko >Assignee: Oleg Ignatenko >Priority: Major > Fix For: 2.7 > > > Doing code coverage analysis discovered a bit of unused code: > # in package > [math.exceptions|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/math/exceptions] > - classes ConvergenceException / MathIllegalStateException, > InsufficientDataException, MathIllegalNumberException / > NumberIsTooSmallException, NonPositiveDefiniteMatrixException, > NonSymmetricMatrixException, NullArgumentException, SingularMatrixException, > UnknownProviderException. In very early releases of ML these exceptions were > used by some linear algebra code. This code has been very deeply reworked > since but outdated exceptions were left hanging unattended, making rather > confusing impression of the current API. > # in > [optimization|https://github.com/apache/ignite/tree/master/modules/ml/src/main/java/org/apache/ignite/ml/optimization] > - interface Updater and two classes implementing it: BarzilaiBorweinUpdater > and SimpleUpdater. This code has left hanging after cleanup that was made for > release 2.5 (IGNITE-8232). Per my discussion with [~dmitrievanthony] (who > most actively maintains this package) it would be better to remove this code. > This task is to remove code mentioned above. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6846) Add metrics for entry processor invocations
[
https://issues.apache.org/jira/browse/IGNITE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-6846:
---
Ignite Flags: Docs Required
> Add metrics for entry processor invocations
> ---
>
> Key: IGNITE-6846
> URL: https://issues.apache.org/jira/browse/IGNITE-6846
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Labels: iep-6
> Fix For: 2.7
>
>
> {{CacheMetrics}} object has multiple metrics for various cache operations
> like {{get}}, {{put}} and {{remove}}, but nothing for
> {{invoke}}/{{EntryProcessor}}. It makes sense to add such metrics, for
> example:
> * Total number of `invoke` operations executed.
> * Number of `invoke` operations that included updates.
> * Number of read-only `invoke` operations.
> * Min/max/avg execution time.
> * ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7783) Thin Client lib: PHP
[ https://issues.apache.org/jira/browse/IGNITE-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7783: Fix Version/s: 2.7 > Thin Client lib: PHP > > > Key: IGNITE-7783 > URL: https://issues.apache.org/jira/browse/IGNITE-7783 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: ekaterina.vergizova >Priority: Major > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in PHP programming language for > Ignite Binary Client Protocol. > Functionality: > -- > Support all operations of the Ignite Binary Client Protocol 2.6: > [https://apacheignite.readme.io/v2.6/docs/binary-client-protocol] > Except the following features which are not applicable to PHP client: > - Filter object for OP_QUERY_SCAN operation (OP_QUERY_SCAN operation itself > will be supported). > - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME operations. > - Registration of a new Ignite Enum type (reading and writing items of the > existing Ignite Enum types will be supported). > Additionally support: > - SSL/TLS connection. > - "Failover re-connection algorithm": > https://issues.apache.org/jira/browse/IGNITE-7282 > Ignite Binary Client Protocol handshake versions: 1.1.0 only. > Minimal required PHP version: 7.2 > [http://php.net/supported-versions.php] > PHP code-style standards: [https://www.php-fig.org/psr/] > Synchronous API will be supported (asynchronous operations are not supported > by the standard PHP). > The API will not be thread-safe (threads are not available in the standard > PHP; pthreads extension is not available for the latest PHP version; > thread-safety is possible to support by an application). > Examples: > - > The set of examples will cover: > - cache get/create/destroy operations > - cache put/get operations > - SQL operations (create table/index, insert/select/drop) > - SQL Fields query and Scan query > - Authentication and TLS connection > - working with primitive and complex data types > Tests: > -- > PHPUnit tests [https://phpunit.de|https://phpunit.de/] for all API methods > and all basic features. Including simple tests to start examples. > Tests will be integrated into the TeamCity with the help from the community. > Docs: > -- > The provided docs will include: > - Auto-generated API spec using Doxygen: > [http://www.doxygen.org|http://www.doxygen.org/] > - Instruction how to generate the API spec. > - Instruction how to release PHP library on Packagist: > [https://packagist.org/] > - Readme for user with info how to install and use the client. > - Simple instruction how to setup/run examples. > - Simple instruction how to setup/run tests. > All docs will be provided separately from the source code and will not be > merged to the target repository. Before the release all instructions and > readme will be moved to the readme.io with the help from the community. > Release: > > Location of the client: > /modules/platforms/php > Will be released as PHP library on Packagist: [https://packagist.org/] by the > community. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7782) Thin Client lib: Python
[ https://issues.apache.org/jira/browse/IGNITE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7782: Fix Version/s: 2.7 > Thin Client lib: Python > --- > > Key: IGNITE-7782 > URL: https://issues.apache.org/jira/browse/IGNITE-7782 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Dmitry Melnichuk >Priority: Major > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in Python programming language for > Ignite Binary Client Protocol > [https://apacheignite.readme.io/v2.4/docs/binary-client-protocol] > Prototype: > [https://github.com/skozlov-gridgain/apache-ignite-python-thin-client] > Example - NodeJS client - IGNITE- > [https://github.com/nobitlost/ignite/tree/master/modules/platforms/nodejs] > --- > h5. Package name (for use with setuptools/PyPI): > pyignite > h5. Location of the lib in the repository: > .../modules/platforms/python > h5. Python version: > 3.4+ (tested on 3.4 and 3.6) > h5. Ignite version: > 2.5. > h5. Architecture: > Syncronous (safe for use with threading/multiprocessing), procedural. Ignite > operations are mapped to functions. > h5. Documentation: > Sphinx/autodoc + readme.md > h5. Test framework: > pytest, pytest-runner for setuptools pytest integration. > h5. Usage examples included: > - cache operations (creating, configuring, deleting), > - key-value operations, > - scan query, > - basic SQL queries. > h5. Goal: > Create a full-featured Ignite thin client library: > - carefully implement, test, and document all the features of the binary > protocol, that can be useful in Python programs, > - implement and document features like type IDs or serialization hints, that > are mostly useless in Python, for interoperability's sake, > - skip features, that are not applicable to Python programs, like filter > object in scan query. > h5. Proposed scope of features: > - basic and SSL-wrapped TCP connection, > - authentication and authorization, > - failover mechanism, > - all datatypes, > - all client operations (except Binary-Type operations with type names). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9134) ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME
[ https://issues.apache.org/jira/browse/IGNITE-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563618#comment-16563618 ] ASF GitHub Bot commented on IGNITE-9134: GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/4461 IGNITE-9134: ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-9134 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4461.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4461 commit c430a34c477e5c2b0f60a34335277910c5982691 Author: Vitaliy Biryukov Date: 2018-07-31T12:46:25Z IGNITE-9134: ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME. > ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with OOME > - > > Key: IGNITE-9134 > URL: https://issues.apache.org/jira/browse/IGNITE-9134 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8900) SqlFieldsQuery provides incorrect result when item size exceeds page size
[ https://issues.apache.org/jira/browse/IGNITE-8900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563586#comment-16563586 ] Dmitriy Govorukhin commented on IGNITE-8900: [~ilantukh] Looks good. Thanks for the contribution! > SqlFieldsQuery provides incorrect result when item size exceeds page size > - > > Key: IGNITE-8900 > URL: https://issues.apache.org/jira/browse/IGNITE-8900 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.4 >Reporter: Anton Kurbanov >Assignee: Ilya Lantukh >Priority: Blocker > Fix For: 2.7 > > Attachments: Main.java, Node.java > > > Start several server nodes, then start client, execute queries with value > range in where clause. Duplicate entries may be found, some entries may be > missing. > Results as an example: > expected 5 results but got back 3 results (query range 61002664327616 to > 610026643276160004), cache.getAll returned 5 entries. > expected 8 results but got back 7 results (query range 61002664327616 to > 610026643276160007), cache.getAll returned 8 entries. > Query results: [61002664327616, 610026643276160003, 610026643276160004, > 610026643276160005, 610026643276160005, 610026643276160006, > 610026643276160007] > Please find reproducer attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8973) Need to support dump for idle_verify
[
https://issues.apache.org/jira/browse/IGNITE-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563580#comment-16563580
]
Dmitriy Govorukhin commented on IGNITE-8973:
[~akalashnikov] Looks good for me. Thanks!
[~agura] Please merge.
> Need to support dump for idle_verify
> -
>
> Key: IGNITE-8973
> URL: https://issues.apache.org/jira/browse/IGNITE-8973
> Project: Ignite
> Issue Type: Improvement
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.7
>
>
> In a current implementation, idle_verify checking consistency between primary
> and backup partitions. Will be useful to have ability dump current state for
> all partition to file or standard output. This dump can help an investigation
> of some kind of problem with partition counters or sizes because it is a
> cluster partition hash snapshot by some partition state (hash include all
> keys in the partition).
> idle_verify --dump - calculate partition hash and print into standard output
> idle_verify --dump {path} - calculate partition hash and write output to file
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7556) Docs should feature specifying SQL key more prominently
[
https://issues.apache.org/jira/browse/IGNITE-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-7556:
---
Description:
Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes]
are not DML-friendly
After reading this page and [https://apacheignite-sql.readme.io/docs/insert],
one would likely still unable to write working INSERT because there won't be
primary key in it.
Their only chance is to spot _key reference in infoblock, or infer usability of
setKeyFields() with single key type. Both are unlikely, leading to questions
such as
[https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
see {{Key is missing from query}}
Such problems are hard to debug. They can be avoided if all examples of
QueryEntities in docs will contain setKeyFields, and INSERT docs page will
refer to _key field.
was:
Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes]
are not DML-friendly
After reading this page and [https://apacheignite-sql.readme.io/docs/insert],
one would likely still unable to write working INSERT because there won't be
primary key in it.
Their only chance is to spot _key reference in infoblock, or infer usability of
setKeyFields() with single key type. Both are unlikely, leading to questions
such as
[https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
see {{Key is missing from query}}
Such problems are hard to debug. They can be avoided if all examples of
QueryEntities in docs will contain setKeyFields, and INSERT docs page will
refer to _key field.
> Docs should feature specifying SQL key more prominently
> ---
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Ilya Kasnacheev
>Assignee: Artem Budnikov
>Priority: Minor
> Fix For: 2.7
>
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes]
> are not DML-friendly
> After reading this page and
> [https://apacheignite-sql.readme.io/docs/insert], one would likely still
> unable to write working INSERT because there won't be primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability
> of setKeyFields() with single key type. Both are unlikely, leading to
> questions such as
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
> see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will
> refer to _key field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8654) Move SET command documentation to Operational Commands section
[ https://issues.apache.org/jira/browse/IGNITE-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-8654: --- Description: We need to be consistent and document SQL commands under SQL Reference section. So, move and slightly rework (no need to show step by step JDBC example) the doc from here: [https://apacheignite-sql.readme.io/v2.5/docs/jdbc-driver#section-streaming] there: [https://apacheignite-sql.readme.io/v2.5/docs/set] Once moved, ensure the format complies with the rest of the commands and there is a callout saying the feature is supported for JDBC only. Refer to COPY as to an example: [https://apacheignite-sql.readme.io/v2.5/docs/copy] was: We need to be consistent and document SQL commands under SQL Reference section. So, move and slightly rework (no need to show step by step JDBC example) the doc from here: https://apacheignite-sql.readme.io/v2.5/docs/jdbc-driver#section-streaming there: https://apacheignite-sql.readme.io/v2.5/docs/set Once moved, ensure the format complies with the rest of the commands and there is a callout saying the feature is supported for JDBC only. Refer to COPY as to an example: https://apacheignite-sql.readme.io/v2.5/docs/copy > Move SET command documentation to Operational Commands section > -- > > Key: IGNITE-8654 > URL: https://issues.apache.org/jira/browse/IGNITE-8654 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > We need to be consistent and document SQL commands under SQL Reference > section. > So, move and slightly rework (no need to show step by step JDBC example) the > doc from here: > [https://apacheignite-sql.readme.io/v2.5/docs/jdbc-driver#section-streaming] > there: > [https://apacheignite-sql.readme.io/v2.5/docs/set] > Once moved, ensure the format complies with the rest of the commands and > there is a callout saying the feature is supported for JDBC only. Refer to > COPY as to an example: > [https://apacheignite-sql.readme.io/v2.5/docs/copy] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8718) Documentation about using of the C++ BinaryWriter/BinaryReader should be updated
[
https://issues.apache.org/jira/browse/IGNITE-8718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-8718:
---
Description:
The usage that should be documented:
1)In case if you get some writer from BinaryWriter then you started writing
session. Until method close will not be called for this writer you can't get
another writer.
For example, next code isn't correct:
{code:java}
BinaryMapWriter field1Writer = writer.WriteMap("field1", MapType::HASH_MAP); //here you start writing session
BinaryMapWriter field2Writer = writer.WriteMap("field2", MapType::HASH_MAP); //here you start another writing session
- error
{code}
Should be:
{code:java}
BinaryMapWriter field1Writer = writer.WriteMap("field1", MapType::HASH_MAP); //here you start writing session
//do something
field1Writer.Close() //here you end writing session
BinaryMapWriter field2Writer = writer.WriteMap("field2", MapType::HASH_MAP); //here you start another writing session
//do something
field2Writer.Close() //here you end another writing session
{code}
2) In case if you get some reader from BinaryWriter then you started reading
session. Until something will not be read from this reader you can't get
another reader.
For example, next code isn't correct:
{code:java}
BinaryMapReader field1Reader = reader.ReadMap("field1"); //start reading session
BinaryMapReader field2Reader = reader.ReadMap("field2"); //start another read session - error
{code}
Should be for example:
{code:java}
BinaryMapReader field1Reader = reader.ReadMap("field1"); //start reading session
...
field1Reader.GetNext(key, val); //reading done
...
BinaryMapReader field2Reader = reader.ReadMap("field2"); //start another read session
...
field2Reader.GetNext(key, val); //reading done
...{code}
In the case of the writer, it looks like expected. In case of the reader, it
looks a little bit confusing.
These two behaviors should be described in the documentation as well.
was:
The usage that should be documented:
1)In case if you get some writer from BinaryWriter then you started writing
session. Until method close will not be called for this writer you can't get
another writer.
For example, next code isn't correct:
{code:java}
BinaryMapWriter field1Writer = writer.WriteMap("field1", MapType::HASH_MAP); //here you start writing session
BinaryMapWriter field2Writer = writer.WriteMap("field2", MapType::HASH_MAP); //here you start another writing session
- error
{code}
Should be:
{code:java}
BinaryMapWriter field1Writer = writer.WriteMap("field1", MapType::HASH_MAP); //here you start writing session
//do something
field1Writer.Close() //here you end writing session
BinaryMapWriter field2Writer = writer.WriteMap("field2", MapType::HASH_MAP); //here you start another writing session
//do something
field2Writer.Close() //here you end another writing session
{code}
2) In case if you get some reader from BinaryWriter then you started reading
session. Until something will not be read from this reader you can't get
another reader.
For example, next code isn't correct:
{code:java}
BinaryMapReader field1Reader = reader.ReadMap("field1"); //start reading session
BinaryMapReader field2Reader = reader.ReadMap("field2"); //start another read session - error
{code}
Should be for example:
{code:java}
BinaryMapReader field1Reader = reader.ReadMap("field1"); //start reading session
...
field1Reader.GetNext(key, val); //reading done
...
BinaryMapReader field2Reader = reader.ReadMap("field2"); //start another read session
...
field2Reader.GetNext(key, val); //reading done
...{code}
In the case of the writer, it looks like expected. In case of the reader, it
looks a little bit confusing.
These two behaviors should be described in the documentation as well.
> Documentation about using of the C++ BinaryWriter/BinaryReader should be
> updated
>
>
> Key: IGNITE-8718
> URL: https://issues.apache.org/jira/browse/IGNITE-8718
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.5
>Reporter: Andrey Aleksandrov
>Assignee: Artem Budnikov
>Priority: Major
> Labels: c++
> Fix For: 2.7
>
>
> The usage that should be documented:
> 1)In case if you get some writer from BinaryWriter then you started writing
> session. Until method close will not be called for this writer you can't get
> another writer.
>
> For example, next code isn't correct:
> {code:java}
> BinaryMapWriter field1Writer = writer.WriteMap int64_t>("field1", MapType::HASH_MAP); //here you start writing session
> BinaryMapWriter field2Writer = writer.WriteMap int64_t>("field2", MapType::HASH_MAP); //here you start another writing
[jira] [Updated] (IGNITE-7730) Improve WAL history size documentation
[
https://issues.apache.org/jira/browse/IGNITE-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov updated IGNITE-7730:
---
Description:
Until IGNITE-6552 is not implemented, we have only ability to configure WAL
hist. size in checkpoints.
It is needed to improve description for this parameter.
I've added draft notes to wiki
[https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Estimatingdiskspace]
about ways how wer can estimate WAL sizes without exact bytes/time
specification:
{panel}
WAL Work max used size: walSegmentSize * walSegments = 640Mb (default)
in case Default WAL mode - this size is used always,
in case other modes best case is 1 segment * walSegmentSize
WAL Work+WAL Archive max size may be estimated by
1. average load or
2. by maximum size.
1st way is applicable if checkpoints are triggered mostly by timer trigger.
Wal size = 2*Average load(bytes/sec) * trigger interval (sec) * walHistSize
(number of checkpoints)
Where 2 multiplier coming from physical & logical WAL Records.
2nd way: Checkpoint is triggered by segments max dirty pages percent. Use
persisted data regions max sizes:
sum(Max configured DataRegionConfiguration.maxSize) * 75% - est. maximum data
volume to be writen on 1 checkpoint.
Overall WAL size (before archiving) = 2* est. data volume * walHistSize = 1,5
* sum(DataRegionConfiguration.maxSize) * walHistSize
Note applying WAL compressor may significiantly reduce archive size.
{panel}
One more note from [~ivan.glukos] on dev.list we need to include. It is answer
to question how user can determine if segment from archive folder can be safely
removed:
{quote}By the way: WAL compression is already implemented that way. If there
are any ".zip" segments in archive dir, they are free to delete.
This can be a safe workaround for users who experience lack of free
space - just delete compressed segments. We should mention it in
documentation for 2.4 release.
{quote}
was:
Until IGNITE-6552 is not implemented, we have only ability to configure WAL
hist. size in checkpoints.
It is needed to improve description for this parameter.
I've added draft notes to wiki
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Estimatingdiskspace
about ways how wer can estimate WAL sizes without exact bytes/time
specification:
{panel}
WAL Work max used size: walSegmentSize * walSegments = 640Mb (default)
in case Default WAL mode - this size is used always,
in case other modes best case is 1 segment * walSegmentSize
WAL Work+WAL Archive max size may be estimated by
1. average load or
2. by maximum size.
1st way is applicable if checkpoints are triggered mostly by timer trigger.
Wal size = 2*Average load(bytes/sec) * trigger interval (sec) * walHistSize
(number of checkpoints)
Where 2 multiplier coming from physical & logical WAL Records.
2nd way: Checkpoint is triggered by segments max dirty pages percent. Use
persisted data regions max sizes:
sum(Max configured DataRegionConfiguration.maxSize) * 75% - est. maximum data
volume to be writen on 1 checkpoint.
Overall WAL size (before archiving) = 2* est. data volume * walHistSize = 1,5 *
sum(DataRegionConfiguration.maxSize) * walHistSize
Note applying WAL compressor may significiantly reduce archive size.
{panel}
One more note from [~ivan.glukos] on dev.list we need to include. It is answer
to question how user can determine if segment from archive folder can be safely
removed:
{quote}
By the way: WAL compression is already implemented that way. If there
are any ".zip" segments in archive dir, they are free to delete.
This can be a safe workaround for users who experience lack of free
space - just delete compressed segments. We should mention it in
documentation for 2.4 release.
{quote}
> Improve WAL history size documentation
> --
>
> Key: IGNITE-7730
> URL: https://issues.apache.org/jira/browse/IGNITE-7730
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.7
>
>
> Until IGNITE-6552 is not implemented, we have only ability to configure WAL
> hist. size in checkpoints.
> It is needed to improve description for this parameter.
> I've added draft notes to wiki
> [https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-underthehood-Estimatingdiskspace]
> about ways how wer can estimate WAL sizes without exact bytes/time
> specification:
> {panel}
> WAL Work max used size: walSegmentSize * walSegments = 640Mb (default)
> in case Default WAL mode - this size
[jira] [Updated] (IGNITE-7645) Clarify eviction policy documentation
[ https://issues.apache.org/jira/browse/IGNITE-7645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-7645: --- Description: Eviction policies work differently depending on the configuration that might be one of the following: * Just off-heap memory w/o Ignite persistence * off-heap memory + on-heap cache * off-heap memory + Ignite persistence * off-heap memory + swap or cache store Cover all these scenarios on the main eviction doc page:[https://apacheignite.readme.io/docs/evictions] More details: [http://apache-ignite-developers.2346864.n4.nabble.com/Eviction-policies-with-persistence-td26588.html |http://apache-ignite-developers.2346864.n4.nabble.com/Eviction-policies-with-persistence-td26588.html] was: Eviction policies work differently depending on the configuration that might be one of the following: * Just off-heap memory w/o Ignite persistence * off-heap memory + on-heap cache * off-heap memory + Ignite persistence * off-heap memory + swap or cache store Cover all these scenarios on the main eviction doc page:https://apacheignite.readme.io/docs/evictions More details: http://apache-ignite-developers.2346864.n4.nabble.com/Eviction-policies-with-persistence-td26588.html > Clarify eviction policy documentation > - > > Key: IGNITE-7645 > URL: https://issues.apache.org/jira/browse/IGNITE-7645 > Project: Ignite > Issue Type: Task >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.7 > > > Eviction policies work differently depending on the configuration that might > be one of the following: > * Just off-heap memory w/o Ignite persistence > * off-heap memory + on-heap cache > * off-heap memory + Ignite persistence > * off-heap memory + swap or cache store > Cover all these scenarios on the main eviction doc > page:[https://apacheignite.readme.io/docs/evictions] > More details: > [http://apache-ignite-developers.2346864.n4.nabble.com/Eviction-policies-with-persistence-td26588.html > > |http://apache-ignite-developers.2346864.n4.nabble.com/Eviction-policies-with-persistence-td26588.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9114) Fail fast in org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
[ https://issues.apache.org/jira/browse/IGNITE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563561#comment-16563561 ] Vladimir Ozerov commented on IGNITE-9114: - New test run: https://ci.ignite.apache.org/viewQueued.html?itemId=1567014 > Fail fast in > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > - > > Key: IGNITE-9114 > URL: https://issues.apache.org/jira/browse/IGNITE-9114 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > has infinite loop with exit condition on success, thus failure to make > reservation on partition can "hang" query. Exception should be thrown and > method should return if cycle does not succeed in reasonable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9114) Fail fast in org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
[ https://issues.apache.org/jira/browse/IGNITE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563558#comment-16563558 ] Vladimir Ozerov commented on IGNITE-9114: - Reopened - need to take query timeout in count > Fail fast in > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > - > > Key: IGNITE-9114 > URL: https://issues.apache.org/jira/browse/IGNITE-9114 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > has infinite loop with exit condition on success, thus failure to make > reservation on partition can "hang" query. Exception should be thrown and > method should return if cycle does not succeed in reasonable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9114) Fail fast in org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
[ https://issues.apache.org/jira/browse/IGNITE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563556#comment-16563556 ] ASF GitHub Bot commented on IGNITE-9114: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4460 IGNITE-9114 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9114-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4460.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4460 commit 91b9501b9e5844e76276739514445058df7b66ee Author: devozerov Date: 2018-07-31T12:15:30Z Better timeout management. > Fail fast in > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > - > > Key: IGNITE-9114 > URL: https://issues.apache.org/jira/browse/IGNITE-9114 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > has infinite loop with exit condition on success, thus failure to make > reservation on partition can "hang" query. Exception should be thrown and > method should return if cycle does not succeed in reasonable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-9114) Fail fast in org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query
[ https://issues.apache.org/jira/browse/IGNITE-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reopened IGNITE-9114: - > Fail fast in > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > - > > Key: IGNITE-9114 > URL: https://issues.apache.org/jira/browse/IGNITE-9114 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#query > has infinite loop with exit condition on success, thus failure to make > reservation on partition can "hang" query. Exception should be thrown and > method should return if cycle does not succeed in reasonable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9137) Web console: UI of 'select node' modal a little bit broken
[ https://issues.apache.org/jira/browse/IGNITE-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-9137: Assignee: Pavel Konstantinov (was: Dmitriy Shabalin) > Web console: UI of 'select node' modal a little bit broken > -- > > Key: IGNITE-9137 > URL: https://issues.apache.org/jira/browse/IGNITE-9137 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Under Firefox > Query - Execute on Selected Node > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9143: - Component/s: wizards > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9144) A client node leaving a grid may trigger the wrong message about coordinator change in the logs
[
https://issues.apache.org/jira/browse/IGNITE-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgenii Zagumennov reassigned IGNITE-9144:
--
Assignee: Evgenii Zagumennov
> A client node leaving a grid may trigger the wrong message about coordinator
> change in the logs
> ---
>
> Key: IGNITE-9144
> URL: https://issues.apache.org/jira/browse/IGNITE-9144
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Artukhov
>Assignee: Evgenii Zagumennov
>Priority: Major
>
> The issue was introduced by https://issues.apache.org/jira/browse/IGNITE-8738.
> Suppose we have a grid with X server nodes and Y client nodes. Server nodes
> are restarted periodically while client nodes are left untouched. In this
> case *order* of current coordinator might be greater than *order* of any
> client node. Then when some client node leaves the grid, we will erroneously
> print the *Coordinator changed* message with *client* node being the previous
> coordinator. E.g.:
> {noformat}
> [2018-07-19 14:55:28,897][INFO ][disco-event-worker-#61] Node left topology:
> TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68, addrs=[127.0.0.1,
> 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0, /127.0.0.1:0,
> lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16, intOrder=11,
> lastExchangeTime=1532001260398, loc=false, ver=2.5.1#20180717-sha1:80e51c80,
> isClient=true]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Topology snapshot
> [ver=27, servers=3, clients=4, CPUs=96, offheap=260.0GB, heap=56.0GB]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Coordinator changed
> [prev=TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68,
> addrs=[127.0.0.1, 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0,
> /127.0.0.1:0, lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16,
> intOrder=11, lastExchangeTime=1532001260398, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=true], cur=TcpDiscoveryNode
> [id=760fd8f2-b9d7-4953-aa86-3954c05c9feb, addrs=[127.0.0.1, 172.17.0.1,
> 172.25.1.21], sockAddrs=[/172.17.0.1:47500,
> lab21.gridgain.local/172.25.1.21:47500, /127.0.0.1:47500], discPort=47500,
> order=21, intOrder=15, lastExchangeTime=1532001260428, loc=false,
> ver=2.5.1#20180717-sha1:80e51c80, isClient=false]]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Node
> [id=22B15E97-9944-48B5-A473-5C64E75A4D5A, clusterState=ACTIVE]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Baseline
> [id=6, size=3, online=3, offline=0]
> [2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Data Regions
> Configured:
> [2018-07-19 14:55:28,900][INFO ][disco-event-worker-#61] ^-- default
> [initSize=256.0 MiB, maxSize=60.0 GiB, persistenceEnabled=true]
> {noformat}
> The *Coordinator changed* message should not be here because in fact the
> coordinator was not changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov resolved IGNITE-9136.
--
Resolution: Fixed
Merged to master.
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[ https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563535#comment-16563535 ] Eduard Shangareev commented on IGNITE-9130: --- [~VitaliyB], looks good for me. Thanx. [~dpavlov] Please, help with merge. > ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails > > > Key: IGNITE-9130 > URL: https://issues.apache.org/jira/browse/IGNITE-9130 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9144) A client node leaving a grid may trigger the wrong message about coordinator change in the logs
Ivan Artukhov created IGNITE-9144:
-
Summary: A client node leaving a grid may trigger the wrong
message about coordinator change in the logs
Key: IGNITE-9144
URL: https://issues.apache.org/jira/browse/IGNITE-9144
Project: Ignite
Issue Type: Bug
Reporter: Ivan Artukhov
The issue was introduced by https://issues.apache.org/jira/browse/IGNITE-8738.
Suppose we have a grid with X server nodes and Y client nodes. Server nodes are
restarted periodically while client nodes are left untouched. In this case
*order* of current coordinator might be greater than *order* of any client
node. Then when some client node leaves the grid, we will erroneously print the
*Coordinator changed* message with *client* node being the previous
coordinator. E.g.:
{noformat}
[2018-07-19 14:55:28,897][INFO ][disco-event-worker-#61] Node left topology:
TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68, addrs=[127.0.0.1,
172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0, /127.0.0.1:0,
lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16, intOrder=11,
lastExchangeTime=1532001260398, loc=false, ver=2.5.1#20180717-sha1:80e51c80,
isClient=true]
[2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Topology snapshot
[ver=27, servers=3, clients=4, CPUs=96, offheap=260.0GB, heap=56.0GB]
[2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Coordinator changed
[prev=TcpDiscoveryNode [id=7240957f-a51b-452d-bfc8-420e8ef9ea68,
addrs=[127.0.0.1, 172.17.0.1, 172.25.1.15], sockAddrs=[/172.17.0.1:0,
/127.0.0.1:0, lab15.gridgain.local/172.25.1.15:0], discPort=0, order=16,
intOrder=11, lastExchangeTime=1532001260398, loc=false,
ver=2.5.1#20180717-sha1:80e51c80, isClient=true], cur=TcpDiscoveryNode
[id=760fd8f2-b9d7-4953-aa86-3954c05c9feb, addrs=[127.0.0.1, 172.17.0.1,
172.25.1.21], sockAddrs=[/172.17.0.1:47500,
lab21.gridgain.local/172.25.1.21:47500, /127.0.0.1:47500], discPort=47500,
order=21, intOrder=15, lastExchangeTime=1532001260428, loc=false,
ver=2.5.1#20180717-sha1:80e51c80, isClient=false]]
[2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Node
[id=22B15E97-9944-48B5-A473-5C64E75A4D5A, clusterState=ACTIVE]
[2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] ^-- Baseline [id=6,
size=3, online=3, offline=0]
[2018-07-19 14:55:28,899][INFO ][disco-event-worker-#61] Data Regions
Configured:
[2018-07-19 14:55:28,900][INFO ][disco-event-worker-#61] ^-- default
[initSize=256.0 MiB, maxSize=60.0 GiB, persistenceEnabled=true]
{noformat}
The *Coordinator changed* message should not be here because in fact the
coordinator was not changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9130) ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails
[ https://issues.apache.org/jira/browse/IGNITE-9130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563532#comment-16563532 ] Vitaliy Biryukov commented on IGNITE-9130: -- This PR [https://github.com/apache/ignite/pull/4458] is right. > ZookeeperDiscoverySpiTest#testDuplicatedNodeId fails > > > Key: IGNITE-9130 > URL: https://issues.apache.org/jira/browse/IGNITE-9130 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Vitaliy Biryukov >Assignee: Vitaliy Biryukov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9139) Web console: item from dropdown cannot be selected
[ https://issues.apache.org/jira/browse/IGNITE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9139: Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Merged to master. > Web console: item from dropdown cannot be selected > -- > > Key: IGNITE-9139 > URL: https://issues.apache.org/jira/browse/IGNITE-9139 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Query - Result - Chart - Chart Settings - Y axis settings -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9143: --- Attachment: screenshot-1.png > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9143: --- Description: Create a new notebook. Start writing a new query. !screenshot-1.png! was: Create a new notebook. Start writing a new query. > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query. > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
Pavel Konstantinov created IGNITE-9143: -- Summary: Web console: SQL buttons are disabled in case when it must be enabled Key: IGNITE-9143 URL: https://issues.apache.org/jira/browse/IGNITE-9143 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Assignee: Alexey Kuznetsov Create a new notebook. Start writing a new query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9139) Web console: item from dropdown cannot be selected
[ https://issues.apache.org/jira/browse/IGNITE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9139: -- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web console: item from dropdown cannot be selected > -- > > Key: IGNITE-9139 > URL: https://issues.apache.org/jira/browse/IGNITE-9139 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > Attachments: screenshot-1.png > > > Query - Result - Chart - Chart Settings - Y axis settings -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8915) NPE during executing local SqlQuery from client node
[
https://issues.apache.org/jira/browse/IGNITE-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563473#comment-16563473
]
Nikolay Izhikov commented on IGNITE-8915:
-
[~zstan]
> is it works properly well for LOCAL cache created on client side too?
It will throw the same exception.
I moved tests to {{IgniteCacheAbstractQuerySelfTest}} so now it tested for all
types of caches.
https://github.com/apache/ignite/pull/4414
> NPE during executing local SqlQuery from client node
>
>
> Key: IGNITE-8915
> URL: https://issues.apache.org/jira/browse/IGNITE-8915
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Vyacheslav Daradur
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: IgniteCacheReplicatedClientLocalQuerySelfTest.java
>
>
> NPE when trying to execute {{SqlQuery}} with {{setLocal(true)}} from client
> node.
> [Reproducer|^IgniteCacheReplicatedClientLocalQuerySelfTest.java].
> UPD:
> Right behavior:
> Local query should be forbidden and a sensible exception should be thrown if
> it is executed on client node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8611) Binary marshaller documentation should cover how data classes can or can't be changed
[ https://issues.apache.org/jira/browse/IGNITE-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov updated IGNITE-8611: --- Description: Binary marshaller docs ([https://apacheignite.readme.io/docs/binary-marshaller]) give an idea that a class structure may be changed (fields can be added or removed) and the marshaller will handle such change. However, not all changes are supported. One corner case is when an enum value is stored in the cache: if the order of the enum constants is changed, or if a new constant is added at the start or at the middle of the constants list, it will lead to an error. This is because the enums are stored as ordinals (integers), and the ordinals of an enum depend on the order of values in the code. The task is to update the documentation with the description of data class changes that are incompatible from binary marshallers point of view. At least the enum case should be covered. If more cases are discovered, they should be documented as well. was: Binary marshaller docs (https://apacheignite.readme.io/docs/binary-marshaller) give an idea that a class structure may be changed (fields can be added or removed) and the marshaller will handle such change. However, not all changes are supported. One corner case is when an enum value is stored in the cache: if the order of the enum constants is changed, or if a new constant is added at the start or at the middle of the constants list, it will lead to an error. This is because the enums are stored as ordinals (integers), and the ordinals of an enum depend on the order of values in the code. The task is to update the documentation with the description of data class changes that are incompatible from binary marshallers point of view. At least the enum case should be covered. If more cases are discovered, they should be documented as well. > Binary marshaller documentation should cover how data classes can or can't be > changed > - > > Key: IGNITE-8611 > URL: https://issues.apache.org/jira/browse/IGNITE-8611 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Minor > > Binary marshaller docs > ([https://apacheignite.readme.io/docs/binary-marshaller]) give an idea that a > class structure may be changed (fields can be added or removed) and the > marshaller will handle such change. > However, not all changes are supported. > One corner case is when an enum value is stored in the cache: if the order > of the enum constants is changed, or if a new constant is added at the start > or at the middle of the constants list, it will lead to an error. This is > because the enums are stored as ordinals (integers), and the ordinals of an > enum depend on the order of values in the code. > The task is to update the documentation with the description of data class > changes that are incompatible from binary marshallers point of view. At least > the enum case should be covered. If more cases are discovered, they should be > documented as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov reassigned IGNITE-9136:
Assignee: Pavel Konstantinov (was: Alexey Kuznetsov)
Fixed visibility of "(De)Activating..." label for old cluster.
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-9136:
--
Assignee: Alexey Kuznetsov (was: Pavel Konstantinov)
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9136) Web console: hide\disable cluster activation switcher if cluster has no persistent configuration
[
https://issues.apache.org/jira/browse/IGNITE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563451#comment-16563451
]
Pavel Konstantinov commented on IGNITE-9136:
Please hide the 'Activating...'\'Deactivating...' label as well.
> Web console: hide\disable cluster activation switcher if cluster has no
> persistent configuration
>
>
> Key: IGNITE-9136
> URL: https://issues.apache.org/jira/browse/IGNITE-9136
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.7
>
>
> I faced with exception when tried to activate a cluster of version 7.x due to
> that version of ignite has no persistent at all.
> {code}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.visor.misc.VisorChangeGridActiveStateTaskArg
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:313)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9142) CacheAsyncOperationsFailoverTxTest hangs because of exchange
[
https://issues.apache.org/jira/browse/IGNITE-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Shangareev updated IGNITE-9142:
--
Attachment: ignite.log.zip
> CacheAsyncOperationsFailoverTxTest hangs because of exchange
>
>
> Key: IGNITE-9142
> URL: https://issues.apache.org/jira/browse/IGNITE-9142
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Priority: Major
> Attachments: ignite.log.zip
>
>
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=1542329&_focus=2400075
> {code}
> "main" #1 prio=5 os_prio=0 tid=0x7f9ea000d000 nid=0x437d waiting on
> condition [0x7f9ea901b000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:816)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.loadData(DataStreamerImpl.java:700)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:666)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.removeDataInternal(DataStreamerImpl.java:619)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter$GlobalRemoveAllJob.localExecute(GridDistributedCacheAdapter.java:467)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6233)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6744)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1407)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:660)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:760)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:452)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:408)
> at
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.removeAll(GridDistributedCacheAdapter.java:188)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.removeAll(IgniteCacheProxyImpl.java:1333)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.removeAll(GatewayProtectedCacheProxy.java:1081)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractSelfTest$1.applyx(GridCacheAbstractSelfTest.java:150)
> at
> org.apache.ignite.internal.util.lang.GridAbsPredicateX.apply(GridAbsPredicateX.java:32)
> at
> org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1647)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAbstractSelfTest.afterTest(GridCacheAbstractSelfTest.java:146)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1694)
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:503)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at
