[jira] [Commented] (IGNITE-11978) Javadoc enhancement for the ReadRepair feature.
[ https://issues.apache.org/jira/browse/IGNITE-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886690#comment-16886690 ] Anton Vinogradov commented on IGNITE-11978: --- Seems, we have a consensus issue :) [~NIzhikov], could you please join PR discussion? > Javadoc enhancement for the ReadRepair feature. > --- > > Key: IGNITE-11978 > URL: https://issues.apache.org/jira/browse/IGNITE-11978 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > Time Spent: 4.5h > Remaining Estimate: 0h > > The newly added `ReadRepair` feature requires Javadoc improvements. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
[
https://issues.apache.org/jira/browse/IGNITE-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886503#comment-16886503
]
Vyacheslav Koptilin commented on IGNITE-11986:
--
In any case, I am a bit confused that the client's log does not provide enough
information about the unsuccessful attempt to join the cluster. Looks like a
usability issue.
> Failed to deserialize object with given class loader:
> sun.misc.Launcher$AppClassLoader
> ---
>
> Key: IGNITE-11986
> URL: https://issues.apache.org/jira/browse/IGNITE-11986
> Project: Ignite
> Issue Type: Bug
>Affects Versions: mas
> Environment: Ignite master: commit
> {{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
> spark 2.4.3
> hadoop 3.1.2
> OpenJDK 8
> scala 2.11.12
>
>Reporter: Jean-Denis Giguère
>Priority: Major
> Attachments: server-not-ok.log, spark.log
>
>
> h1. Current situation
> Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
> get the error message given in the error log attached.
> See code snippet here :
> https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
> h2. Expected situation
> We shall be able to connect to a remote Ignite even when we are using Hadoop
> 3.1.x.
> h3. Steps to reproduce
> See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
[
https://issues.apache.org/jira/browse/IGNITE-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886494#comment-16886494
]
Vyacheslav Koptilin commented on IGNITE-11986:
--
Well, it seems a class-path issue. The log file from the server node gives a
hint:
> InvalidClassException: javax.cache.configuration.MutableConfiguration; local
>class incompatible: stream classdesc serialVersionUID = 201405, local class
>serialVersionUID = 201306200821
This class `javax.cache.configuration.MutableConfiguration` is part of
`cache-api` jar, and it looks like that the client node uses the old version of
this library.
Apache Ignite uses version 1.0.0. Please make sure that only one version is
used in the cluster.
> Failed to deserialize object with given class loader:
> sun.misc.Launcher$AppClassLoader
> ---
>
> Key: IGNITE-11986
> URL: https://issues.apache.org/jira/browse/IGNITE-11986
> Project: Ignite
> Issue Type: Bug
>Affects Versions: mas
> Environment: Ignite master: commit
> {{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
> spark 2.4.3
> hadoop 3.1.2
> OpenJDK 8
> scala 2.11.12
>
>Reporter: Jean-Denis Giguère
>Priority: Major
> Attachments: server-not-ok.log, spark.log
>
>
> h1. Current situation
> Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
> get the error message given in the error log attached.
> See code snippet here :
> https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
> h2. Expected situation
> We shall be able to connect to a remote Ignite even when we are using Hadoop
> 3.1.x.
> h3. Steps to reproduce
> See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
[
https://issues.apache.org/jira/browse/IGNITE-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Denis Giguère updated IGNITE-11986:
Attachment: server-not-ok.log
> Failed to deserialize object with given class loader:
> sun.misc.Launcher$AppClassLoader
> ---
>
> Key: IGNITE-11986
> URL: https://issues.apache.org/jira/browse/IGNITE-11986
> Project: Ignite
> Issue Type: Bug
>Affects Versions: mas
> Environment: Ignite master: commit
> {{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
> spark 2.4.3
> hadoop 3.1.2
> OpenJDK 8
> scala 2.11.12
>
>Reporter: Jean-Denis Giguère
>Priority: Major
> Attachments: server-not-ok.log, spark.log
>
>
> h1. Current situation
> Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
> get the error message given in the error log attached.
> See code snippet here :
> https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
> h2. Expected situation
> We shall be able to connect to a remote Ignite even when we are using Hadoop
> 3.1.x.
> h3. Steps to reproduce
> See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
[
https://issues.apache.org/jira/browse/IGNITE-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886459#comment-16886459
]
Jean-Denis Giguère commented on IGNITE-11986:
-
[~slava.koptilin], here they are [^server-not-ok.log]
> Failed to deserialize object with given class loader:
> sun.misc.Launcher$AppClassLoader
> ---
>
> Key: IGNITE-11986
> URL: https://issues.apache.org/jira/browse/IGNITE-11986
> Project: Ignite
> Issue Type: Bug
>Affects Versions: mas
> Environment: Ignite master: commit
> {{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
> spark 2.4.3
> hadoop 3.1.2
> OpenJDK 8
> scala 2.11.12
>
>Reporter: Jean-Denis Giguère
>Priority: Major
> Attachments: server-not-ok.log, spark.log
>
>
> h1. Current situation
> Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
> get the error message given in the error log attached.
> See code snippet here :
> https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
> h2. Expected situation
> We shall be able to connect to a remote Ignite even when we are using Hadoop
> 3.1.x.
> h3. Steps to reproduce
> See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
[
https://issues.apache.org/jira/browse/IGNITE-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886429#comment-16886429
]
Vyacheslav Koptilin commented on IGNITE-11986:
--
Hi [~jean-denis_at_anagraph], could you please attach log files from remote
nodes?
> Failed to deserialize object with given class loader:
> sun.misc.Launcher$AppClassLoader
> ---
>
> Key: IGNITE-11986
> URL: https://issues.apache.org/jira/browse/IGNITE-11986
> Project: Ignite
> Issue Type: Bug
>Affects Versions: mas
> Environment: Ignite master: commit
> {{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
> spark 2.4.3
> hadoop 3.1.2
> OpenJDK 8
> scala 2.11.12
>
>Reporter: Jean-Denis Giguère
>Priority: Major
> Attachments: spark.log
>
>
> h1. Current situation
> Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
> get the error message given in the error log attached.
> See code snippet here :
> https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
> h2. Expected situation
> We shall be able to connect to a remote Ignite even when we are using Hadoop
> 3.1.x.
> h3. Steps to reproduce
> See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-11986) Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader
Jean-Denis Giguère created IGNITE-11986:
---
Summary: Failed to deserialize object with given class loader:
sun.misc.Launcher$AppClassLoader
Key: IGNITE-11986
URL: https://issues.apache.org/jira/browse/IGNITE-11986
Project: Ignite
Issue Type: Bug
Affects Versions: mas
Environment: Ignite master: commit
{{1a2c35caf805769ca4e3f169d7a5c72c31147e41}}
spark 2.4.3
hadoop 3.1.2
OpenJDK 8
scala 2.11.12
Reporter: Jean-Denis Giguère
Attachments: spark.log
h1. Current situation
Trying to create connect to a remote ignite cluster from {{spark-submit}}, I
get the error message given in the error log attached.
See code snippet here :
https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data
h2. Expected situation
We shall be able to connect to a remote Ignite even when we are using Hadoop
3.1.x.
h3. Steps to reproduce
See: [https://github.com/jdenisgiguere/ignite_failed_unmarshal_discovery_data]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11981) [IEP-35] Create MU shortcut instead of static import of MetricUtils
[
https://issues.apache.org/jira/browse/IGNITE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886250#comment-16886250
]
Andrey Gura commented on IGNITE-11981:
--
[~NIzhikov] As I know there are no any restrictions about static imports.
> [IEP-35] Create MU shortcut instead of static import of MetricUtils
> ---
>
> Key: IGNITE-11981
> URL: https://issues.apache.org/jira/browse/IGNITE-11981
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
>
> More Ignite-way of coding is the usage of short cut classes.
> We should use MU instead of static import of {{MetricUtils}}.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (IGNITE-9488) GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs
[ https://issues.apache.org/jira/browse/IGNITE-9488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Korenshteyn reassigned IGNITE-9488: - Assignee: Alexander Korenshteyn > GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs > --- > > Key: IGNITE-9488 > URL: https://issues.apache.org/jira/browse/IGNITE-9488 > Project: Ignite > Issue Type: Bug > Components: spring >Reporter: Mikhail Cherkasov >Assignee: Alexander Korenshteyn >Priority: Minor > Fix For: 2.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > GridSpringCacheManagerMultiJvmSelfTest#testSyncCache test hangs -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Issue Comment Deleted] (IGNITE-11983) TcpDiscoverySpi: Infinite circulation of TcpDiscoveryStatusCheckMessage after node restart
[
https://issues.apache.org/jira/browse/IGNITE-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lazurkin updated IGNITE-11983:
-
Comment: was deleted
(was: How about that?
https://github.com/apache/ignite/blob/2.7.5/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L4164
{code:java}
if (!node.id().equals(msg.creatorNodeId())) {
return;
}
{code:java}
)
> TcpDiscoverySpi: Infinite circulation of TcpDiscoveryStatusCheckMessage after
> node restart
> --
>
> Key: IGNITE-11983
> URL: https://issues.apache.org/jira/browse/IGNITE-11983
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Dmitry Lazurkin
>Priority: Major
>
> Node *ignite-2*/*ignite-3* has inifite logs about
> *TcpDiscoveryStatusCheckMessage* with id
> *832a931eb61-f507bad3-ea78-40a6-81ce-ab415ab871bb*.
> h2. Cluster topology
> *ignite-1 (f170bfc0-3dec-4b7b-8815-99ca641abc2f)*
> {code}
> 2019-07-15 12:13:16,076 [RMI TCP Connection(10)-127.0.0.1] INFO
> o.a.i.s.d.tcp.TcpDiscoverySpi - TcpDiscoveryNodesRing [
> locNode=TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1563192795758, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> nodes=[
> TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1562343474727, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1563192795758, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=b400aa0a-1d9b-4165-96ae-d75aba2d1bb8,
> addrs=[10.40.105.88], sockAddrs=[/10.40.105.88:0], discPort=0, order=7,
> intOrder=6, lastExchangeTime=1562343561117, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=618b2910-071d-4247-86f3-1d40237e7645,
> addrs=[10.44.151.8], sockAddrs=[/10.44.151.8:0], discPort=0, order=9,
> intOrder=7, lastExchangeTime=1562343652607, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=2b033aed-132d-4341-b1cf-6f45a21619b7,
> addrs=[10.37.26.56], sockAddrs=[/10.37.26.56:0], discPort=0, order=14,
> intOrder=10, lastExchangeTime=1562851741145, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=6a182cef-25dc-4ee6-8307-a62ec164f466,
> addrs=[10.48.44.3], sockAddrs=[ignite-3/10.48.44.3:47500], discPort=47500,
> order=18, intOrder=12, lastExchangeTime=1562853582125, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false]], topVer=18, nodeOrder=12,
> maxInternalOrder=12, minNodeVer=2.7.0#20181130-sha1:256ae401]
> {code}
> *ignite-2 (d47598e1-bbfd-4789-ba25-b1af6dc147bf, coordinator)*
> {code}
> 2019-07-15 12:11:29,679 [RMI TCP Connection(88)-127.0.0.1] INFO
> o.a.i.s.d.tcp.TcpDiscoverySpi - TcpDiscoveryNodesRing [
> locNode=TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1563192689675, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> nodes=[
> TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1563192689675, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1562343474657, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=b400aa0a-1d9b-4165-96ae-d75aba2d1bb8,
> addrs=[10.40.105.88], sockAddrs=[/10.40.105.88:0], discPort=0, order=7,
> intOrder=6, lastExchangeTime=1562343561102, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=618b2910-071d-4247-86f3-1d40237e7645,
> addrs=[10.44.151.8], sockAddrs=[/10.44.151.8:0], discPort=0, order=9,
> intOrder=7, lastExchangeTime=1562343652597, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=2b033aed-132d-4341-b1cf-6f45a21619b7,
> addrs=[10.37.26.56], sockAddrs=[/10.37.26.56:0], discPort=0, order=14,
> intOrder=10, lastExchangeTime=1562851741133, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode
[jira] [Commented] (IGNITE-9283) [ML] Add Discrete Cosine preprocessor
[ https://issues.apache.org/jira/browse/IGNITE-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886097#comment-16886097 ] Aleksey Zinoviev commented on IGNITE-9283: -- [~ilantukh] are you going to make this task? > [ML] Add Discrete Cosine preprocessor > - > > Key: IGNITE-9283 > URL: https://issues.apache.org/jira/browse/IGNITE-9283 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Ilya Lantukh >Priority: Major > > Add [https://en.wikipedia.org/wiki/Discrete_cosine_transform] > Please look at the MinMaxScaler or Normalization packages in preprocessing > package. > Add classes if required > 1) Preprocessor > 2) Trainer > 3) custom PartitionData if shuffling is a step of algorithm > > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-10697) [ML] Add Frequency Encoding
[ https://issues.apache.org/jira/browse/IGNITE-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886093#comment-16886093 ] Aleksey Zinoviev commented on IGNITE-10697: --- Draft solution: [https://github.com/gridgain/apache-ignite/tree/ignite-10697] > [ML] Add Frequency Encoding > --- > > Key: IGNITE-10697 > URL: https://issues.apache.org/jira/browse/IGNITE-10697 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Trivial > Fix For: 2.8 > > > Encode the values to a fraction of all the labels. Can work with linear > models if the frequency is correlated with the target value. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11983) TcpDiscoverySpi: Infinite circulation of TcpDiscoveryStatusCheckMessage after node restart
[
https://issues.apache.org/jira/browse/IGNITE-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886091#comment-16886091
]
Dmitry Lazurkin commented on IGNITE-11983:
--
How about that?
https://github.com/apache/ignite/blob/2.7.5/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/ServerImpl.java#L4164
{code:java}
if (!node.id().equals(msg.creatorNodeId())) {
return;
}
{code:java}
> TcpDiscoverySpi: Infinite circulation of TcpDiscoveryStatusCheckMessage after
> node restart
> --
>
> Key: IGNITE-11983
> URL: https://issues.apache.org/jira/browse/IGNITE-11983
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Dmitry Lazurkin
>Priority: Major
>
> Node *ignite-2*/*ignite-3* has inifite logs about
> *TcpDiscoveryStatusCheckMessage* with id
> *832a931eb61-f507bad3-ea78-40a6-81ce-ab415ab871bb*.
> h2. Cluster topology
> *ignite-1 (f170bfc0-3dec-4b7b-8815-99ca641abc2f)*
> {code}
> 2019-07-15 12:13:16,076 [RMI TCP Connection(10)-127.0.0.1] INFO
> o.a.i.s.d.tcp.TcpDiscoverySpi - TcpDiscoveryNodesRing [
> locNode=TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1563192795758, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> nodes=[
> TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1562343474727, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1563192795758, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=b400aa0a-1d9b-4165-96ae-d75aba2d1bb8,
> addrs=[10.40.105.88], sockAddrs=[/10.40.105.88:0], discPort=0, order=7,
> intOrder=6, lastExchangeTime=1562343561117, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=618b2910-071d-4247-86f3-1d40237e7645,
> addrs=[10.44.151.8], sockAddrs=[/10.44.151.8:0], discPort=0, order=9,
> intOrder=7, lastExchangeTime=1562343652607, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=2b033aed-132d-4341-b1cf-6f45a21619b7,
> addrs=[10.37.26.56], sockAddrs=[/10.37.26.56:0], discPort=0, order=14,
> intOrder=10, lastExchangeTime=1562851741145, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=6a182cef-25dc-4ee6-8307-a62ec164f466,
> addrs=[10.48.44.3], sockAddrs=[ignite-3/10.48.44.3:47500], discPort=47500,
> order=18, intOrder=12, lastExchangeTime=1562853582125, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false]], topVer=18, nodeOrder=12,
> maxInternalOrder=12, minNodeVer=2.7.0#20181130-sha1:256ae401]
> {code}
> *ignite-2 (d47598e1-bbfd-4789-ba25-b1af6dc147bf, coordinator)*
> {code}
> 2019-07-15 12:11:29,679 [RMI TCP Connection(88)-127.0.0.1] INFO
> o.a.i.s.d.tcp.TcpDiscoverySpi - TcpDiscoveryNodesRing [
> locNode=TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1563192689675, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> nodes=[
> TcpDiscoveryNode [id=d47598e1-bbfd-4789-ba25-b1af6dc147bf,
> addrs=[10.48.44.2], sockAddrs=[ignite-2/10.48.44.2:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1563192689675, loc=true,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=f170bfc0-3dec-4b7b-8815-99ca641abc2f,
> addrs=[10.48.44.1], sockAddrs=[ignite-1/10.48.44.1:47500], discPort=47500,
> order=2, intOrder=2, lastExchangeTime=1562343474657, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=false],
> TcpDiscoveryNode [id=b400aa0a-1d9b-4165-96ae-d75aba2d1bb8,
> addrs=[10.40.105.88], sockAddrs=[/10.40.105.88:0], discPort=0, order=7,
> intOrder=6, lastExchangeTime=1562343561102, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=618b2910-071d-4247-86f3-1d40237e7645,
> addrs=[10.44.151.8], sockAddrs=[/10.44.151.8:0], discPort=0, order=9,
> intOrder=7, lastExchangeTime=1562343652597, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode [id=2b033aed-132d-4341-b1cf-6f45a21619b7,
> addrs=[10.37.26.56], sockAddrs=[/10.37.26.56:0], discPort=0, order=14,
> intOrder=10, lastExchangeTime=1562851741133, loc=false,
> ver=2.7.0#20181130-sha1:256ae401, isClient=true],
> TcpDiscoveryNode
[jira] [Commented] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
[
https://issues.apache.org/jira/browse/IGNITE-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886060#comment-16886060
]
Sergey Chugunov commented on IGNITE-11784:
--
[~Denis Chudov], change looks good to me as well. We should proceed with
merging it to master. Thank you for contribution!
> Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
> --
>
> Key: IGNITE-11784
> URL: https://issues.apache.org/jira/browse/IGNITE-11784
> Project: Ignite
> Issue Type: Improvement
>Reporter: Sergey Antonov
>Assignee: Denis Chudov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}}
> have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to
> node attributes. We could sent only nodeId and get TcpDiscoveryNode from
> {{TcpDiscoveryNodesRing}} on target node.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11978) Javadoc enhancement for the ReadRepair feature.
[ https://issues.apache.org/jira/browse/IGNITE-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886035#comment-16886035 ] Vyacheslav Koptilin commented on IGNITE-11978: -- Hi [~avinogradov], I have updated the PR. Please take a look. > Javadoc enhancement for the ReadRepair feature. > --- > > Key: IGNITE-11978 > URL: https://issues.apache.org/jira/browse/IGNITE-11978 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > The newly added `ReadRepair` feature requires Javadoc improvements. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11982) Fix bugs of pds
[ https://issues.apache.org/jira/browse/IGNITE-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886031#comment-16886031 ] Anton Kalashnikov commented on IGNITE-11982: Cache 6 same as master > Fix bugs of pds > --- > > Key: IGNITE-11982 > URL: https://issues.apache.org/jira/browse/IGNITE-11982 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > fixed pds crash: > * Fail during logical recovery > * JVM crash in all compatibility LFS tests > * WAL segments serialization problem > * Unable to read last WAL record after crash during checkpoint > * Node failed on detecting storage block size if page compression enabled on > many caches > * Can not change baseline for in-memory cluster > * SqlFieldsQuery DELETE FROM causes JVM crash > * Fixed IgniteCheckedException: Compound exception for CountDownFuture. > fixed tests: > * WalCompactionAndPageCompressionTest > * IgnitePdsRestartAfterFailedToWriteMetaPageTest.test > * GridPointInTimeRecoveryRebalanceTest.testRecoveryNotFailsIfWalSomewhereEnab > * > IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers_5_Clients_Fro > * IgniteCacheReplicatedQuerySelfTest.testNodeLeft > * .NET tests > optimization: > * Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages > * Failures to deserialize discovery data should be handled by a failure > handler > * Optimize GridToStringBuilder -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11982) Fix bugs of pds
[
https://issues.apache.org/jira/browse/IGNITE-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16886030#comment-16886030
]
Ignite TC Bot commented on IGNITE-11982:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4336935]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4332991buildTypeId=IgniteTests24Java8_RunAll]
> Fix bugs of pds
> ---
>
> Key: IGNITE-11982
> URL: https://issues.apache.org/jira/browse/IGNITE-11982
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> fixed pds crash:
> * Fail during logical recovery
> * JVM crash in all compatibility LFS tests
> * WAL segments serialization problem
> * Unable to read last WAL record after crash during checkpoint
> * Node failed on detecting storage block size if page compression enabled on
> many caches
> * Can not change baseline for in-memory cluster
> * SqlFieldsQuery DELETE FROM causes JVM crash
> * Fixed IgniteCheckedException: Compound exception for CountDownFuture.
> fixed tests:
> * WalCompactionAndPageCompressionTest
> * IgnitePdsRestartAfterFailedToWriteMetaPageTest.test
> * GridPointInTimeRecoveryRebalanceTest.testRecoveryNotFailsIfWalSomewhereEnab
> *
> IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers_5_Clients_Fro
> * IgniteCacheReplicatedQuerySelfTest.testNodeLeft
> * .NET tests
> optimization:
> * Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
> * Failures to deserialize discovery data should be handled by a failure
> handler
> * Optimize GridToStringBuilder
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11979) Add ability to set default parallelizm of rebuild indexes in configuration
[
https://issues.apache.org/jira/browse/IGNITE-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885980#comment-16885980
]
Sergey Antonov commented on IGNITE-11979:
-
[~Denis Chudov] Changes looks good for me
> Add ability to set default parallelizm of rebuild indexes in configuration
> --
>
> Key: IGNITE-11979
> URL: https://issues.apache.org/jira/browse/IGNITE-11979
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can't change SchemaIndexCacheVisitorImpl#DFLT_PARALLELISM at the moment:
> {code:java}
> /** Default degree of parallelism. */
> private static final int DFLT_PARALLELISM = Math.min(4, Math.max(1,
> Runtime.getRuntime().availableProcessors() / 4));
> {code}
> On huge servers with a lot of cores (such as 56) we will rebuild indexes in 4
> threads. I think we should have ability to set DFLT_PARALLELISM in Ignite
> configuration.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11979) Add ability to set default parallelizm of rebuild indexes in configuration
[
https://issues.apache.org/jira/browse/IGNITE-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885935#comment-16885935
]
Denis Chudov commented on IGNITE-11979:
---
[~antonovsergey93], done
> Add ability to set default parallelizm of rebuild indexes in configuration
> --
>
> Key: IGNITE-11979
> URL: https://issues.apache.org/jira/browse/IGNITE-11979
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can't change SchemaIndexCacheVisitorImpl#DFLT_PARALLELISM at the moment:
> {code:java}
> /** Default degree of parallelism. */
> private static final int DFLT_PARALLELISM = Math.min(4, Math.max(1,
> Runtime.getRuntime().availableProcessors() / 4));
> {code}
> On huge servers with a lot of cores (such as 56) we will rebuild indexes in 4
> threads. I think we should have ability to set DFLT_PARALLELISM in Ignite
> configuration.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11979) Add ability to set default parallelizm of rebuild indexes in configuration
[
https://issues.apache.org/jira/browse/IGNITE-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885934#comment-16885934
]
Ignite TC Bot commented on IGNITE-11979:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4318886]]
{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4318911]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4318932buildTypeId=IgniteTests24Java8_RunAll]
> Add ability to set default parallelizm of rebuild indexes in configuration
> --
>
> Key: IGNITE-11979
> URL: https://issues.apache.org/jira/browse/IGNITE-11979
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can't change SchemaIndexCacheVisitorImpl#DFLT_PARALLELISM at the moment:
> {code:java}
> /** Default degree of parallelism. */
> private static final int DFLT_PARALLELISM = Math.min(4, Math.max(1,
> Runtime.getRuntime().availableProcessors() / 4));
> {code}
> On huge servers with a lot of cores (such as 56) we will rebuild indexes in 4
> threads. I think we should have ability to set DFLT_PARALLELISM in Ignite
> configuration.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (IGNITE-11917) Row count [select count(*) from table] not matching with the actual row count present in the table
[
https://issues.apache.org/jira/browse/IGNITE-11917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeniy Rudenko resolved IGNITE-11917.
--
Resolution: Duplicate
Assignee: (was: Evgeniy Rudenko)
Fix Version/s: 2.8
Dup of IGNITE-11438, will be fixed in Ignite 2.8
> Row count [select count(*) from table] not matching with the actual row count
> present in the table
> ---
>
> Key: IGNITE-11917
> URL: https://issues.apache.org/jira/browse/IGNITE-11917
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: shivakumar
>Priority: Major
> Fix For: 2.8
>
>
> To reproduce, create a sample table using JDBC endpoint:
> {code}
> CREATE TABLE person(Id VARCHAR, birthTime TIMESTAMP, name VARCHAR, PRIMARY
> KEY(Id)) WITH "TEMPLATE=templateEternal,CACHE_NAME=person,
> KEY_TYPE=personKey,VALUE_TYPE=person";
> {code}
> and configure cache expiry policy as below
> {code}
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
> factory-method="factoryOf">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> with above cache configuration records will start expiring at the end of 10
> minute, batch insert around 1 records to the table and after 10 minute
> records will start expiring but after some time check the records count
> [select count(*) from person] most of the time it will show some non zero
> number but if rows are selected instead of count to see the actual data with
> [select * from person] there will be zero rows.
> why count is not becoming zero even though there is no data (rows) in the
> table ?
>
> {code}
> 0: jdbc:ignite:thin://10.*.*.*:10800> select count(*) from person;
> ++
> |COUNT(*)|
> ++
> |70|
> ++
> 1 row selected (0.004 seconds)
> 0: jdbc:ignite:thin://10.*.*.*:10800> select * from person;
>
> +--+--++++-
> |ID|BIRTHTIME|NAME|
> +--+--++++-
>
> +--+--++++-
> No rows selected (0.015 seconds)
> 0: jdbc:ignite:thin://10.*.*.*:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (IGNITE-11984) .NET CompiledQuery won't work with strings
[ https://issues.apache.org/jira/browse/IGNITE-11984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-11984. - Resolution: Duplicate Assignee: Pavel Tupitsyn > .NET CompiledQuery won't work with strings > -- > > Key: IGNITE-11984 > URL: https://issues.apache.org/jira/browse/IGNITE-11984 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7.5 >Reporter: Alexandr Shapkin >Assignee: Pavel Tupitsyn >Priority: Minor > > Consider two samples: > var cache = GetClientCache(); > var persons = cache.AsCacheQueryable(); > > This works: > var qry = CompiledQuery.Compile((int id) => persons.Where(x => x.Value.Id == > id)); > > This won't: > var qry = CompiledQuery.Compile((string id) => persons.Where(x => > x.Value.Name.Equals(id))); > > Error compiling query: entire LINQ expression should be specified within > lambda passed to Compile method. > > Reason: > GetCompiledQuery method -> var paramValues becomes null > Because of that CacheQueryExpressionVisitor -> VisitConstant will not be > executed > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11985) .NET: CompiledQuery.Compile does not work with string parameters
[
https://issues.apache.org/jira/browse/IGNITE-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885916#comment-16885916
]
Pavel Tupitsyn commented on IGNITE-11985:
-
[~Pavlukhin] you are right, it does. My bad, did not found that one for some
reason. However, I've started the work on this one, so let's close IGNITE-11984
as duplicate if possible - [~ashapkin], any objections?
> .NET: CompiledQuery.Compile does not work with string parameters
>
>
> Key: IGNITE-11985
> URL: https://issues.apache.org/jira/browse/IGNITE-11985
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4, 2.5, 2.6, 2.7, 2.7.5
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> String parameters always produce an exception, example:
> {code}
> CompiledQuery.Compile((string empName) => persons.Where(x => x.Value.Name ==
> empName))
> {code}
> Result:
> {code}
> System.InvalidOperationException: Error compiling query: entire LINQ
> expression should be specified within lambda passed to Compile method. Part
> of the query can't be outside the Compile method call.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-11985) .NET: CompiledQuery.Compile does not work with string parameters
[
https://issues.apache.org/jira/browse/IGNITE-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-11985:
Affects Version/s: 2.4
2.5
2.6
2.7
2.7.5
> .NET: CompiledQuery.Compile does not work with string parameters
>
>
> Key: IGNITE-11985
> URL: https://issues.apache.org/jira/browse/IGNITE-11985
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.4, 2.5, 2.6, 2.7, 2.7.5
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
>
> String parameters always produce an exception, example:
> {code}
> CompiledQuery.Compile((string empName) => persons.Where(x => x.Value.Name ==
> empName))
> {code}
> Result:
> {code}
> System.InvalidOperationException: Error compiling query: entire LINQ
> expression should be specified within lambda passed to Compile method. Part
> of the query can't be outside the Compile method call.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11978) Javadoc enhancement for the ReadRepair feature.
[
https://issues.apache.org/jira/browse/IGNITE-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885908#comment-16885908
]
Ignite TC Bot commented on IGNITE-11978:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4332174buildTypeId=IgniteTests24Java8_RunAll]
> Javadoc enhancement for the ReadRepair feature.
> ---
>
> Key: IGNITE-11978
> URL: https://issues.apache.org/jira/browse/IGNITE-11978
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The newly added `ReadRepair` feature requires Javadoc improvements.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-11978) Javadoc enhancement for the ReadRepair feature.
[ https://issues.apache.org/jira/browse/IGNITE-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885883#comment-16885883 ] Anton Vinogradov commented on IGNITE-11978: --- [~slava.koptilin] Awesome work! See my comments at PR. > Javadoc enhancement for the ReadRepair feature. > --- > > Key: IGNITE-11978 > URL: https://issues.apache.org/jira/browse/IGNITE-11978 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > The newly added `ReadRepair` feature requires Javadoc improvements. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
