[jira] [Comment Edited] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716403#comment-16716403
]
Dmitriy Pavlov edited comment on IGNITE-7153 at 12/11/18 7:31 AM:
--
[~mcfongtw] a kindly reminder, could you please set PA if it is ready for
review?
was (Author: dpavlov):
[~mcfongtw] kindly remainder, could you please set PA if it is ready for review?
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Michael Fong
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
>
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Classes:
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends GenericChildModel {
public static final String[] HUMAN_NAME_USE = {"usual", "official", "temp",
"nickname", "anonymous", "old", "maiden"};
@QuerySqlField
private Byte use;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 0)})
@NotNull
@Name
private String family;
@QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = "fullname_idx",
order = 1)})
@Name
private String firstName;
@QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 2)})
@Name
private String patronymic;
public HumanNameModel() {
}
...
{code}
{code:java}
CacheConfiguration cfg = new CacheConfiguration<>();
cfg.setBackups(1);
cfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cfg.setName("HumanName");
cfg.setIndexedTypes(AffinityKey.class, HumanNameModel.class);
ignite.getOrCreateCache(cfg);
{code}
I think, the problem in "column_size", because if I recreate field "ParentID"
from sql (sqlline) it works fine (recreated.png)
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Attachment: recreated.png
> Ignite throws org.apache.ignite.IgniteCheckedException
> --
>
> Key: IGNITE-10635
> URL: https://issues.apache.org/jira/browse/IGNITE-10635
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
> Environment: Ignite 2.7. JDK 1.8, Linux Mint
>Reporter: Andrey
>Priority: Major
> Attachments: error.png, recreated.png
>
>
> Can't select row with uuid predicate:
> SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
> 'e3f070fa78884fbbbaaca02d5338e217';
>
> {code:java}
> Error: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
> "class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
> Deserialization failed, cause: "class
> org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
> [90027-197] (state=5,code=1)
> java.sql.SQLException: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
> "class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
> Deserialization failed, cause: "class
> org.apache.ignite.IgniteCheckedException: Invalid flag value: -29" [90027-197]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
> Classes:
> {code:java}
> public abstract class GenericChildModel Serializable> implements Serializable {
> transient protected T id;
> protected transient AffinityKey key;
> @QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name
> = "parent_version_idx", order = 0)})
> protected P parentId;
> @QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name
> = "parent_version_idx", order = 1, descending = true)})
> protected Long version;
> transient protected P colocationId;
> public T getId() {
> return id;
> }
> public void setId(T id) {
> this.id = id;
> }
> public P getParentId() {
> return parentId;
> }
> public void setParentId(P parentId) {
> this.parentId = parentId;
> }
> public Long getVersion() {
> return version;
> }
> public void setVersion(Long version) {
> this.version = version;
> }
> public P getColocationId() {
> return colocationId;
> }
> public void setColocationId(P colocationId) {
> this.colocationId = colocationId;
> }
> public AffinityKey key() {
> if (key == null)
> key = new AffinityKey<>(id, colocationId);
> return key;
> }
>
> public class HumanNameModel extends GenericChildModel {
> public static final String[] HUMAN_NAME_USE = {"usual", "official",
> "temp", "nickname", "anonymous", "old", "maiden"};
> @QuerySqlField
> private Byte use;
> @QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name
> = "fullname_idx", order = 0)})
> @NotNull
> @Name
> private String family;
> @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name =
> "fullname_idx", order = 1)})
> @Name
> private String firstName;
> @QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
> "fullname_idx", order = 2)})
> @Name
> private String patronymic;
> public HumanNameModel() {
> }
> ...
> {code}
> {code:java}
> CacheConfiguration cfg = new CacheConfiguration<>();
> cfg.setBackups(1);
> cfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> cfg.setName("HumanName");
> cfg.setIndexedTypes(AffinityKey.class, HumanNameModel.class);
> ignite.getOrCreateCache(cfg);
> {code}
>
> I think, the problem in "column_size", because if I recreate field "ParentID"
> from sql (sqlline) it works fine.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization.
[
https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716375#comment-16716375
]
Sergey Chugunov commented on IGNITE-10300:
--
[~agoncharuk],
I agree with [~voropava] here: we already have a section dedicated to analyze
exception's cause and returning proper error code, it is just a few lines below.
Instead of returning error code from another place in the method body why not
to trigger an existing code by throwing an exception?
> control.sh: incorrect error message after three tries on unsuccessful
> authorization.
>
>
> Key: IGNITE-10300
> URL: https://issues.apache.org/jira/browse/IGNITE-10300
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
> Fix For: 2.8
>
>
> 1. start grid with securirty enabled
> 2. try to issue control.sh --cache
> authentication credentials asked
> 3. enter incorrect credentials three times
> expected: Authentication error printed and logged
> actual: Latest topology update failed error printed
> {noformat}
> IGNITE_HOME=`pwd` bin/control.sh --cache list .
> Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error.
> Error: Latest topology update failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716374#comment-16716374 ] ASF GitHub Bot commented on IGNITE-8227: Github user pavlukhin closed the pull request at: https://github.com/apache/ignite/pull/5586 > Research possibility and implement JUnit test failure handler for TeamCity > -- > > Key: IGNITE-8227 > URL: https://issues.apache.org/jira/browse/IGNITE-8227 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Major > > After IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > we found a lot of TC failures involving unexpected nodes stop. > To avoid suites exit codes, tests have NoOpFailureHandler as default. > But instead of this, better handler could be > stopNode + fail currenly running test with message. > This default allows to identify such failures without log-message fail > condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Classes:
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends GenericChildModel {
public static final String[] HUMAN_NAME_USE = {"usual", "official", "temp",
"nickname", "anonymous", "old", "maiden"};
@QuerySqlField
private Byte use;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 0)})
@NotNull
@Name
private String family;
@QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = "fullname_idx",
order = 1)})
@Name
private String firstName;
@QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 2)})
@Name
private String patronymic;
public HumanNameModel() {
}
...
{code}
{code:java}
CacheConfiguration cfg = new CacheConfiguration<>();
cfg.setBackups(1);
cfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cfg.setName("HumanName");
cfg.setIndexedTypes(AffinityKey.class, HumanNameModel.class);
ignite.getOrCreateCache(cfg);
{code}
I think, the problem in "column_size", because if I recreate field "ParentID"
from sql (sqlline) it works fine.
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Classes:
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends GenericChildModel {
public static final String[] HUMAN_NAME_USE = {"usual", "official", "temp",
"nickname", "anonymous", "old", "maiden"};
@QuerySqlField
private Byte use;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 0)})
@NotNull
@Name
private String family;
@QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = "fullname_idx",
order = 1)})
@Name
private String firstName;
@QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 2)})
@Name
private String patronymic;
public HumanNameModel() {
}
...
{code}
I think, the problem in "column_size", because if i create this table from DDL,
it works fine, but when create from cache configuration it fails.
{code:java}
CacheConfiguration cfg = new CacheConfiguration<>();
cfg.setBackups(1);
cfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cfg.setName("HumanName");
cfg.setIndexedTypes(AffinityKey.class, HumanNameModel.class);
ignite.getOrCreateCache(cfg);
{code}
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
[jira] [Updated] (IGNITE-10177) cleanup Junit 3 from the project
[
https://issues.apache.org/jira/browse/IGNITE-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10177:
Description:
If needed, refer parent task for more details.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
(per discussion with [~EdShangGG] it looks more convenient to do this in a
separate ticket for smoother merges)
Side note if for some reason it turns out critically important to keep test
suites names (by default Junit 4 will use suite class names instead), approach
with custom description annotation [described
here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
can be used to address that.
was:
If needed, refer parent task for more details.
# remove Junit3-specific parts of API of GridAbstractTest and its subclasses
# remove dependencies from Junit 3 in Maven (if there are any)
# migrate tests that were missed at prior steps, if there are any
## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
which currently conflict with Junit4 execution because of using constructors
and make them properly use {{@Test}} annotation
## find out why
{{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
start running slow / timing out after adding Junit 4 annotations (reproduced
this on teamcity and locally as was discovered in IGNITE-10175)
# remove redundant references to {{JUnit4.class}} if there are any (like in
{{@RunWith(JUnit4.class)}})
# in tests suite classes, change {{extends TestSuite}} to either
{{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
# find and update all Junit3-specific code that {{extends TestCase}}
# execute junit related inspections of IDE and analyse results
Side note if for some reason it turns out critically important to keep test
suites names (by default Junit 4 will use suite class names instead), approach
with custom description annotation [described
here|https://stackoverflow.com/questions/34745080/is-it-possible-to-name-a-test-suite-in-junit-4/34745518]
can be used to address that.
> cleanup Junit 3 from the project
>
>
> Key: IGNITE-10177
> URL: https://issues.apache.org/jira/browse/IGNITE-10177
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> # remove Junit3-specific parts of API of GridAbstractTest and its subclasses
> # remove dependencies from Junit 3 in Maven (if there are any)
> # migrate tests that were missed at prior steps, if there are any
> ## untangle design of {{IgnitePdsContinuousRestartTest}} and its subclass
> which currently conflict with Junit4 execution because of using constructors
> and make them properly use {{@Test}} annotation
> ## find out why
> {{WalCompactionTest.testCompressorToleratesEmptyWalSegmentsFsync}} appears to
> start running slow / timing out after adding Junit 4 annotations (reproduced
> this on teamcity and locally as was discovered in IGNITE-10175)
> # in tests suite classes, change {{extends TestSuite}} to either
> {{@RunWith(AllTests.class)}} or {{@Suite.SuiteClasses}}
> # find and update all Junit3-specific code that {{extends TestCase}}
> # execute junit related inspections of IDE and analyse results
> # remove redundant references to {{JUnit4.class}} if there are any (like in
> {{@RunWith(JUnit4.class)}})
> (per discussion with [~EdShangGG] it looks more convenient to do this in a
> separate ticket for smoother merges)
> Side note if for some reason it turns out critically important to keep test
> suites names (by default Junit 4 will use suite class names instead),
> approach with custom description annotation [described
>
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends GenericChildModel {
public static final String[] HUMAN_NAME_USE = {"usual", "official", "temp",
"nickname", "anonymous", "old", "maiden"};
@QuerySqlField
private Byte use;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 0)})
@NotNull
@Name
private String family;
@QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = "fullname_idx",
order = 1)})
@Name
private String firstName;
@QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 2)})
@Name
private String patronymic;
public HumanNameModel() {
}
...
{code}
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
{code:java}
// заполнитель кода
{code}
public abstract class GenericChildModel implements Serializable \{ transient protected T id; protected
transient AffinityKey key; @QuerySqlField(notNull = true, orderedGroups =
{@QuerySqlField.Group(name = "parent_version_idx", order = 0)}) protected P
parentId; @QuerySqlField(notNull = true, orderedGroups =
\{@QuerySqlField.Group(name = "parent_version_idx", order = 1, descending =
true)}) protected Long version; transient protected P colocationId; public T
getId() \{ return id; } public void setId(T id) \{ this.id = id; } public P
getParentId() \{ return parentId; } public void setParentId(P parentId) \{
this.parentId = parentId; } public Long getVersion() \{ return version; }
public void setVersion(Long version) \{ this.version = version; } public P
getColocationId() \{ return colocationId; } public void setColocationId(P
colocationId) \{ this.colocationId = colocationId; } public AffinityKey
key() \{ if (key == null) key = new AffinityKey<>(id, colocationId); return
key; } public abstract IBase toFhirType(); public abstract boolean
deepEquals(Object other); /** * Сравнивает списки моделей вызывая deepEquals
без учета порядка элементов и учета служебных полей
(version,parentId,colocationId,id) * * @param list1 список моделей * @param
list2 список моделей * @param тип модели * @param тип ключа модели *
@param тип родительского ключа модели * @return true если равны */ public
static , T extends Serializable, P extends
Serializable> boolean deepEqualsModelList(List list1, List list2) \{ if
(list1 == list2) { return true; } if (list1 == null || list2 == null ||
list1.size() != list2.size()) \{ return false; } for (C l1 : list1) \{ if
(list2.stream().noneMatch(l1::deepEquals)) { return false; } } return true; }
> Ignite throws org.apache.ignite.IgniteCheckedException
> --
>
> Key: IGNITE-10635
> URL: https://issues.apache.org/jira/browse/IGNITE-10635
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
> Environment: Ignite 2.7. JDK 1.8, Linux Mint
>Reporter: Andrey
>Priority: Major
> Attachments: error.png
>
>
> Can't select row with uuid predicate:
> SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
> 'e3f070fa78884fbbbaaca02d5338e217';
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
{code:java}
Error: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197] (state=5,code=1)
java.sql.SQLException: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Ошибка десериализации, причина:
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
Deserialization failed, cause: "class org.apache.ignite.IgniteCheckedException:
Invalid flag value: -29" [90027-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Classes:
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends GenericChildModel {
public static final String[] HUMAN_NAME_USE = {"usual", "official", "temp",
"nickname", "anonymous", "old", "maiden"};
@QuerySqlField
private Byte use;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 0)})
@NotNull
@Name
private String family;
@QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = "fullname_idx",
order = 1)})
@Name
private String firstName;
@QuerySqlField(index = true, orderedGroups = {@QuerySqlField.Group(name =
"fullname_idx", order = 2)})
@Name
private String patronymic;
public HumanNameModel() {
}
...
{code}
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
{code:java}
public abstract class GenericChildModel implements Serializable {
transient protected T id;
protected transient AffinityKey key;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 0)})
protected P parentId;
@QuerySqlField(notNull = true, orderedGroups = {@QuerySqlField.Group(name =
"parent_version_idx", order = 1, descending = true)})
protected Long version;
transient protected P colocationId;
public T getId() {
return id;
}
public void setId(T id) {
this.id = id;
}
public P getParentId() {
return parentId;
}
public void setParentId(P parentId) {
this.parentId = parentId;
}
public Long getVersion() {
return version;
}
public void setVersion(Long version) {
this.version = version;
}
public P getColocationId() {
return colocationId;
}
public void setColocationId(P colocationId) {
this.colocationId = colocationId;
}
public AffinityKey key() {
if (key == null)
key = new AffinityKey<>(id, colocationId);
return key;
}
public class HumanNameModel extends
[jira] [Commented] (IGNITE-10428) [ML] Add example for OneVsRest trainer/model usage
[ https://issues.apache.org/jira/browse/IGNITE-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716342#comment-16716342 ] ASF GitHub Bot commented on IGNITE-10428: - GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/5631 IGNITE-10428: [ML] Add example for OneVsRest trainer/model usage You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10428 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5631.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 #5631 commit 237c9d356aab7c7dfb5944f90cd7d761002e12dd Author: Zinoviev Alexey Date: 2018-11-29T13:02:36Z IGNITE-10428: Add example for OneVsRest trainer/model usage commit 907d3c99ee85e2e450e767023354b338fbccf6ec Author: Zinoviev Alexey Date: 2018-12-11T06:33:11Z Merge branch 'master' into ignite-10428 commit 30cfd4ea7df893d5c8e81c8c2aeca59c3a06e354 Author: Zinoviev Alexey Date: 2018-12-11T06:35:14Z IGNITE-10428: Fixed example > [ML] Add example for OneVsRest trainer/model usage > -- > > Key: IGNITE-10428 > URL: https://issues.apache.org/jira/browse/IGNITE-10428 > Project: Ignite > Issue Type: Task > Components: ml >Affects Versions: 2.8 >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Critical > Fix For: 2.8 > > > This example should use LogReg or SVM or DT to train multiclass model to > distinguish classes on prepared dataset (generate or use wide-known dataset) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10635) Ignite throws org.apache.ignite.IgniteCheckedException
[
https://issues.apache.org/jira/browse/IGNITE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey updated IGNITE-10635:
Description:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
{code:java}
// заполнитель кода
{code}
public abstract class GenericChildModel implements Serializable \{ transient protected T id; protected
transient AffinityKey key; @QuerySqlField(notNull = true, orderedGroups =
{@QuerySqlField.Group(name = "parent_version_idx", order = 0)}) protected P
parentId; @QuerySqlField(notNull = true, orderedGroups =
\{@QuerySqlField.Group(name = "parent_version_idx", order = 1, descending =
true)}) protected Long version; transient protected P colocationId; public T
getId() \{ return id; } public void setId(T id) \{ this.id = id; } public P
getParentId() \{ return parentId; } public void setParentId(P parentId) \{
this.parentId = parentId; } public Long getVersion() \{ return version; }
public void setVersion(Long version) \{ this.version = version; } public P
getColocationId() \{ return colocationId; } public void setColocationId(P
colocationId) \{ this.colocationId = colocationId; } public AffinityKey
key() \{ if (key == null) key = new AffinityKey<>(id, colocationId); return
key; } public abstract IBase toFhirType(); public abstract boolean
deepEquals(Object other); /** * Сравнивает списки моделей вызывая deepEquals
без учета порядка элементов и учета служебных полей
(version,parentId,colocationId,id) * * @param list1 список моделей * @param
list2 список моделей * @param тип модели * @param тип ключа модели *
@param тип родительского ключа модели * @return true если равны */ public
static , T extends Serializable, P extends
Serializable> boolean deepEqualsModelList(List list1, List list2) \{ if
(list1 == list2) { return true; } if (list1 == null || list2 == null ||
list1.size() != list2.size()) \{ return false; } for (C l1 : list1) \{ if
(list2.stream().noneMatch(l1::deepEquals)) { return false; } } return true; }
was:
Can't select row with uuid predicate:
SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
'e3f070fa78884fbbbaaca02d5338e217';
"class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
> Ignite throws org.apache.ignite.IgniteCheckedException
> --
>
> Key: IGNITE-10635
> URL: https://issues.apache.org/jira/browse/IGNITE-10635
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
> Environment: Ignite 2.7. JDK 1.8, Linux Mint
>Reporter: Andrey
>Priority: Major
> Attachments: error.png
>
>
> Can't select row with uuid predicate:
> SELECT PARENTID FROM "HumanName".HUMANNAMEMODEL WHERE PARENTID =
> 'e3f070fa78884fbbbaaca02d5338e217';
>
> "class org.apache.ignite.IgniteCheckedException: Invalid flag value: -29"
> {code:java}
> // заполнитель кода
> {code}
> public abstract class GenericChildModel Serializable> implements Serializable \{ transient protected T id; protected
> transient AffinityKey key; @QuerySqlField(notNull = true, orderedGroups =
> {@QuerySqlField.Group(name = "parent_version_idx", order = 0)}) protected P
> parentId; @QuerySqlField(notNull = true, orderedGroups =
> \{@QuerySqlField.Group(name = "parent_version_idx", order = 1, descending =
> true)}) protected Long version; transient protected P colocationId; public T
> getId() \{ return id; } public void setId(T id) \{ this.id = id; } public P
> getParentId() \{ return parentId; } public void setParentId(P parentId) \{
> this.parentId = parentId; } public Long getVersion() \{ return version; }
> public void setVersion(Long version) \{ this.version = version; } public P
> getColocationId() \{ return colocationId; } public void setColocationId(P
> colocationId) \{ this.colocationId = colocationId; } public AffinityKey
> key() \{ if (key == null) key = new AffinityKey<>(id, colocationId); return
> key; } public abstract IBase toFhirType(); public abstract boolean
> deepEquals(Object other); /** * Сравнивает списки моделей вызывая deepEquals
> без учета порядка элементов и учета служебных полей
> (version,parentId,colocationId,id) * * @param list1 список моделей * @param
> list2 список моделей * @param тип модели * @param тип ключа модели *
> @param тип родительского ключа модели * @return true если равны */ public
> static , T extends Serializable, P extends
> Serializable> boolean deepEqualsModelList(List list1, List list2) \{ if
> (list1 == list2) { return true; } if (list1 == null || list2 == null ||
> list1.size() != list2.size()) \{ return false; } for (C l1 : list1) \{ if
> (list2.stream().noneMatch(l1::deepEquals)) {
[jira] [Created] (IGNITE-10634) .NET: EntityFramework Core Second Level Cache
Pavel Tupitsyn created IGNITE-10634: --- Summary: .NET: EntityFramework Core Second Level Cache Key: IGNITE-10634 URL: https://issues.apache.org/jira/browse/IGNITE-10634 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Similar to "classic" Entity Framework, implement 2nd level cache for EF Core. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
[
https://issues.apache.org/jira/browse/IGNITE-9858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716216#comment-16716216
]
Ignite TC Bot commented on IGNITE-9858:
---
{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=2512312buildTypeId=IgniteTests24Java8_RunAll]
> [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
>
>
> Key: IGNITE-9858
> URL: https://issues.apache.org/jira/browse/IGNITE-9858
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).
> Example of such failures on master branch:
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-2762467041583095183=TEST_STATUS_DESC=50_IgniteTests24Java8=%3Cdefault%3E]
> When we using ip finder in shared mode each node should register self address
> (except clients, obviously).
> Check that the node is a client uses installed (via DI
> @IgniteInstanceResource) Ignite instance (see
> {{TcpDiscoveryIpFinderAdapter#initializeLocalAddresses}}).
> So when client and server starts simultaneously, the following scenario is
> possible - Ignite server injected at first, then the Ignite client injected
> when the SPI is initialized ({{spiStart}}) both nodes assume that the local
> node is a client and don't register local address.
> {noformat}
> [2018-10-11 18:03:49,794][WARN
> ][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi] IP finder
> returned empty addresses list. Please check IP finder configuration. Will
> retry every 2000 ms. Change 'reconnectDelay' to configure the frequency of
> retries.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10175) migrate core module tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715727#comment-16715727
]
Oleg Ignatenko edited comment on IGNITE-10175 at 12/11/18 4:47 AM:
---
(i) sort of intermediate progress report: as of now only remaining suite that
makes bot unhappy is cache 1. I checked its status at Teamcity
[here|https://ci.ignite.apache.org/viewLog.html?buildId=2515629=buildResultsDiv=IgniteTests24Java8_Cache1]
and it appears like hanging after all tests have passed. To check how it runs
locally I executed reported test class
{{CacheEntryProcessorExternalizableFailedTest}} on my machine and it run
smoothly and quickly without failures and without hanging. I created
IGNITE-10633 to address this issue.
was (Author: oignatenko):
(i) sort of intermediate progress report: as of now only remaining suite that
makes bot unhappy is cache 1. I checked its status at Teamcity
[here|https://ci.ignite.apache.org/viewLog.html?buildId=2515629=buildResultsDiv=IgniteTests24Java8_Cache1]
and it appears like hanging after all tests have passed. To check how it runs
locally I executed reported test class
{{CacheEntryProcessorExternalizableFailedTest}} on my machine and it run
smoothly and quickly without failures and without hanging.
> migrate core module tests from Junit 3 to 4
> ---
>
> Key: IGNITE-10175
> URL: https://issues.apache.org/jira/browse/IGNITE-10175
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> If needed, refer parent task for more details.
> Migrate using new API introduced at prior step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10633) CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed under JUnit 4
[
https://issues.apache.org/jira/browse/IGNITE-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10633:
Labels: MakeTeamcityGreenAgain (was: )
> CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed
> under JUnit 4
> -
>
> Key: IGNITE-10633
> URL: https://issues.apache.org/jira/browse/IGNITE-10633
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> {{CacheEntryProcessorExternalizableFailedTest}} fails on Teamcity when
> executed under JUnit 4 (I couldn't reproduce that locally.
> Link to example failures at TC:
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=2516404=buildResultsDiv=IgniteTests24Java8_Cache1]
> Example snippet from error log: {noformat}
> org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided
> name doesn't exist. Did you call Ignition.start(..) to start an Ignite
> instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
> --- Stdout: ---
> [2018-12-11 00:46:36,826][INFO
> ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
> >>> Starting test:
> CacheEntryProcessorExternalizableFailedTest#testOptimistic <<<
> [2018-12-11 00:46:36,826][INFO
> ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
> >>> Stopping test:
> CacheEntryProcessorExternalizableFailedTest#testOptimistic in 0 ms <<<
> --- Stderr: ---
> [2018-12-11 00:46:36,827][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteIllegalStateException: Ignite instance with
> provided name doesn't exist. Did you call Ignition.start(..) to start an
> Ignite instance?
> [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
> at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1392)
> at org.apache.ignite.Ignition.ignite(Ignition.java:529)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1285)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1301)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> -
> Possible reason for failure is that some code is missing in {{beforeTest}}
> because it is placed in {{beforeTestsStarted}} instead. I think so because
> per prior experience of migrating tests from Junit 3 to 4 we discovered that
> handling of these methods noticeably differs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10633) CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed under JUnit 4
[
https://issues.apache.org/jira/browse/IGNITE-10633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10633:
Ignite Flags: (was: Docs Required)
> CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed
> under JUnit 4
> -
>
> Key: IGNITE-10633
> URL: https://issues.apache.org/jira/browse/IGNITE-10633
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> {{CacheEntryProcessorExternalizableFailedTest}} fails on Teamcity when
> executed under JUnit 4 (I couldn't reproduce that locally.
> Link to example failures at TC:
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=2516404=buildResultsDiv=IgniteTests24Java8_Cache1]
> Example snippet from error log: {noformat}
> org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided
> name doesn't exist. Did you call Ignition.start(..) to start an Ignite
> instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
> --- Stdout: ---
> [2018-12-11 00:46:36,826][INFO
> ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
> >>> Starting test:
> CacheEntryProcessorExternalizableFailedTest#testOptimistic <<<
> [2018-12-11 00:46:36,826][INFO
> ][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
> >>> Stopping test:
> CacheEntryProcessorExternalizableFailedTest#testOptimistic in 0 ms <<<
> --- Stderr: ---
> [2018-12-11 00:46:36,827][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteIllegalStateException: Ignite instance with
> provided name doesn't exist. Did you call Ignition.start(..) to start an
> Ignite instance?
> [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
> at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1392)
> at org.apache.ignite.Ignition.ignite(Ignition.java:529)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1285)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1301)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
> 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
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> -
> Possible reason for failure is that some code is missing in {{beforeTest}}
> because it is placed in {{beforeTestsStarted}} instead. I think so because
> per prior experience of migrating tests from Junit 3 to 4 we discovered that
> handling of these methods noticeably differs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10633) CacheEntryProcessorExternalizableFailedTest fails on Teamcity when executed under JUnit 4
Oleg Ignatenko created IGNITE-10633:
---
Summary: CacheEntryProcessorExternalizableFailedTest fails on
Teamcity when executed under JUnit 4
Key: IGNITE-10633
URL: https://issues.apache.org/jira/browse/IGNITE-10633
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8
Reporter: Oleg Ignatenko
{{CacheEntryProcessorExternalizableFailedTest}} fails on Teamcity when executed
under JUnit 4 (I couldn't reproduce that locally.
Link to example failures at TC:
[here|https://ci.ignite.apache.org/viewLog.html?buildId=2516404=buildResultsDiv=IgniteTests24Java8_Cache1]
Example snippet from error log: {noformat}
org.apache.ignite.IgniteIllegalStateException: Ignite instance with provided
name doesn't exist. Did you call Ignition.start(..) to start an Ignite
instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
--- Stdout: ---
[2018-12-11 00:46:36,826][INFO
][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
>>> Starting test: CacheEntryProcessorExternalizableFailedTest#testOptimistic
<<<
[2018-12-11 00:46:36,826][INFO
][test-runner-#4280%continuous.CacheEntryProcessorExternalizableFailedTest%][root]
>>> Stopping test: CacheEntryProcessorExternalizableFailedTest#testOptimistic
in 0 ms <<<
--- Stderr: ---
[2018-12-11 00:46:36,827][ERROR][main][root] Test failed.
class org.apache.ignite.IgniteIllegalStateException: Ignite instance with
provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite
instance? [name=continuous.CacheEntryProcessorExternalizableFailedTest3]
at org.apache.ignite.internal.IgnitionEx.grid(IgnitionEx.java:1392)
at org.apache.ignite.Ignition.ignite(Ignition.java:529)
at
org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1285)
at
org.apache.ignite.testframework.junits.GridAbstractTest.grid(GridAbstractTest.java:1301)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.doTestInvokeTest(CacheEntryProcessorExternalizableFailedTest.java:625)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheEntryProcessorExternalizableFailedTest.testOptimistic(CacheEntryProcessorExternalizableFailedTest.java:155)
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
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
at java.lang.Thread.run(Thread.java:748)
{noformat}
-
Possible reason for failure is that some code is missing in {{beforeTest}}
because it is placed in {{beforeTestsStarted}} instead. I think so because per
prior experience of migrating tests from Junit 3 to 4 we discovered that
handling of these methods noticeably differs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Attachment: new design example.png > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-10239: - Assignee: Andrey Novikov (was: Ilya Borisov) [~anovikov] please review. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716114#comment-16716114 ] ASF GitHub Bot commented on IGNITE-10239: - GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/5630 IGNITE-10239 Update navigation and top menu https://issues.apache.org/jira/browse/IGNITE-10239 @nva please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10239 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5630.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 #5630 commit 9d578e25759351a231b1c6f62ebb54293031f793 Author: Ilya Borisov Date: 2018-11-26T10:11:02Z IGNITE-10239 Update top menu, navigation and footer. commit 6980be0dae42cd1760f7a384cad1ea466a5f3c9e Author: Ilya Borisov Date: 2018-12-05T09:47:12Z IGNITE-10239 Use old-style footer on certain pages. commit 1e38cc13cc1a2f608268885e6168058fba064476 Author: Ilya Borisov Date: 2018-12-06T04:48:01Z IGNITE-10239 Add configuration icon. commit 8b3b8ba356b0da66d178108e9b57721a8c26a2b0 Author: Ilya Borisov Date: 2018-12-06T07:09:13Z IGNITE-10239 Fix page side paddings. commit 1cc228075bc814bdc445720dfc75bcd055bf085f Author: Ilya Borisov Date: 2018-12-06T07:10:59Z IGNITE-10239 Fix navigation icon height. commit aa5874251d5d3fc8fd42feeea1c22deac33e4ae8 Author: Ilya Borisov Date: 2018-12-06T07:28:47Z IGNITE-10239 More padding fixes. commit 365f6adc9e085688cc1380fd27a267aa67cc5601 Author: Ilya Borisov Date: 2018-12-06T07:29:28Z IGNITE-10239 Restore footer styles on certain pages. commit 7a0e8a57db84535d82949af012072a0c8c016060 Author: Ilya Borisov Date: 2018-12-06T09:42:31Z WIP UNDO LATER commit 986d22e1ce3863d449f5a47e71b1bf48194ad087 Author: Ilya Borisov Date: 2018-12-07T03:34:55Z IGNITE-10239 Use solid background in footer. commit b45580fafedc3f18ff3e7c4307c8f090b5721f96 Author: Ilya Borisov Date: 2018-12-07T03:38:26Z IGNITE-10239 Fix password-reset-change page styles. commit ced945e6cd62fa7fadf8c556d0444877a6f50f96 Author: Ilya Borisov Date: 2018-12-07T06:18:11Z IGNITE-10239 Use class to style page bottom footer. commit 844d3f93ec4182cae891fd6ba53d7077fa3c154e Author: Ilya Borisov Date: 2018-12-07T08:32:12Z IGNITE-10239 Refactor public pages. commit cf8ce9f3e738c46538075cfd2b20973a92e995b8 Author: Ilya Borisov Date: 2018-12-10T05:53:26Z IGNITE-10239 Handle navigation items overflow. commit a7fdd67589df0f595915814eecd580a24b8bb506 Author: Ilya Borisov Date: 2018-12-10T06:38:40Z IGNITE-10239 Make nav menu items accessible by keyboard. commit df4fba7cd1219f27b74208d05f19669e1aad0a68 Author: Ilya Borisov Date: 2018-12-10T07:12:22Z IGNITE-10239 Make overflow work with page zoom. commit 33faf8acc5afa197e93d4b48b8bf9fc7309a9dac Author: Ilya Borisov Date: 2018-12-10T07:37:40Z IGNITE-10239 Add bottom padding to all pages. commit 564da7506b0f6cb10f90789fc251c0a97d2671f4 Author: Ilya Borisov Date: 2018-12-10T08:37:31Z IGNITE-10239 Safari fixes. commit 085438a8f4f6fa0f13fde86e4ff546ac8767d2ba Author: Ilya Borisov Date: 2018-12-10T09:30:21Z IGNITE-10239 Tweak some layout styles. commit a14e26eaccde699831d4f67adfa1379a67e18f56 Author: Ilya Borisov Date: 2018-12-10T09:54:45Z IGNITE-10239 Fix footer position on 404 screen. commit 6295d4ae907079fa2db998598dc666a8168fc0c5 Author: Ilya Borisov Date: 2018-12-10T10:01:16Z IGNITE-10239 Cleanup. commit 4a2aed5bf600c7f690cf647c952f51aadbc39c60 Author: Ilya Borisov Date: 2018-12-10T10:29:05Z IGNITE-10239 Fix e2e tests. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Andrey Novikov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded >
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Ignite Flags: (was: Docs Required) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16716109#comment-16716109 ] Ilya Borisov commented on IGNITE-10239: --- Extra items to test: 1. All public pages markup should remain intact. 2. All navigation links should still work, that includes links outside of navigation sidebar. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png, new design example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Attachment: navigation links block scroll example.png > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png, navigation links block scroll > example.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password". Navigation links block in sidebar should scroll and indicate that some content is hidden when viewport height is low enough. (was: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password".) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". > Navigation links block in sidebar should scroll and indicate that some > content is hidden when viewport height is low enough. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. The footer should be moved to expanded sidebar, except for public screens like "sign in" or "reset password". (was: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads.) > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. The footer should be moved to expanded > sidebar, except for public screens like "sign in" or "reset password". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10239) Web Console: Create a new top menu
[ https://issues.apache.org/jira/browse/IGNITE-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-10239: -- Description: New navigation menu design moves navigation to left sidebar in order to save some vertical space. The sidebar with navigation links has two modes - collapsed, with icon-only link, and expanded, with full-text links. By default, it's kept collapsed, but user can click on toggle sidebar button left of logo to expand or collapse it again. For now, the sidebar state does not persist between page reloads. > Web Console: Create a new top menu > -- > > Key: IGNITE-10239 > URL: https://issues.apache.org/jira/browse/IGNITE-10239 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Attachments: Top-ignite-menu.png > > Time Spent: 9h 5m > Remaining Estimate: 0h > > New navigation menu design moves navigation to left sidebar in order to save > some vertical space. The sidebar with navigation links has two modes - > collapsed, with icon-only link, and expanded, with full-text links. By > default, it's kept collapsed, but user can click on toggle sidebar button > left of logo to expand or collapse it again. For now, the sidebar state does > not persist between page reloads. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
[
https://issues.apache.org/jira/browse/IGNITE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715885#comment-16715885
]
Oleg Ignatenko commented on IGNITE-10629:
-
(i) draft inspections profile attached: [^junit_inspections.xml]
> Migration follow up: check for old style tests that could be slipped through
> in transition period
> -
>
> Key: IGNITE-10629
> URL: https://issues.apache.org/jira/browse/IGNITE-10629
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: junit_inspections.xml
>
>
> We need to account for risk that while tests are migrating some commits may
> by mistake slip in old style test cases - that will be ignored by JUnit 4.
> In order to address possible issues of that kind, do the following a week or
> two after IGNITE-10177 is merged to master: run the IntelliJ inspection
> called "old style Junit test method in JUnit 4 class", review report and fix
> discovered problems if there are any.
> For the reference, my version of IDE explains this inspection as follows:
> {quote}Reports JUnit 3 style test methods which are located inside a class
> which does not extend the abstract JUnit 3 class TestCase and contains JUnit
> 4/JUnit 5 @Test annotated methods.{quote}
> (note concerns mentioned in this ticket were originally raised at dev list:
> [here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
[
https://issues.apache.org/jira/browse/IGNITE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10629:
Attachment: junit_inspections.xml
> Migration follow up: check for old style tests that could be slipped through
> in transition period
> -
>
> Key: IGNITE-10629
> URL: https://issues.apache.org/jira/browse/IGNITE-10629
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Attachments: junit_inspections.xml
>
>
> We need to account for risk that while tests are migrating some commits may
> by mistake slip in old style test cases - that will be ignored by JUnit 4.
> In order to address possible issues of that kind, do the following a week or
> two after IGNITE-10177 is merged to master: run the IntelliJ inspection
> called "old style Junit test method in JUnit 4 class", review report and fix
> discovered problems if there are any.
> For the reference, my version of IDE explains this inspection as follows:
> {quote}Reports JUnit 3 style test methods which are located inside a class
> which does not extend the abstract JUnit 3 class TestCase and contains JUnit
> 4/JUnit 5 @Test annotated methods.{quote}
> (note concerns mentioned in this ticket were originally raised at dev list:
> [here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10175) migrate core module tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715727#comment-16715727
]
Oleg Ignatenko commented on IGNITE-10175:
-
(i) sort of intermediate progress report: as of now only remaining suite that
makes bot unhappy is cache 1. I checked its status at Teamcity
[here|https://ci.ignite.apache.org/viewLog.html?buildId=2515629=buildResultsDiv=IgniteTests24Java8_Cache1]
and it appears like hanging after all tests have passed. To check how it runs
locally I executed reported test class
{{CacheEntryProcessorExternalizableFailedTest}} on my machine and it run
smoothly and quickly without failures and without hanging.
> migrate core module tests from Junit 3 to 4
> ---
>
> Key: IGNITE-10175
> URL: https://issues.apache.org/jira/browse/IGNITE-10175
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> If needed, refer parent task for more details.
> Migrate using new API introduced at prior step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10175) migrate core module tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715723#comment-16715723
]
Ignite TC Bot commented on IGNITE-10175:
{panel:title=-- Run :: All (Nightly): Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 1{color} [[tests
16|https://ci.ignite.apache.org/viewLog.html?buildId=2514698]]
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimistic - 0,0% fails in
last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticOnePhaseCommit - 0,0%
fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticOnePhaseCommitFullSync
- 0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimistic - 0,0% fails in last
100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticFullSync - 0,0%
fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticOnePhaseCommit -
0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticOnePhaseCommitFullSync
- 0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticFullSync - 0,0% fails
in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticOnePhaseCommitWithNearCache
- 0,0% fails in last 4 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticOnePhaseCommitFullSyncWithNearCache
- 0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticFullSyncWithNearCache
- 0,0% fails in last 4 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticOnePhaseCommitWithNearCache
- 0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testPessimisticWithNearCache - 0,0%
fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticOnePhaseCommitFullSyncWithNearCache
- 0,0% fails in last 100 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticWithNearCache - 0,0%
fails in last 4 master runs.
* IgniteBinaryCacheTestSuite:
CacheEntryProcessorExternalizableFailedTest.testOptimisticFullSyncWithNearCache
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity *-- Run :: All (Nightly)*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2514582buildTypeId=IgniteTests24Java8_RunAllNightly]
> migrate core module tests from Junit 3 to 4
> ---
>
> Key: IGNITE-10175
> URL: https://issues.apache.org/jira/browse/IGNITE-10175
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> If needed, refer parent task for more details.
> Migrate using new API introduced at prior step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10631) examples/sql/world.sql doesn't work for IgniteJdbcDriver
[
https://issues.apache.org/jira/browse/IGNITE-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-10631:
---
Description:
{noformat}
['/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/art-gg-pro/bin/sqlline.sh',
'-d', 'org.apache.ignite.IgniteJdbcDriver', '--verbose=true', '--force=true',
'--showWarnings=true', '--showNestedErrs=true', '-u',
'jdbc:ignite:cfg://cache=default:transactionsAllowed=true@/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/client.xml',
'-f',
'/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/sqlline_output.1.batch.txt']
...
9/5330 CREATE TABLE City (
ID INT,
Name VARCHAR,
CountryCode CHAR(3),
District VARCHAR,
Population INT,
PRIMARY KEY (ID, CountryCode)
) WITH "template=partitioned, backups=1, affinityKey=CountryCode,
CACHE_NAME=City, KEY_TYPE=demo.model.CityKey, VALUE_TYPE=demo.model.City";
No rows affected (0.118 seconds)
10/5330
11/5330 CREATE INDEX idx_country_code ON city (CountryCode);
Error: Table doesn't exist: CITY (state=42000,code=3001)
java.sql.SQLException: Table doesn't exist: CITY
at
org.apache.ignite.internal.processors.query.IgniteSQLException.toJdbcException(IgniteSQLException.java:143)
at
org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:179)
at
org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:158)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeSingle(JdbcStatement.java:181)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.execute0(JdbcStatement.java:195)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.execute(JdbcStatement.java:303)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.runCommands(SqlLine.java:1706)
at sqlline.Commands.run(Commands.java:1317)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.initArgs(SqlLine.java:595)
at sqlline.SqlLine.begin(SqlLine.java:643)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
> examples/sql/world.sql doesn't work for IgniteJdbcDriver
>
>
> Key: IGNITE-10631
> URL: https://issues.apache.org/jira/browse/IGNITE-10631
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
>
> {noformat}
> ['/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/art-gg-pro/bin/sqlline.sh',
> '-d', 'org.apache.ignite.IgniteJdbcDriver', '--verbose=true',
> '--force=true', '--showWarnings=true', '--showNestedErrs=true', '-u',
> 'jdbc:ignite:cfg://cache=default:transactionsAllowed=true@/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/client.xml',
> '-f',
> '/var/lib/teamcity/data/work/dd4d79acf76cc870/i2test/var/suite-examples/test_modules/test_sql_world/jdbc-memory-region.3/sqlline_output.1.batch.txt']
> ...
> 9/5330 CREATE TABLE City (
> ID INT,
> Name VARCHAR,
> CountryCode CHAR(3),
> District VARCHAR,
> Population INT,
> PRIMARY KEY (ID, CountryCode)
> ) WITH "template=partitioned, backups=1, affinityKey=CountryCode,
> CACHE_NAME=City, KEY_TYPE=demo.model.CityKey, VALUE_TYPE=demo.model.City";
> No rows affected (0.118 seconds)
> 10/5330
> 11/5330 CREATE INDEX idx_country_code ON city (CountryCode);
> Error: Table doesn't exist: CITY (state=42000,code=3001)
> java.sql.SQLException: Table doesn't exist: CITY
> at
> org.apache.ignite.internal.processors.query.IgniteSQLException.toJdbcException(IgniteSQLException.java:143)
> at
> org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:179)
> at
> org.apache.ignite.internal.jdbc2.JdbcUtils.convertToSqlException(JdbcUtils.java:158)
> at
> org.apache.ignite.internal.jdbc2.JdbcStatement.executeSingle(JdbcStatement.java:181)
> at
> org.apache.ignite.internal.jdbc2.JdbcStatement.execute0(JdbcStatement.java:195)
> at
>
[jira] [Created] (IGNITE-10631) examples/sql/world.sql doesn't work for IgniteJdbcDriver
Sergey Kozlov created IGNITE-10631: -- Summary: examples/sql/world.sql doesn't work for IgniteJdbcDriver Key: IGNITE-10631 URL: https://issues.apache.org/jira/browse/IGNITE-10631 Project: Ignite Issue Type: Bug Components: examples Affects Versions: 2.7 Reporter: Sergey Kozlov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests
[ https://issues.apache.org/jira/browse/IGNITE-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715576#comment-16715576 ] ASF GitHub Bot commented on IGNITE-10620: - dspavlov opened a new pull request #98: IGNITE-10620: Tracked branches & Issue detector unit tests URL: https://github.com/apache/ignite-teamcity-bot/pull/98 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests > -- > > Key: IGNITE-10620 > URL: https://issues.apache.org/jira/browse/IGNITE-10620 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > Implement actual tests for tracked branches processing and issue detectors. > Skeletons: > org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector > org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor > The actual challenge is refactoring of configuration to use not singletons, > but some injected interfaces with mock-able alternatives, refactor scheduler, > and any other refactorings needed to cover issue detection by test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10630) Missed descriptions for ML packages
Sergey Kozlov created IGNITE-10630:
--
Summary: Missed descriptions for ML packages
Key: IGNITE-10630
URL: https://issues.apache.org/jira/browse/IGNITE-10630
Project: Ignite
Issue Type: Bug
Components: build
Affects Versions: 2.7
Reporter: Sergey Kozlov
There're two modules in JavaDoc with missed descriptions:
{noformat}
org.apache.ignite.ml.math.exceptions.preprocessing
org.apache.ignite.ml.selection.scoring.evaluator
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
[
https://issues.apache.org/jira/browse/IGNITE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko reassigned IGNITE-10629:
---
Assignee: Oleg Ignatenko
> Migration follow up: check for old style tests that could be slipped through
> in transition period
> -
>
> Key: IGNITE-10629
> URL: https://issues.apache.org/jira/browse/IGNITE-10629
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> We need to account for risk that while tests are migrating some commits may
> by mistake slip in old style test cases - that will be ignored by JUnit 4.
> In order to address possible issues of that kind, do the following a week or
> two after IGNITE-10177 is merged to master: run the IntelliJ inspection
> called "old style Junit test method in JUnit 4 class", review report and fix
> discovered problems if there are any.
> For the reference, my version of IDE explains this inspection as follows:
> {quote}Reports JUnit 3 style test methods which are located inside a class
> which does not extend the abstract JUnit 3 class TestCase and contains JUnit
> 4/JUnit 5 @Test annotated methods.{quote}
> (note concerns mentioned in this ticket were originally raised at dev list:
> [here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8797) Error during writeCheckpointEntry is not passed to failure handler during checkpoint finish
[
https://issues.apache.org/jira/browse/IGNITE-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715400#comment-16715400
]
ASF GitHub Bot commented on IGNITE-8797:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4229
> Error during writeCheckpointEntry is not passed to failure handler during
> checkpoint finish
> ---
>
> Key: IGNITE-8797
> URL: https://issues.apache.org/jira/browse/IGNITE-8797
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> I observed the following failure in Cache 3 suite:
> {code}
> [13:10:55]W: [org.apache.ignite:ignite-core] [2018-06-14
> 10:10:55,509][ERROR][db-checkpoint-thread-#138910%paged.PageEvictionMultinodeMixedRegionsTest2%][GridCacheDatabaseSharedManager]
> Failed to create checkpoint.
> [13:10:55]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.internal.processors.cache.persistence.file.PersistentStorageIOException:
> Failed to write checkpoint entry [ptr=FileWALPointer [idx=0, fileOff=219747,
> len=1947], cpTs=1528971054548, cpId=d8b42759-ca5e-4613-b091-ed0356b3915d,
> type=END]
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.writeCheckpointEntry(GridCacheDatabaseSharedManager.java:2757)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.access$8100(GridCacheDatabaseSharedManager.java:178)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointEnd(GridCacheDatabaseSharedManager.java:3716)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:3277)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:3053)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> java.lang.Thread.run(Thread.java:748)
> [13:10:55]W: [org.apache.ignite:ignite-core] Caused by:
> java.nio.file.NoSuchFileException:
> /data/teamcity/work/c182b70f2dfa6507/work/db/node03-c5dcc243-fc3c-4b2f-8002-81e88d8cff7d/cp/1528971054548-d8b42759-ca5e-4613-b091-ed0356b3915d-END.bin.tmp
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> java.nio.file.Files.move(Files.java:1395)
> [13:10:55]W: [org.apache.ignite:ignite-core]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.writeCheckpointEntry(GridCacheDatabaseSharedManager.java:2752)
> [13:10:55]W: [org.apache.ignite:ignite-core]... 6 more
> [13:10:55]W: [org.apache.ignite:ignite-core] [2018-06-14
> 10:10:55,509][ERROR][db-checkpoint-thread-#138914%paged.PageEvictionMultinodeMixedRegionsTest3%][GridCacheDatabaseSharedManager]
> Failed to create checkpoint.
> {code}
> I see two issues here:
> 1) Some concurrent process is removing the work folder which results in the
> exception above
> 2) The checkpoint exception is not passed to the failure handler. This is due
> to a catch {{// TODO-ignite-db how to handle exception?}} in
> {{Checkpointer}}, which yields an uncompleted checkpoint future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7951) Add metrics for remains to evict keys/partitions
[ https://issues.apache.org/jira/browse/IGNITE-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715399#comment-16715399 ] ASF GitHub Bot commented on IGNITE-7951: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/4055 > Add metrics for remains to evict keys/partitions > > > Key: IGNITE-7951 > URL: https://issues.apache.org/jira/browse/IGNITE-7951 > Project: Ignite > Issue Type: New Feature > Components: general >Affects Versions: 2.4 >Reporter: Alexander Belyak >Assignee: Aleksey Plekhanov >Priority: Major > Labels: jmx > Fix For: 2.7 > > > Need to add some metrics for remains to evict keys/partitions to indicate > total amount of evicting work. In some cases we have synchronous eviction and > it's critically important to know how many keys need to be evicted before > exchange process end and cluster became working again. In some other cases we > just wanna know what happens in cluster now (background eviction without > workload) and when cluster will became 100% healthy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8515) Value of CacheGroupMetricsMXBean.getTotalAllocatedPages() is always 0
[
https://issues.apache.org/jira/browse/IGNITE-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715398#comment-16715398
]
ASF GitHub Bot commented on IGNITE-8515:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4007
> Value of CacheGroupMetricsMXBean.getTotalAllocatedPages() is always 0
> -
>
> Key: IGNITE-8515
> URL: https://issues.apache.org/jira/browse/IGNITE-8515
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.7
>
>
> {{DataRegionMetricsImpl#getOrAllocateGroupPageAllocationTracker}} don't save
> created trackers and always returns new tracker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8191) Print out information when cluster is not activated
[ https://issues.apache.org/jira/browse/IGNITE-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715391#comment-16715391 ] ASF GitHub Bot commented on IGNITE-8191: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3906 > Print out information when cluster is not activated > --- > > Key: IGNITE-8191 > URL: https://issues.apache.org/jira/browse/IGNITE-8191 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.5 > > > We should add additional information to local node statistics when a cluster > is not activated and add a hint on how activation is performed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8443) Flaky failure of IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
[
https://issues.apache.org/jira/browse/IGNITE-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715394#comment-16715394
]
ASF GitHub Bot commented on IGNITE-8443:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3963
> Flaky failure of
> IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
> ---
>
> Key: IGNITE-8443
> URL: https://issues.apache.org/jira/browse/IGNITE-8443
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails on TC sometimes (failure rate: 30%) with the following error:
> {noformat}
> junit.framework.AssertionFailedError: Failed to wait for update.
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.multinode(IgniteCacheClientNodeChangingTopologyTest.java:1855)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode(IgniteCacheClientNodeChangingTopologyTest.java:1673)
> {noformat}
> Each time some seconds prior to failure there is error in log:
> {noformat}
> [ERROR][sys-stripe-10-#90529%distributed.IgniteCacheClientNodeChangingTopologyTest0%][GridDhtColocatedCache]
> Failed to unmarshal at least one of the keys for lock request
> message: GridNearLockRequest [topVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], miniId=1, dhtVers=[...],
> subjId=5ad87047-5d80-4530-bb48-f7c26846, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, filter=null, super=GridDistributedLockRequest
> [nodeId=5ad87047-5d80-4530-bb48-f7c26846, nearXidVer=GridCacheVersion
> [topVer=136730132, order=1525250131532, nodeOrder=7], threadId=100107,
> futId=3e2912f2361-94bff164-8062-4fb4-8d85-c2e89e579148, timeout=0,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[...], txSize=0, flags=0, keysCnt=94,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=136730132,
> order=1525250131532, nodeOrder=7], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=1544803905
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=54, msg=Adding entry to partition that is concurrently evicted
> [grp=default, part=54, shouldBeMoving=, belongs=true,
> topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=10, minorTopVer=1]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:923)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:955)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryExx(GridDhtCacheAdapter.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.lockAllAsync(GridDhtTransactionalCacheAdapter.java:987)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest0(GridDhtTransactionalCacheAdapter.java:667)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$800(GridDhtTransactionalCacheAdapter.java:94)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12$1.run(GridDhtTransactionalCacheAdapter.java:704)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence
[ https://issues.apache.org/jira/browse/IGNITE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715396#comment-16715396 ] ASF GitHub Bot commented on IGNITE-5977: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3980 > [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence > --- > > Key: IGNITE-5977 > URL: https://issues.apache.org/jira/browse/IGNITE-5977 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Aleksey Plekhanov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Fails locally. > Example of failing > http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence
[ https://issues.apache.org/jira/browse/IGNITE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715397#comment-16715397 ] ASF GitHub Bot commented on IGNITE-5977: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3981 > [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence > --- > > Key: IGNITE-5977 > URL: https://issues.apache.org/jira/browse/IGNITE-5977 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Aleksey Plekhanov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Fails locally. > Example of failing > http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8400) Flaky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup (Grid is in invalid state)
[
https://issues.apache.org/jira/browse/IGNITE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715393#comment-16715393
]
ASF GitHub Bot commented on IGNITE-8400:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3930
> Flaky failure of
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
> (Grid is in invalid state)
> -
>
> Key: IGNITE-8400
> URL: https://issues.apache.org/jira/browse/IGNITE-8400
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails sometimes on TeamCity with exception:
> {noformat}
> java.lang.IllegalStateException: Grid is in invalid state to perform this
> operation. It either not started yet or has already being or have stopped
> [igniteInstanceName=cache.IgniteTopologyValidatorGridSplitCacheTest6,
> state=STOPPED]
> {noformat}
> Before this exception node is dropped out of topology by coordinator:
> {noformat}
> [tcp-disco-msg-worker-#7831%cache.IgniteTopologyValidatorGridSplitCacheTest6%][IgniteCacheTopologySplitAbstractTest$SplitTcpDiscoverySpi]
> Node is out of topology (probably, due to short-time network problems).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8443) Flaky failure of IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
[
https://issues.apache.org/jira/browse/IGNITE-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715395#comment-16715395
]
ASF GitHub Bot commented on IGNITE-8443:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3964
> Flaky failure of
> IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode
> ---
>
> Key: IGNITE-8443
> URL: https://issues.apache.org/jira/browse/IGNITE-8443
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails on TC sometimes (failure rate: 30%) with the following error:
> {noformat}
> junit.framework.AssertionFailedError: Failed to wait for update.
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.multinode(IgniteCacheClientNodeChangingTopologyTest.java:1855)
> at
> org.apache.ignite.internal.processors.cache.distributed.IgniteCacheClientNodeChangingTopologyTest.testPessimisticTxPutAllMultinode(IgniteCacheClientNodeChangingTopologyTest.java:1673)
> {noformat}
> Each time some seconds prior to failure there is error in log:
> {noformat}
> [ERROR][sys-stripe-10-#90529%distributed.IgniteCacheClientNodeChangingTopologyTest0%][GridDhtColocatedCache]
> Failed to unmarshal at least one of the keys for lock request
> message: GridNearLockRequest [topVer=AffinityTopologyVersion [topVer=10,
> minorTopVer=0], miniId=1, dhtVers=[...],
> subjId=5ad87047-5d80-4530-bb48-f7c26846, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, filter=null, super=GridDistributedLockRequest
> [nodeId=5ad87047-5d80-4530-bb48-f7c26846, nearXidVer=GridCacheVersion
> [topVer=136730132, order=1525250131532, nodeOrder=7], threadId=100107,
> futId=3e2912f2361-94bff164-8062-4fb4-8d85-c2e89e579148, timeout=0,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[...], txSize=0, flags=0, keysCnt=94,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=136730132,
> order=1525250131532, nodeOrder=7], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=1544803905
> class
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
> [part=54, msg=Adding entry to partition that is concurrently evicted
> [grp=default, part=54, shouldBeMoving=, belongs=true,
> topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
> curTopVer=AffinityTopologyVersion [topVer=10, minorTopVer=1]]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:923)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:798)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:955)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:525)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryExx(GridDhtCacheAdapter.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.lockAllAsync(GridDhtTransactionalCacheAdapter.java:987)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearLockRequest0(GridDhtTransactionalCacheAdapter.java:667)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$800(GridDhtTransactionalCacheAdapter.java:94)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12$1.run(GridDhtTransactionalCacheAdapter.java:704)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8400) Flaky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup (Grid is in invalid state)
[
https://issues.apache.org/jira/browse/IGNITE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715392#comment-16715392
]
ASF GitHub Bot commented on IGNITE-8400:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3922
> Flaky failure of
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
> (Grid is in invalid state)
> -
>
> Key: IGNITE-8400
> URL: https://issues.apache.org/jira/browse/IGNITE-8400
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails sometimes on TeamCity with exception:
> {noformat}
> java.lang.IllegalStateException: Grid is in invalid state to perform this
> operation. It either not started yet or has already being or have stopped
> [igniteInstanceName=cache.IgniteTopologyValidatorGridSplitCacheTest6,
> state=STOPPED]
> {noformat}
> Before this exception node is dropped out of topology by coordinator:
> {noformat}
> [tcp-disco-msg-worker-#7831%cache.IgniteTopologyValidatorGridSplitCacheTest6%][IgniteCacheTopologySplitAbstractTest$SplitTcpDiscoverySpi]
> Node is out of topology (probably, due to short-time network problems).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7527) SQL system view for current node transactions
[ https://issues.apache.org/jira/browse/IGNITE-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715384#comment-16715384 ] ASF GitHub Bot commented on IGNITE-7527: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3433 > SQL system view for current node transactions > - > > Key: IGNITE-7527 > URL: https://issues.apache.org/jira/browse/IGNITE-7527 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-13 > Fix For: 2.8 > > > Implement SQL system view to show active transactions on local node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8191) Print out information when cluster is not activated
[ https://issues.apache.org/jira/browse/IGNITE-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715387#comment-16715387 ] ASF GitHub Bot commented on IGNITE-8191: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3855 > Print out information when cluster is not activated > --- > > Key: IGNITE-8191 > URL: https://issues.apache.org/jira/browse/IGNITE-8191 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.5 > > > We should add additional information to local node statistics when a cluster > is not activated and add a hint on how activation is performed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7969) Flaky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
[
https://issues.apache.org/jira/browse/IGNITE-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715385#comment-16715385
]
ASF GitHub Bot commented on IGNITE-7969:
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3664
> Flaky failure of
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
> --
>
> Key: IGNITE-7969
> URL: https://issues.apache.org/jira/browse/IGNITE-7969
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Test fails on TeamCity with exception:
> {noformat}
> java.lang.AssertionError: Successful tryPut after failure [gridIdx=2,
> sucessful puts = 50]
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:491)
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator0(IgniteTopologyValidatorGridSplitCacheTest.java:281)
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup(IgniteTopologyValidatorGridSplitCacheTest.java:234)
> ...
> Caused by: class org.apache.ignite.IgniteException: Failed to put entry
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:498)
> ... 11 more
> Suppressed: class org.apache.ignite.IgniteException: Failed to put
> entry [node=cache.IgniteTopologyValidatorGridSplitCacheTest0]
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:463)
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:488)
> ... 11 more
> Suppressed: junit.framework.AssertionFailedError: expected:<1>
> but was:<2>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:448)
> ... 12 more
> ...
> {noformat}
> Sometimes reproduces locally.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8190) Print out an information message when local node is not in baseline
[ https://issues.apache.org/jira/browse/IGNITE-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715389#comment-16715389 ] ASF GitHub Bot commented on IGNITE-8190: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3875 > Print out an information message when local node is not in baseline > --- > > Key: IGNITE-8190 > URL: https://issues.apache.org/jira/browse/IGNITE-8190 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.5 > > > When a node is joined into the cluster and the node is not in the baseline > topology, we should print out an information message that informs how this > affects local node and what a user should do in order to add the node to > baseline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8192) Print out information on how many nodes left until auto-activation
[ https://issues.apache.org/jira/browse/IGNITE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715388#comment-16715388 ] ASF GitHub Bot commented on IGNITE-8192: Github user alex-plekhanov closed the pull request at: https://github.com/apache/ignite/pull/3866 > Print out information on how many nodes left until auto-activation > -- > > Key: IGNITE-8192 > URL: https://issues.apache.org/jira/browse/IGNITE-8192 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.5 > > > We should print out a message (probably on each topology change event) about > baseline topology and how many nodes left to be started until > auto-activation. Also, when the number of nodes is not too large, print out > their consistent IDs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
[
https://issues.apache.org/jira/browse/IGNITE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10629:
Labels: MakeTeamcityGreenAgain (was: )
> Migration follow up: check for old style tests that could be slipped through
> in transition period
> -
>
> Key: IGNITE-10629
> URL: https://issues.apache.org/jira/browse/IGNITE-10629
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> We need to account for risk that while tests are migrating some commits may
> by mistake slip in old style test cases - that will be ignored by JUnit 4.
> In order to address possible issues of that kind, do the following a week or
> two after IGNITE-10177 is merged to master: run the IntelliJ inspection
> called "old style Junit test method in JUnit 4 class", review report and fix
> discovered problems if there are any.
> For the reference, my version of IDE explains this inspection as follows:
> {quote}Reports JUnit 3 style test methods which are located inside a class
> which does not extend the abstract JUnit 3 class TestCase and contains JUnit
> 4/JUnit 5 @Test annotated methods.{quote}
> (note concerns mentioned in this ticket were originally raised at dev list:
> [here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
Oleg Ignatenko created IGNITE-10629:
---
Summary: Migration follow up: check for old style tests that could
be slipped through in transition period
Key: IGNITE-10629
URL: https://issues.apache.org/jira/browse/IGNITE-10629
Project: Ignite
Issue Type: Sub-task
Affects Versions: 2.8
Reporter: Oleg Ignatenko
We need to account for risk that while tests are migrating some commits may by
mistake slip in old style test cases - that will be ignored by JUnit 4.
In order to address possible issues of that kind, do the following a week or
two after IGNITE-10177 is merged to master: run the IntelliJ inspection called
"old style Junit test method in JUnit 4 class", review report and fix
discovered problems if there are any.
For the reference, my version of IDE explains this inspection as follows:
{quote}Reports JUnit 3 style test methods which are located inside a class
which does not extend the abstract JUnit 3 class TestCase and contains JUnit
4/JUnit 5 @Test annotated methods.{quote}
(note concerns mentioned in this ticket were originally raised at dev list:
[here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10629) Migration follow up: check for old style tests that could be slipped through in transition period
[
https://issues.apache.org/jira/browse/IGNITE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10629:
Ignite Flags: (was: Docs Required)
> Migration follow up: check for old style tests that could be slipped through
> in transition period
> -
>
> Key: IGNITE-10629
> URL: https://issues.apache.org/jira/browse/IGNITE-10629
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> We need to account for risk that while tests are migrating some commits may
> by mistake slip in old style test cases - that will be ignored by JUnit 4.
> In order to address possible issues of that kind, do the following a week or
> two after IGNITE-10177 is merged to master: run the IntelliJ inspection
> called "old style Junit test method in JUnit 4 class", review report and fix
> discovered problems if there are any.
> For the reference, my version of IDE explains this inspection as follows:
> {quote}Reports JUnit 3 style test methods which are located inside a class
> which does not extend the abstract JUnit 3 class TestCase and contains JUnit
> 4/JUnit 5 @Test annotated methods.{quote}
> (note concerns mentioned in this ticket were originally raised at dev list:
> [here|http://apache-ignite-developers.2346864.n4.nabble.com/Is-it-time-to-move-forward-to-JUnit4-5-tp29608p39300.html])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10628) Add support for nightly RunAll
[ https://issues.apache.org/jira/browse/IGNITE-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715349#comment-16715349 ] ASF GitHub Bot commented on IGNITE-10628: - zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly RunAll URL: https://github.com/apache/ignite-teamcity-bot/pull/97 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add support for nightly RunAll > -- > > Key: IGNITE-10628 > URL: https://issues.apache.org/jira/browse/IGNITE-10628 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > Add support for nightly RunAll, fix divisions on the y-axis of duration chart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10628) Add support for nightly RunAll
Nikolai Kulagin created IGNITE-10628: Summary: Add support for nightly RunAll Key: IGNITE-10628 URL: https://issues.apache.org/jira/browse/IGNITE-10628 Project: Ignite Issue Type: Sub-task Reporter: Nikolai Kulagin Assignee: Nikolai Kulagin Add support for nightly RunAll, fix divisions on the y-axis of duration chart -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10627) Support custom preferences like date format and other similar features
Evgenii Zhuravlev created IGNITE-10627: -- Summary: Support custom preferences like date format and other similar features Key: IGNITE-10627 URL: https://issues.apache.org/jira/browse/IGNITE-10627 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10079) FileWriteAheadLogManager may return invalid lastCompactedSegment
[
https://issues.apache.org/jira/browse/IGNITE-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715314#comment-16715314
]
ASF GitHub Bot commented on IGNITE-10079:
-
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/5219
> FileWriteAheadLogManager may return invalid lastCompactedSegment
>
>
> Key: IGNITE-10079
> URL: https://issues.apache.org/jira/browse/IGNITE-10079
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: WalCompactionAfterRestartTest.java
>
>
> As of current {{master}} branch,
> {{FileWriteAheadLogManager#lastCompactedSegment}} may report -1 even after
> some segments have been actually compressed. Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10386) Add mode when WAL won't be disabled during rebalancing caused by BLT change
[ https://issues.apache.org/jira/browse/IGNITE-10386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715313#comment-16715313 ] ASF GitHub Bot commented on IGNITE-10386: - Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/5541 > Add mode when WAL won't be disabled during rebalancing caused by BLT change > --- > > Key: IGNITE-10386 > URL: https://issues.apache.org/jira/browse/IGNITE-10386 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Rakov >Assignee: Andrey Kuznetsov >Priority: Major > Fix For: 2.8 > > > Enabling IgniteSystemProperties#IGNITE_DISABLE_WAL_DURING_REBALANCING > disables WAL for cache group during rebalancing in case local node has no > OWNING partitions for this group. > We should add mode when in specific case (after BaselineTopology change) WAL > won't be disabled even if this property is switched on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10314) Spark dataframe will get wrong schema if user executes add/drop column DDL
[ https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715271#comment-16715271 ] Nikolay Izhikov edited comment on IGNITE-10314 at 12/10/18 6:12 PM: [~ldz] I left comment in PR. Also, please, see my mail into discussion thread. was (Author: nizhikov): [~ldz] I left comment in PR. Also, please, see my main into discussion thread. > Spark dataframe will get wrong schema if user executes add/drop column DDL > -- > > Key: IGNITE-10314 > URL: https://issues.apache.org/jira/browse/IGNITE-10314 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > When user performs add/remove column in DDL, Spark will get the old/wrong > schema. > > Analyse > Currently Spark data frame API relies on QueryEntity to construct schema, but > QueryEntity in QuerySchema is a local copy of the original QueryEntity, so > the original QueryEntity is not updated when modification happens. > > Solution > Get the latest schema using JDBC thin driver's column metadata call, then > update fields in QueryEntity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10314) Spark dataframe will get wrong schema if user executes add/drop column DDL
[ https://issues.apache.org/jira/browse/IGNITE-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715271#comment-16715271 ] Nikolay Izhikov commented on IGNITE-10314: -- [~ldz] I left comment in PR. Also, please, see my main into discussion thread. > Spark dataframe will get wrong schema if user executes add/drop column DDL > -- > > Key: IGNITE-10314 > URL: https://issues.apache.org/jira/browse/IGNITE-10314 > Project: Ignite > Issue Type: Bug > Components: spark >Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7 >Reporter: Ray >Assignee: Ray >Priority: Critical > Fix For: 2.8 > > > When user performs add/remove column in DDL, Spark will get the old/wrong > schema. > > Analyse > Currently Spark data frame API relies on QueryEntity to construct schema, but > QueryEntity in QuerySchema is a local copy of the original QueryEntity, so > the original QueryEntity is not updated when modification happens. > > Solution > Get the latest schema using JDBC thin driver's column metadata call, then > update fields in QueryEntity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8227) Research possibility and implement JUnit test failure handler for TeamCity
[ https://issues.apache.org/jira/browse/IGNITE-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715241#comment-16715241 ] ASF GitHub Bot commented on IGNITE-8227: Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/5584 > Research possibility and implement JUnit test failure handler for TeamCity > -- > > Key: IGNITE-8227 > URL: https://issues.apache.org/jira/browse/IGNITE-8227 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Major > > After IEP-14 > (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling) > we found a lot of TC failures involving unexpected nodes stop. > To avoid suites exit codes, tests have NoOpFailureHandler as default. > But instead of this, better handler could be > stopNode + fail currenly running test with message. > This default allows to identify such failures without log-message fail > condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10626) Save authenticated Webconsole session for more than one page refresh
Evgenii Zhuravlev created IGNITE-10626: -- Summary: Save authenticated Webconsole session for more than one page refresh Key: IGNITE-10626 URL: https://issues.apache.org/jira/browse/IGNITE-10626 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Now, it's needed to enter login and password after each page refresh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10625) Do first checkpoint on node start before join to topology
Pavel Kovalenko created IGNITE-10625:
Summary: Do first checkpoint on node start before join to topology
Key: IGNITE-10625
URL: https://issues.apache.org/jira/browse/IGNITE-10625
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 2.4
Reporter: Pavel Kovalenko
Fix For: 2.8
If a node joins to active cluster we do the first checkpoint during PME when
partition states have restored here
{code:java}
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopology#afterStateRestored
{code}
In IGNITE-9420 we moved logical recovery phase before joining to topology and
currently when a node joins to active cluster it already has all recovered
partitions. It means that we can safely do the first checkpoint after all
logical updates are applied. This change will accelerate PME process if there
were a lot of applied updates during recovery.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reopened IGNITE-4111: -- > Communication fails to send message if target node did not finish join process > -- > > Key: IGNITE-4111 > URL: https://issues.apache.org/jira/browse/IGNITE-4111 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Amelchev Nikita >Priority: Minor > Fix For: 2.8 > > Attachments: test onFirstMessage hang.log > > > Currently this scenario is possible: > - joining node sent join request and waits for > TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology > - others nodes already see this node and can send messages to it (for example > try to run compute job on this node) > - joining node can not receive message: TcpCommunicationSpi will hang inside > 'onFirstMessage' on 'getSpiContext' call, so sending node will get error > trying to establish connection > Possible fix: if in onFirstMessage() spi context is not available, then > TcpCommunicationSpi should send special response which indicates that this > node is not ready yet, and sender should retry after some time. > Also need check internal code for places where message can be unnecessarily > sent to node: one such place is > GridCachePartitionExchangeManager.refreshPartitions - message is sent to all > known nodes, but here we can filter by node order / finished exchage version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715151#comment-16715151 ] Alexey Goncharuk commented on IGNITE-4111: -- [~NSAmelchev] can you take a look at the reproducer provided by Alexei? > Communication fails to send message if target node did not finish join process > -- > > Key: IGNITE-4111 > URL: https://issues.apache.org/jira/browse/IGNITE-4111 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Amelchev Nikita >Priority: Minor > Fix For: 2.8 > > Attachments: test onFirstMessage hang.log > > > Currently this scenario is possible: > - joining node sent join request and waits for > TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology > - others nodes already see this node and can send messages to it (for example > try to run compute job on this node) > - joining node can not receive message: TcpCommunicationSpi will hang inside > 'onFirstMessage' on 'getSpiContext' call, so sending node will get error > trying to establish connection > Possible fix: if in onFirstMessage() spi context is not available, then > TcpCommunicationSpi should send special response which indicates that this > node is not ready yet, and sender should retry after some time. > Also need check internal code for places where message can be unnecessarily > sent to node: one such place is > GridCachePartitionExchangeManager.refreshPartitions - message is sent to all > known nodes, but here we can filter by node order / finished exchage version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[
https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715144#comment-16715144
]
Alexei Scherbakov edited comment on IGNITE-4111 at 12/10/18 5:19 PM:
-
This fails in master with NPE:
{noformat}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.failure.StopNodeFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
/**
*/
public class ClientReconnectSelfTest extends GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
cfg.setFailureHandler(new StopNodeFailureHandler());
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(1);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 32));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** */
public void testReconnect() throws Exception {
try {
IgniteEx crd = (IgniteEx)startGridsMultiThreaded(1);
IgniteEx client = startGrid("client");
stopGrid(0);
crd = startGrid(0);
crd.cluster().active(true);
awaitPartitionMapExchange();
}
finally {
stopAllGrids();
}
}
}
{noformat}
was (Author: ascherbakov):
This fails in master with NPE:
{noformat}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.failure.StopNodeFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
/**
*/
public class ClientReconnectSelfTest extends GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
cfg.setFailureHandler(new StopNodeFailureHandler());
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(1);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 32));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** */
public void testReconnect() throws Exception {
try {
IgniteEx crd = (IgniteEx)startGridsMultiThreaded(1);
IgniteEx client = startGrid("client");
stopGrid(0);
crd = startGrid(0);
crd.cluster().active(true);
awaitPartitionMapExchange();
}
finally {
stopAllGrids();
}
}
}
{noformat}
> Communication fails to send message if target node did not finish join process
>
[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[
https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715144#comment-16715144
]
Alexei Scherbakov commented on IGNITE-4111:
---
This fails in master with NPE:
{noformat}
package org.apache.ignite.internal.processors.cache;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.failure.StopNodeFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
/**
*/
public class ClientReconnectSelfTest extends GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
cfg.setFailureHandler(new StopNodeFailureHandler());
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(1);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 32));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** */
public void testReconnect() throws Exception {
try {
IgniteEx crd = (IgniteEx)startGridsMultiThreaded(1);
IgniteEx client = startGrid("client");
stopGrid(0);
crd = startGrid(0);
crd.cluster().active(true);
awaitPartitionMapExchange();
}
finally {
stopAllGrids();
}
}
}
{noformat}
> Communication fails to send message if target node did not finish join process
> --
>
> Key: IGNITE-4111
> URL: https://issues.apache.org/jira/browse/IGNITE-4111
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Semen Boikov
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.8
>
> Attachments: test onFirstMessage hang.log
>
>
> Currently this scenario is possible:
> - joining node sent join request and waits for
> TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology
> - others nodes already see this node and can send messages to it (for example
> try to run compute job on this node)
> - joining node can not receive message: TcpCommunicationSpi will hang inside
> 'onFirstMessage' on 'getSpiContext' call, so sending node will get error
> trying to establish connection
> Possible fix: if in onFirstMessage() spi context is not available, then
> TcpCommunicationSpi should send special response which indicates that this
> node is not ready yet, and sender should retry after some time.
> Also need check internal code for places where message can be unnecessarily
> sent to node: one such place is
> GridCachePartitionExchangeManager.refreshPartitions - message is sent to all
> known nodes, but here we can filter by node order / finished exchage version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery
[
https://issues.apache.org/jira/browse/IGNITE-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715095#comment-16715095
]
ASF GitHub Bot commented on IGNITE-10624:
-
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5629
IGNITE-10624 Update deployment id for recovered cache after join to topology
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10624
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5629.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 #5629
commit 009c617d2fa9c23e58bd0cad18dfdd7d92ebb363
Author: Pavel Kovalenko
Date: 2018-12-10T17:00:39Z
IGNITE-10624 Update deployment id for recovered cache after join to topology
Signed-off-by: Pavel Kovalenko
> Cache deployment id may be different that cluster-wide after recovery
> -
>
> Key: IGNITE-10624
> URL: https://issues.apache.org/jira/browse/IGNITE-10624
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.8
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.8
>
>
> When schema for a cache is changing
> (GridQueryProcessor#processSchemaOperationLocal),
> it may produce false-negative "CACHE_NOT_FOUND" message if a cache was
> started during recovery while cluster-wide descriptor was changed.
> {noformat}
> if (cacheInfo == null || !F.eq(depId,
> cacheInfo.dynamicDeploymentId()))
> throw new
> SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND,
> cacheName);
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery
Pavel Kovalenko created IGNITE-10624:
Summary: Cache deployment id may be different that cluster-wide
after recovery
Key: IGNITE-10624
URL: https://issues.apache.org/jira/browse/IGNITE-10624
Project: Ignite
Issue Type: Bug
Components: cache, sql
Affects Versions: 2.8
Reporter: Pavel Kovalenko
Assignee: Pavel Kovalenko
Fix For: 2.8
When schema for a cache is changing
(GridQueryProcessor#processSchemaOperationLocal),
it may produce false-negative "CACHE_NOT_FOUND" message if a cache was started
during recovery while cluster-wide descriptor was changed.
{noformat}
if (cacheInfo == null || !F.eq(depId, cacheInfo.dynamicDeploymentId()))
throw new
SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND,
cacheName);
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-1583) [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient
[ https://issues.apache.org/jira/browse/IGNITE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715076#comment-16715076 ] ASF GitHub Bot commented on IGNITE-1583: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/2121 > [Test Failed] GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient > - > > Key: IGNITE-1583 > URL: https://issues.apache.org/jira/browse/IGNITE-1583 > Project: Ignite > Issue Type: Test >Affects Versions: 1.5.0.final >Reporter: Anton Vinogradov >Priority: Major > Labels: Muted_test > Attachments: GridDiscoveryManagerAliveCacheSelfTest.testAlivesClient > > > See attach for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5100) Exchange queue is not used properly
[ https://issues.apache.org/jira/browse/IGNITE-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715059#comment-16715059 ] ASF GitHub Bot commented on IGNITE-5100: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1955 > Exchange queue is not used properly > --- > > Key: IGNITE-5100 > URL: https://issues.apache.org/jira/browse/IGNITE-5100 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Priority: Critical > Fix For: 2.1 > > > Currently exchange futures share same queue for pending(incomplete) and > completed exchanges. > The queue has fixed hardcoded size of 1000. > This leads to a problem when > 1000 nodes try to enter grid. > In such case oldest exchanges will be removed by ExchangeFutureSet size > limit, leading to whole exchange hanging. > Solution: > 1. Use separate queues for pending and completed exchanges. > 2. Pending exchange queue must be unbounded. > 3. Add system property to control exchange history. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3935) ClassLoaders are not switched during object deserialization
[
https://issues.apache.org/jira/browse/IGNITE-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715069#comment-16715069
]
ASF GitHub Bot commented on IGNITE-3935:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/3190
> ClassLoaders are not switched during object deserialization
> ---
>
> Key: IGNITE-3935
> URL: https://issues.apache.org/jira/browse/IGNITE-3935
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.4
>
>
> If an object is being deserialized with ClassLoader A then this ClassLoader A
> will be used for the deserialization of the whole object's state, i.e.,
> including all its fields that can be custom objects loaded by ClassLoader B.
> In a basic scenario we can have an object of some Ignite class that is
> presented in the classpath. That Ignite class may enclose an object that is
> loaded by peer-class-loading class loader. The deserialization will fail
> because Ignite won't switch to the peer-class-loading loader when it's needed.
> To reproduce the issue do the following:
> 1. Start a remote ignite node using {{./ignite.sh
> ../examples/config/example-ignite.xml}}
> 2. Run the code below
> {code}
> public class StreamingExample {`
> public static class StreamingExampleCacheEntryProcessor implements
> CacheEntryProcessor {
> @Override
> public Object process(MutableEntry e, Object... arg) throws
> EntryProcessorException {
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite =
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache =
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr =
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(StreamTransformer.from(new
> StreamingExampleCacheEntryProcessor()));
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> {code}
> However if to modify this code to the following everything will work fine
> {code}
> public class StreamingExample {
> public static class StreamingExampleCacheEntryProcessor extends
> StreamTransformer {
> @Override
> public Object process(MutableEntry e, Object... arg)
> throws EntryProcessorException {
> System.out.println("Executed!");
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException,
> IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite =
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache =
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr =
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(new StreamingExampleCacheEntryProcessor());
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[
https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715049#comment-16715049
]
ASF GitHub Bot commented on IGNITE-9542:
dspavlov commented on a change in pull request #95: IGNITE-9542: new run
history stripe
URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240287246
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java
##
@@ -446,9 +463,9 @@ protected String checkFailuresEx(String brachName) {
backgroundOpsCreds
);
-registerIssuesAndNotifyLater(failures, backgroundOpsCreds);
+String issResult = registerIssuesAndNotifyLater(failures,
backgroundOpsCreds);
Review comment:
Yes, I agree, but this string will go to the monitoring, so it is better to
see null showing there is some unexpected behavior there.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC bot] provide separated base/current branch history for PR page
> --
>
> Key: IGNITE-9542
> URL: https://issues.apache.org/jira/browse/IGNITE-9542
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> https://issues.apache.org/jira/browse/IGNITE-9376
> works incorrectly without separation of test history for the base and for a
> shown branch.
> It is suggested to refactor provided data for the current and for the base
> branch.
> It will allow showing blockers based on statistics from any base branch
> without relation with the previous quering of data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[ https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715063#comment-16715063 ] ASF GitHub Bot commented on IGNITE-9542: asfgit closed pull request #95: IGNITE-9542: new run history stripe URL: https://github.com/apache/ignite-teamcity-bot/pull/95 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC bot] provide separated base/current branch history for PR page > -- > > Key: IGNITE-9542 > URL: https://issues.apache.org/jira/browse/IGNITE-9542 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > > https://issues.apache.org/jira/browse/IGNITE-9376 > works incorrectly without separation of test history for the base and for a > shown branch. > It is suggested to refactor provided data for the current and for the base > branch. > It will allow showing blockers based on statistics from any base branch > without relation with the previous quering of data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails
[
https://issues.apache.org/jira/browse/IGNITE-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715064#comment-16715064
]
ASF GitHub Bot commented on IGNITE-5955:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/2986
> Ignite Continuous Query (Queries 3):
> IgniteCacheContinuousQueryClientReconnectTest fails
>
>
> Key: IGNITE-5955
> URL: https://issues.apache.org/jira/browse/IGNITE-5955
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.4, 2.5
>
>
> Reproducible locally with the same exception as on TC.
> In test log there is the following exception:
> {noformat}
> [2017-08-07
> 03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
> Failed to stop grid
> [igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0,
> cancel=true]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node
> disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
> at
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
> at
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
> at
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> According to [TC
> history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
> is failing since mid of April.
> Last commit where test has been passing is *b6b3d3754849*.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5869) Unexpected timeout exception while client connecting with different BinaryConfiguration compactFooter param.
[ https://issues.apache.org/jira/browse/IGNITE-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715061#comment-16715061 ] ASF GitHub Bot commented on IGNITE-5869: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/2482 > Unexpected timeout exception while client connecting with different > BinaryConfiguration compactFooter param. > > > Key: IGNITE-5869 > URL: https://issues.apache.org/jira/browse/IGNITE-5869 > Project: Ignite > Issue Type: Bug > Components: clients >Affects Versions: 2.0 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.3 > > Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java > > > While client connecting with different from cluster > BinaryConfiguration::setCompactFooter param, instead of expecting: > "configuration is not equal" exception catch: Join process timed out > exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5125) Need to improve logging in case of hang
[
https://issues.apache.org/jira/browse/IGNITE-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715056#comment-16715056
]
ASF GitHub Bot commented on IGNITE-5125:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1922
> Need to improve logging in case of hang
> ---
>
> Key: IGNITE-5125
> URL: https://issues.apache.org/jira/browse/IGNITE-5125
> Project: Ignite
> Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Priority: Critical
> Fix For: 2.1
>
>
> 1. When cache operation hangs on node it is not reported as hanged although
> partition map exchange cannot finish.
> {noformat}
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x7fdd260fd7c0> (a
> org.apache.ignite.internal.util.future.GridEmbeddedFuture)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:964)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1282)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:159)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2356)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4168)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2354)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2335)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2312)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1379)
> {noformat}
> {noformat}
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x7fa0698fee50> (a
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedSingleGetFuture)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:161)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4570)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4544)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:589)
> at
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.sequence(DataStructuresProcessor.java:397)
> {noformat}
> 2. Partition exchnage future dumps objects only limited number of times. I
> would suggest to switch to mode when we double the delay between dumps each
> time, but no more than 30min
> 3. If exchange worker is stuck at
> GridDhtPartitionsExchangeFuture.waitPartitionRelease then unreleased
> partitions should be reported (same rules as of pt 2 apply)
> {noformat}
> "exchange-worker-#93%...%" #143 prio=5 os_prio=0 tid=0x7fd782df3000
> nid=0x1526 waiting on condition [0x7fc2dc9c5000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x7fcab30006b8> (a
> org.apache.ignite.internal.util.future.GridCompoundFuture)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
>
[jira] [Commented] (IGNITE-4710) Better optimistic tx lock conflict client information.
[ https://issues.apache.org/jira/browse/IGNITE-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715054#comment-16715054 ] ASF GitHub Bot commented on IGNITE-4710: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1544 > Better optimistic tx lock conflict client information. > -- > > Key: IGNITE-4710 > URL: https://issues.apache.org/jira/browse/IGNITE-4710 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.8 >Reporter: Stanilovsky Evgeny >Assignee: Semen Boikov >Priority: Minor > Fix For: 2.0 > > > On tx optimistic exception we should provide information about key causing > conflict for easier debugging of conflict source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9777) Gathering local node IO statistics with cache and index dimensions
[
https://issues.apache.org/jira/browse/IGNITE-9777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715039#comment-16715039
]
Alexey Goncharuk commented on IGNITE-9777:
--
[~vozerov], [~jooger], can we get rid of {{deriveIndexType}} method from
{{IoStatisticsHolderIndex}} and move it to {{PageIO}}, for example? I think it
should be mandatory for the developer to define the statistics type when a new
{{PageIO}} type is added. Currently it is very easy to miss when a new index
type is added or current index structure changed.
> Gathering local node IO statistics with cache and index dimensions
> --
>
> Key: IGNITE-9777
> URL: https://issues.apache.org/jira/browse/IGNITE-9777
> Project: Ignite
> Issue Type: Task
> Components: persistence, sql
>Reporter: Yury Gerzhedovich
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-27
> Fix For: 2.8
>
>
> Should be gathered and exposed IO statistics on cache/index level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4654) GridMarshallerPerformanceTest fail
[
https://issues.apache.org/jira/browse/IGNITE-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715053#comment-16715053
]
ASF GitHub Bot commented on IGNITE-4654:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1493
> GridMarshallerPerformanceTest fail
> --
>
> Key: IGNITE-4654
> URL: https://issues.apache.org/jira/browse/IGNITE-4654
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Stanilovsky Evgeny
>Priority: Minor
> Fix For: 2.0
>
>
> NPE fail
> {code}
> [13:46:49,678][INFO ][main][root] >>> Starting test class:
> GridMarshallerPerformanceTest <<<
> [13:46:49,688][INFO ][main][root] >>> Starting test:
> GridMarshallerPerformanceTest#testGridMarshaller <<<
> [13:46:49,694][ERROR][main][root] Test failed.
> class org.apache.ignite.internal.util.lang.GridClosureException: Failed to
> serialize object:
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$TestObject@d0bb6d5
> at
> org.apache.ignite.internal.util.lang.GridFunc.wrap(GridFunc.java:4582)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:41)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest.runTest(GridMarshallerPerformanceTest.java:236)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest.testGridMarshaller(GridMarshallerPerformanceTest.java:132)
> 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:1803)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1718)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> serialize object:
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$TestObject@d0bb6d5
> at
> org.apache.ignite.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:197)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$3.applyx(GridMarshallerPerformanceTest.java:122)
> at
> org.apache.ignite.marshaller.GridMarshallerPerformanceTest$3.applyx(GridMarshallerPerformanceTest.java:120)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> ... 11 more
> Caused by: java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6437) DataStructure can not be obtained on client if it is created on server node.
[ https://issues.apache.org/jira/browse/IGNITE-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715047#comment-16715047 ] ASF GitHub Bot commented on IGNITE-6437: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/2779 > DataStructure can not be obtained on client if it is created on server node. > > > Key: IGNITE-6437 > URL: https://issues.apache.org/jira/browse/IGNITE-6437 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.1, 2.3 >Reporter: Mikhail Cherkasov >Priority: Critical > Fix For: 2.4 > > Attachments: NoQueueOnClientNodeTest.java, tc_111.png > > > DataStructure can not be obtained on client if it is created on server node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7112) Non informative "Failed to wait for partition map exchange" message.
[
https://issues.apache.org/jira/browse/IGNITE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715050#comment-16715050
]
ASF GitHub Bot commented on IGNITE-7112:
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/3144
> Non informative "Failed to wait for partition map exchange" message.
>
>
> Key: IGNITE-7112
> URL: https://issues.apache.org/jira/browse/IGNITE-7112
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Minor
> Fix For: 2.7
>
>
> Eventually can be observed "Failed to wait for partition map exchange" with
> no further detalization info, due to code below.
> {code:java}
> final long futTimeout = 2 * cctx.gridConfig().getNetworkTimeout();
> long nextDumpTime = 0;
> while (true) {
> try {
> resVer = exchFut.get(futTimeout, TimeUnit.MILLISECONDS);
> break;
> }
> catch (IgniteFutureTimeoutCheckedException ignored) {
> U.warn(diagnosticLog, "Failed to wait for partition map exchange [" +
> ...
> if (nextDumpTime <= U.currentTimeMillis()) {
> try {
> dumpDebugInfo(exchFut);
> }
> catch (Exception e) {
> U.error(diagnosticLog, "Failed to dump debug information: " + e, e);
> }
> nextDumpTime = U.currentTimeMillis() + nextDumpTimeout(dumpCnt++,
> futTimeout);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests
[ https://issues.apache.org/jira/browse/IGNITE-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-10620: Ignite Flags: (was: Docs Required) > [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests > -- > > Key: IGNITE-10620 > URL: https://issues.apache.org/jira/browse/IGNITE-10620 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > > Implement actual tests for tracked branches processing and issue detectors. > Skeletons: > org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector > org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor > The actual challenge is refactoring of configuration to use not singletons, > but some injected interfaces with mock-able alternatives, refactor scheduler, > and any other refactorings needed to cover issue detection by test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8849) Split suites to achieve 1 hour per suite run
[ https://issues.apache.org/jira/browse/IGNITE-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715014#comment-16715014 ] ASF GitHub Bot commented on IGNITE-8849: Github user EdShangGG closed the pull request at: https://github.com/apache/ignite/pull/4239 > Split suites to achieve 1 hour per suite run > > > Key: IGNITE-8849 > URL: https://issues.apache.org/jira/browse/IGNITE-8849 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4484) Call commit for read-only transactions.
[ https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715018#comment-16715018 ] ASF GitHub Bot commented on IGNITE-4484: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1522 > Call commit for read-only transactions. > --- > > Key: IGNITE-4484 > URL: https://issues.apache.org/jira/browse/IGNITE-4484 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.8 >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.0 > > > IGNITE-3601 introduces a behavior, which is not compliant with tx isolation > semantics. > Read-only transaction doesn't throw optimisitc exception in case if entry > version were changes by other writing tx. > With the appearance of IGNITE-4285 this is no longer needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10462) MVCC: Create "PDS 2" test suite for MVCC mode.
[
https://issues.apache.org/jira/browse/IGNITE-10462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715021#comment-16715021
]
Roman Kondakov commented on IGNITE-10462:
-
[~amashenkov], it looks like we've missed
{{IgnitePdsCacheStartStopWithFreqCheckpointTest}} - there are only atomic
caches start there. Please, add transactional mode to this test. Except for
this item everything else looks good for me.
> MVCC: Create "PDS 2" test suite for MVCC mode.
> --
>
> Key: IGNITE-10462
> URL: https://issues.apache.org/jira/browse/IGNITE-10462
> Project: Ignite
> Issue Type: Sub-task
> Components: mvcc
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.8
>
>
> Create MVCC version of IgnitePdsTestSuite2 and add it to TC.
> All non-relevant tests should be marked as ignored.
> Failed tests should be muted and tickets should be created for unknown
> failure reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9542) [TC bot] provide separated base/current branch history for PR page
[
https://issues.apache.org/jira/browse/IGNITE-9542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715019#comment-16715019
]
ASF GitHub Bot commented on IGNITE-9542:
zzzadruga commented on a change in pull request #95: IGNITE-9542: new run
history stripe
URL: https://github.com/apache/ignite-teamcity-bot/pull/95#discussion_r240279974
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcbot/issue/IssueDetector.java
##
@@ -446,9 +463,9 @@ protected String checkFailuresEx(String brachName) {
backgroundOpsCreds
);
-registerIssuesAndNotifyLater(failures, backgroundOpsCreds);
+String issResult = registerIssuesAndNotifyLater(failures,
backgroundOpsCreds);
Review comment:
if #registerIssuesAndNotifyLater returns null (if creds == null), method
return string like "Tests 4 Suites 3 were checked. **null**"
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [TC bot] provide separated base/current branch history for PR page
> --
>
> Key: IGNITE-9542
> URL: https://issues.apache.org/jira/browse/IGNITE-9542
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> https://issues.apache.org/jira/browse/IGNITE-9376
> works incorrectly without separation of test history for the base and for a
> shown branch.
> It is suggested to refactor provided data for the current and for the base
> branch.
> It will allow showing blockers based on statistics from any base branch
> without relation with the previous quering of data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4552) Optimize GridDhtLocalPartition.rmvQueue
[ https://issues.apache.org/jira/browse/IGNITE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715015#comment-16715015 ] ASF GitHub Bot commented on IGNITE-4552: Github user zstan closed the pull request at: https://github.com/apache/ignite/pull/1481 > Optimize GridDhtLocalPartition.rmvQueue > --- > > Key: IGNITE-4552 > URL: https://issues.apache.org/jira/browse/IGNITE-4552 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Priority: Major > Fix For: 2.0 > > Attachments: Plot_ThroughputLatencyProbe_01_20170203_1.png, > Plot_ThroughputLatencyProbe_01_31_origin.png, > Plot_ThroughputLatencyProbe_01_4552_mine.png, > Plot_ThroughputLatencyProbe_01_mine.png, > Plot_ThroughputLatencyProbe_01_mine_3node.png, > Plot_ThroughputLatencyProbe_01_origin.png, > Plot_ThroughputLatencyProbe_01_origin_3node.png, > Screenshot_20170124_155355.png, benchmark-put-remove-simultaneously.properties > > > Current implementation stores deferred entry removals in rmvQueue for > consistency guaranties. > This can lead to significant heap over-usage(I observed several Gbs) in case > of many caches with removals, because currently queue is cleared lazily after > reaching max capacity(200_000 by default). > This can be mitigated by using lower IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE, > but can lead to consistency issues in case of frequent cache updates. > Possible optimizations: > * Use single fixed size queue per all caches to overcome limitations of > IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE workaround. > * Do queue cleaning in background > * Move queue to an off-heap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8849) Split suites to achieve 1 hour per suite run
[ https://issues.apache.org/jira/browse/IGNITE-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev resolved IGNITE-8849. --- Resolution: Fixed > Split suites to achieve 1 hour per suite run > > > Key: IGNITE-8849 > URL: https://issues.apache.org/jira/browse/IGNITE-8849 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10623) Possible JVM crash when node stopped with errors
[
https://issues.apache.org/jira/browse/IGNITE-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715000#comment-16715000
]
Anton Kalashnikov commented on IGNITE-10623:
Looks good for me
> Possible JVM crash when node stopped with errors
>
>
> Key: IGNITE-10623
> URL: https://issues.apache.org/jira/browse/IGNITE-10623
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> {noformat}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x03a23bde,
> pid=5444, tid=0x18d0
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build
> 1.8.0_102-b14)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode
> windows-amd64 compressed oops)
> # Problematic frame:
> # J 25052 C2
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(IJZ)J
> (1421 bytes) @ 0x03a23bde [0x03a23800+0x3de]
> #
> # Core dump written. Default location:
> C:\BuildAgent\work\81a8bed9f07f3feb\ggprivate\hs_err_pid5444.mdmp
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> {noformat}
> Seems that it was caused by an erroneous stop on a node which left
> checkpoint-thread alive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-1683) .NET: IEvents.RemoteListen
[ https://issues.apache.org/jira/browse/IGNITE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Pligin reassigned IGNITE-1683: --- Assignee: Vladimir Pligin > .NET: IEvents.RemoteListen > -- > > Key: IGNITE-1683 > URL: https://issues.apache.org/jira/browse/IGNITE-1683 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.6 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Pligin >Priority: Major > Labels: .net, newbie > > Bring back IEvents.RemoteListen as soon as it is fixed in Java. > Currently rmtFilter is not actually a filter and semantics are unclear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10622) Undelivered ensure message to some nodes
[ https://issues.apache.org/jira/browse/IGNITE-10622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714947#comment-16714947 ] ASF GitHub Bot commented on IGNITE-10622: - GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5628 IGNITE-10622 to sent pending messages when new next node was selected You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10622 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5628.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 #5628 commit 2f301f3ebed56c787e23e9aeaf7b77c730ef4345 Author: Anton Kalashnikov Date: 2018-12-10T15:41:25Z IGNITE-10622 to sent pending messages when new next node was selected > Undelivered ensure message to some nodes > > > Key: IGNITE-10622 > URL: https://issues.apache.org/jira/browse/IGNITE-10622 > Project: Ignite > Issue Type: Bug >Reporter: Anton Kalashnikov >Assignee: Anton Kalashnikov >Priority: Major > > We have follow case: > * Grid from 5 nodes(node1, node2, node3, node4, node5) > * node1 detect that node4 was failed and send NodeFailed message to node2 > * node2 send NodeFailedNode3 message to node3 > * node3 accepted message but does not handle because it also failed > * node1 detect that node3 was failed and send NodeFailed message to node2 > * node2 select new next node(node4) and send NodeFailedNode3 message to node4 > As result node4 received only NodeFailedNode3 but don't received > NodeFailedNode3. > This case also valid for other ensure message which sending one after > another. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10464) MVCC: Create "PDS 4" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714899#comment-16714899 ] ASF GitHub Bot commented on IGNITE-10464: - GitHub user rkondakov opened a pull request: https://github.com/apache/ignite/pull/5627 IGNITE-10464: MVCC: Create "PDS 4" test suite for MVCC mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10464 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5627.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 #5627 commit f76b5497eec9c8026ee65fc49c21aedc4df265f4 Author: rkondakov Date: 2018-12-07T15:04:52Z IGNITE-10464: MVCC: Create "PDS 4" test suite for MVCC mode. > MVCC: Create "PDS 4" test suite for MVCC mode. > -- > > Key: IGNITE-10464 > URL: https://issues.apache.org/jira/browse/IGNITE-10464 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Roman Kondakov >Priority: Major > > Create MVCC version of IgnitePdsTestSuite4 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10359) MVCC: P2P deployment for EntryProcessor looks broken.
[
https://issues.apache.org/jira/browse/IGNITE-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714892#comment-16714892
]
ASF GitHub Bot commented on IGNITE-10359:
-
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5626
IGNITE-10359: Add deployment feature for EntryProcessor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10359
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5626.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 #5626
commit a55946f374c8fbfb358e3219ed0b4bcf842afa5b
Author: Andrey V. Mashenkov
Date: 2018-12-10T15:13:56Z
IGNITE-10359: Add deployment feature for EntryProcessor.
> MVCC: P2P deployment for EntryProcessor looks broken.
> -
>
> Key: IGNITE-10359
> URL: https://issues.apache.org/jira/browse/IGNITE-10359
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
>
> GridCacheTransactionalEntryProcessorDeploymentSelfTest and
> GridCacheBinaryTransactionalEntryProcessorDeploymentSelfTest fail with
> ClassNotFoundException.
>
>
> {noformat}
> [11:34:44]W: [org.apache.ignite:ignite-core] [2018-11-21
> 08:34:44,810][ERROR][sys-stripe-15-#41929%cache.GridCacheTransactionalEntryProcessorDeploymentSelfTest0%][GridCacheIoManager]
> Failed to
> [11:34:44]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to send response to node.
> Unsupported direct type [message=GridNearTxEnlistRequest [threadId
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:1043)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:577)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10136)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10188)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridInvokeValue.finishUnmarshal(GridInvokeValue.java:108)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistRequest.finishUnmarshal(GridNearTxEnlistRequest.java:359)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1527)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
>
[jira] [Commented] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming
[ https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714856#comment-16714856 ] Sergey Chugunov commented on IGNITE-8766: - I reviewed changes one more time and merged latest master, according to TC Bot there are no blocker tests. I think we could proceed with merging this to master branch. > TcpDiscoverySpi: discovery threads naming > - > > Key: IGNITE-8766 > URL: https://issues.apache.org/jira/browse/IGNITE-8766 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Sergey Chugunov >Assignee: Dmitry Karachentsev >Priority: Major > Labels: discovery > Fix For: 2.8 > > > Including information about next/prev nodes into names of discovery-related > threads could be very helpful when investigating situations of network > glitches. > tcp-disco-sock-reader and tcp-disco-msg-worker threads must include such > information in their names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10300) control.sh: incorrect error message after three tries on unsuccessful authorization.
[
https://issues.apache.org/jira/browse/IGNITE-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714875#comment-16714875
]
Pavel Voronkin commented on IGNITE-10300:
-
[~agoncharuk] we have common handling of such error here:
catch (Throwable e) {
if (isAuthError(e))
return error(ERR_AUTHENTICATION_FAILED, "Authentication error.", e);
if (isConnectionError(e))
return error(EXIT_CODE_CONNECTION_FAILED, "Connection to cluster failed.", e);
return error(EXIT_CODE_UNEXPECTED_ERROR, "", e);
}
it will be covered by if (isAuthError(e)) condition.
IMHO throwing exception in 2561, will be clearer than handling it on our own.
> control.sh: incorrect error message after three tries on unsuccessful
> authorization.
>
>
> Key: IGNITE-10300
> URL: https://issues.apache.org/jira/browse/IGNITE-10300
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Voronkin
>Assignee: Pavel Voronkin
>Priority: Major
> Fix For: 2.8
>
>
> 1. start grid with securirty enabled
> 2. try to issue control.sh --cache
> authentication credentials asked
> 3. enter incorrect credentials three times
> expected: Authentication error printed and logged
> actual: Latest topology update failed error printed
> {noformat}
> IGNITE_HOME=`pwd` bin/control.sh --cache list .
> Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
> 2018 Copyright(C) Apache Software Foundation
> User: mshonichev
>
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error, try connection again.
> user:
> password:
> Authentication error.
> Error: Latest topology update failed.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10556) Attempt to decrypt data records during read-only metastorage recovery leads to NPE
[
https://issues.apache.org/jira/browse/IGNITE-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Kovalenko reassigned IGNITE-10556:
Assignee: Pavel Kovalenko
> Attempt to decrypt data records during read-only metastorage recovery leads
> to NPE
> --
>
> Key: IGNITE-10556
> URL: https://issues.apache.org/jira/browse/IGNITE-10556
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.8
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Critical
> Fix For: 2.8
>
>
> Stacktrace:
> {noformat}
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$RestoreStateContext.lambda$next$0(GridCacheDatabaseSharedManager.java:4795)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$RestoreStateContext.next(GridCacheDatabaseSharedManager.java:4799)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$RestoreLogicalState.next(GridCacheDatabaseSharedManager.java:4926)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2370)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:733)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4493)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1048)
> ... 20 more
> {noformat}
> It happens because there is no encryption key for that cache group.
> Encryption keys are initialized after read-only metastorage is ready. There
> is a bug in RestoreStateContext which tries to filter out DataEntries in
> DataRecord by group id during read-only metastorage recovery. We should
> explicitly skip such records before filtering. As a possible solution, we
> should provide more flexible records filter to RestoreStateContext if we do
> recovery of read-only metastorage.
> We should also return something more meaningful instead of null if no
> encryption key is found for DataRecord, as it can be a silent problem for
> components iterating over WAL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8717) Move persisted cache configuration to metastore
[ https://issues.apache.org/jira/browse/IGNITE-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714833#comment-16714833 ] ASF GitHub Bot commented on IGNITE-8717: GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5625 IGNITE-8717 Cache configuration was moved to metastore You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8717 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5625.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 #5625 commit d95e8a78f1e71174c130b3b9bbc89f686e6f35ff Author: Sergey Antonov Date: 2018-11-20T13:42:46Z IGNITE-8717 Move cache configuration to metastore. commit 22dc40f634e502cef32c72512db7647cfcdf1e9e Author: Sergey Antonov Date: 2018-11-20T13:43:39Z IGNITE-8717 Move cache configuration to metastore. commit be9ea5710d680bb7be791ee0c3be4abedc575309 Author: Sergey Antonov Date: 2018-11-20T15:20:48Z IGNITE-8717 Add GridCacheConfigurationVersion and tests for it. commit c2441d1ae63ec6f86f7a0089c5c03df483d858a3 Author: Sergey Antonov Date: 2018-12-10T14:53:17Z Merge branch 'master' into ignite-8717 > Move persisted cache configuration to metastore > --- > > Key: IGNITE-8717 > URL: https://issues.apache.org/jira/browse/IGNITE-8717 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Sergey Antonov >Priority: Major > > Currently, we persist cache configuration to local files which resulted in > several inconsistencies when a node misses configuration update (create > index, cache destroy, etc). > I think the cache configuration should be saved to the metastore the same way > as baseline topology is saved. Same mechanics should be used for conflicting > configuration updates resolution. > Along with cache configuration, it also makes sense to move marshaller and > binary metadata to the metastore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming
[ https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16714856#comment-16714856 ] Sergey Chugunov edited comment on IGNITE-8766 at 12/10/18 3:03 PM: --- I reviewed changes one more time and merged latest master, according to TC Bot there are no blocker tests. We can proceed with merging this to master branch. was (Author: sergey-chugunov): I reviewed changes one more time and merged latest master, according to TC Bot there are no blocker tests. I think we could proceed with merging this to master branch. > TcpDiscoverySpi: discovery threads naming > - > > Key: IGNITE-8766 > URL: https://issues.apache.org/jira/browse/IGNITE-8766 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Sergey Chugunov >Assignee: Dmitry Karachentsev >Priority: Major > Labels: discovery > Fix For: 2.8 > > > Including information about next/prev nodes into names of discovery-related > threads could be very helpful when investigating situations of network > glitches. > tcp-disco-sock-reader and tcp-disco-msg-worker threads must include such > information in their names. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
