[jira] [Commented] (IGNITE-8801) Change default behaviour of atomic operations inside transactions
[
https://issues.apache.org/jira/browse/IGNITE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614107#comment-17614107
]
Ryabov Dmitrii commented on IGNITE-8801:
Yes, you can take it.
> Change default behaviour of atomic operations inside transactions
> -
>
> Key: IGNITE-8801
> URL: https://issues.apache.org/jira/browse/IGNITE-8801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ryabov Dmitrii
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise
>
> Need to change default behaviour of atomic operations to fail inside
> transactions.
> 1) Remove IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property.
> 2) Set default value to restrict atomic operations in
> \{{CacheOperationContext}} constructor without arguments and arguments for
> calls of another constructor.
> 3) Fix javadocs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-8801) Change default behaviour of atomic operations inside transactions
[
https://issues.apache.org/jira/browse/IGNITE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii reassigned IGNITE-8801:
--
Assignee: Julia Bakulina (was: Ryabov Dmitrii)
> Change default behaviour of atomic operations inside transactions
> -
>
> Key: IGNITE-8801
> URL: https://issues.apache.org/jira/browse/IGNITE-8801
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ryabov Dmitrii
>Assignee: Julia Bakulina
>Priority: Minor
> Labels: ise
>
> Need to change default behaviour of atomic operations to fail inside
> transactions.
> 1) Remove IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property.
> 2) Set default value to restrict atomic operations in
> \{{CacheOperationContext}} constructor without arguments and arguments for
> calls of another constructor.
> 3) Fix javadocs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13450) Add event fired before query execution
[
https://issues.apache.org/jira/browse/IGNITE-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201592#comment-17201592
]
Ryabov Dmitrii commented on IGNITE-13450:
-
[~jooger], can you take a look?
> Add event fired before query execution
> --
>
> Key: IGNITE-13450
> URL: https://issues.apache.org/jira/browse/IGNITE-13450
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: event
> Fix For: 2.10
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Create {{QueryExecutionEvent}}, which will be fired before query execution.
> Required fields are:
> - text of a query (with hidden arguments);
> - arguments of query;
> - query type;
> - node id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13472) JDBC bulkload operations are processed with wrong security context
[
https://issues.apache.org/jira/browse/IGNITE-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200954#comment-17200954
]
Ryabov Dmitrii commented on IGNITE-13472:
-
[~garus.d.g], can you take a look PR?
> JDBC bulkload operations are processed with wrong security context
> --
>
> Key: IGNITE-13472
> URL: https://issues.apache.org/jira/browse/IGNITE-13472
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
> {code:java}
> [12:02:56] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true]]class
> org.apache.ignite.IgniteCheckedException: Authorization failed
> [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.plugin.security.SecurityException:
> Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
> ... 4 more
> {code}
> This exception means the put operation is processed with node context instead
> of user. Also, operation doesn't finish successfully.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13472) JDBC bulkload operations are processed with wrong security context
[
https://issues.apache.org/jira/browse/IGNITE-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-13472:
Fix Version/s: 2.10
> JDBC bulkload operations are processed with wrong security context
> --
>
> Key: IGNITE-13472
> URL: https://issues.apache.org/jira/browse/IGNITE-13472
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
> {code:java}
> [12:02:56] (err) Failed to execute compound future reducer:
> GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=0, done=false,
> cancelled=false, err=null, futs=TransformCollectionView [true]]class
> org.apache.ignite.IgniteCheckedException: Authorization failed
> [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.plugin.security.SecurityException:
> Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
> subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
> type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
> at
> org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
> at
> org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
> at
> org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
> ... 4 more
> {code}
> This exception means the put operation is processed with node context instead
> of user. Also, operation doesn't finish successfully.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13472) JDBC bulkload operations are processed with wrong security context
[
https://issues.apache.org/jira/browse/IGNITE-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-13472:
Description:
{{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
{code:java}
[12:02:56] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true]]class
org.apache.ignite.IgniteCheckedException: Authorization failed [perm=CACHE_PUT,
name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.plugin.security.SecurityException:
Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
... 4 more
{code}
This exception means the put operation is processed with node context instead
of user. Also, operation doesn't finish successfully.
was:
{{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
{code:java}
[12:02:56] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true]]class
org.apache.ignite.IgniteCheckedException: Authorization failed [perm=CACHE_PUT,
name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.plugin.security.SecurityException:
Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
... 4 more
{code}
> JDBC bulkload operations are processed with wrong security context
> --
>
> Key: IGNITE-13472
> URL: https://issues.apache.org/jira/browse/IGNITE-13472
> Project: Ignite
> Issue Type: Bug
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
>
> {{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
> {code:java}
> [12:02:56] (err) Failed to execute
[jira] [Created] (IGNITE-13472) JDBC bulkload operations are processed with wrong security context
Ryabov Dmitrii created IGNITE-13472:
---
Summary: JDBC bulkload operations are processed with wrong
security context
Key: IGNITE-13472
URL: https://issues.apache.org/jira/browse/IGNITE-13472
Project: Ignite
Issue Type: Bug
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
{{JdbcAuthorizationTest.testCopyFrom()}} have many exceptions like
{code:java}
[12:02:56] (err) Failed to execute compound future reducer: GridCompoundFuture
[rdc=null, initFlag=1, lsnrCalls=0, done=false, cancelled=false, err=null,
futs=TransformCollectionView [true]]class
org.apache.ignite.IgniteCheckedException: Authorization failed [perm=CACHE_PUT,
name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7589)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:979)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.plugin.security.SecurityException:
Authorization failed [perm=CACHE_PUT, name=test-bulkload-cache,
subject=TestSecuritySubject{id=ca0e2ed9-f877-4c49-a80e-11a1c7a0,
type=REMOTE_NODE, login=jdbc.JdbcAuthorizationTest0}]
at
org.apache.ignite.internal.processors.security.impl.TestSecurityProcessor.authorize(TestSecurityProcessor.java:153)
at
org.apache.ignite.internal.processors.security.IgniteSecurityProcessor.authorize(IgniteSecurityProcessor.java:207)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.checkSecurityPermission(DataStreamerUpdateJob.java:170)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:123)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7087)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:971)
... 4 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13450) Add event fired before query execution
[
https://issues.apache.org/jira/browse/IGNITE-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-13450:
Description:
Create {{QueryExecutionEvent}}, which will be fired before query execution.
Required fields are:
- text of a query (with hidden arguments);
- arguments of query;
- query type;
- node id.
was:
Create QUERY_EXECUITION_EVENT, which will be fired before query execution.
Required fields are:
- text of a query (with hidden arguments);
- arguments of query;
- query type;
- node id.
> Add event fired before query execution
> --
>
> Key: IGNITE-13450
> URL: https://issues.apache.org/jira/browse/IGNITE-13450
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
>
> Create {{QueryExecutionEvent}}, which will be fired before query execution.
> Required fields are:
> - text of a query (with hidden arguments);
> - arguments of query;
> - query type;
> - node id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13450) Add event fired before query execution
Ryabov Dmitrii created IGNITE-13450: --- Summary: Add event fired before query execution Key: IGNITE-13450 URL: https://issues.apache.org/jira/browse/IGNITE-13450 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Create QUERY_EXECUITION_EVENT, which will be fired before query execution. Required fields are: - text of a query (with hidden arguments); - arguments of query; - query type; - node id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13314) Tasks from GridClient.compute() are processed with wrong SecurityContext
[
https://issues.apache.org/jira/browse/IGNITE-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii reassigned IGNITE-13314:
---
Assignee: Ryabov Dmitrii
> Tasks from GridClient.compute() are processed with wrong SecurityContext
>
>
> Key: IGNITE-13314
> URL: https://issues.apache.org/jira/browse/IGNITE-13314
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
> Labels: iep-41
> Attachments: ComputeTaskRemoteSecurityContextCheckGridClientTest.java
>
>
> Currently, tasks started from {{GridClient.compute()}} are processed with
> server node's security context.
> Example attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13314) Tasks from GridClient.compute() are processed with wrong SecurityContext
Ryabov Dmitrii created IGNITE-13314:
---
Summary: Tasks from GridClient.compute() are processed with wrong
SecurityContext
Key: IGNITE-13314
URL: https://issues.apache.org/jira/browse/IGNITE-13314
Project: Ignite
Issue Type: Task
Reporter: Ryabov Dmitrii
Attachments: ComputeTaskRemoteSecurityContextCheckGridClientTest.java
Currently, tasks started from {{GridClient.compute()}} are processed with
server node's security context.
Example attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13237) In some cases IgniteClient#query does not fire CacheQueryExecutedEvent
Ryabov Dmitrii created IGNITE-13237:
---
Summary: In some cases IgniteClient#query does not fire
CacheQueryExecutedEvent
Key: IGNITE-13237
URL: https://issues.apache.org/jira/browse/IGNITE-13237
Project: Ignite
Issue Type: Task
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
Fix For: 2.10
In some cases {{IgniteClient#query}} does not fire {{CacheQueryExecutedEvent}}.
Reproducer:
{code:java|title=IgniteCacheAbstractQuerySelfTest.java}
@Test
public void testClientSqlQueryEvents() throws Exception {
CountDownLatch execLatch = new CountDownLatch(9);
IgnitePredicate lsnr = evt -> {
assert evt instanceof CacheQueryExecutedEvent;
System.out.println(">>> EVENT: " + evt);
CacheQueryExecutedEvent qe = (CacheQueryExecutedEvent)evt;
assertEquals("SQL_PUBLIC_TEST_TABLE", qe.cacheName());
assertNotNull(qe.clause());
assertNull(qe.scanQueryFilter());
assertNull(qe.continuousQueryFilter());
execLatch.countDown();
return true;
};
ignite().events().localListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
ClientConfiguration cc = new
ClientConfiguration().setAddresses(Config.SERVER);
try (IgniteClient client = Ignition.startClient(cc)) {
client.query(new SqlFieldsQuery("create table TEST_TABLE(key int
primary key, val int)"))
.getAll();
client.query(new SqlFieldsQuery("insert into TEST_TABLE values (?,
?)").setArgs(1, 1))
.getAll();
client.query(new SqlFieldsQuery("update TEST_TABLE set val = ?2 where
key = ?1").setArgs(1, 2))
.getAll();
client.query(new SqlFieldsQuery("select * from TEST_TABLE"))
.getAll();
client.query(new SqlFieldsQuery("create index idx_1 on
TEST_TABLE(key)"))
.getAll();
client.query(new SqlFieldsQuery("drop index idx_1"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE add column val2
int"))
.getAll();
client.query(new SqlFieldsQuery("alter table TEST_TABLE drop val2"))
.getAll();
client.query(new SqlFieldsQuery("drop table TEST_TABLE"))
.getAll();
assertTrue(execLatch.await(3_000, MILLISECONDS));
}
finally {
ignite().events().stopLocalListen(lsnr, EVT_CACHE_QUERY_EXECUTED);
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-10593) Proper NoOpHandler injection
[ https://issues.apache.org/jira/browse/IGNITE-10593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii resolved IGNITE-10593. - Fix Version/s: (was: 2.9) Resolution: Invalid > Proper NoOpHandler injection > > > Key: IGNITE-10593 > URL: https://issues.apache.org/jira/browse/IGNITE-10593 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > > Improve no-op failure handler usage by replacing copy-pasted code by > extending from class with changed default handler as recommended in > [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Default-failure-handler-was-changed-for-tests-tp38900p39010.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (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:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-8227: -- Assignee: (was: Ryabov Dmitrii) > 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: Dmitry Pavlov >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > 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 (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033493#comment-17033493 ] Ryabov Dmitrii commented on IGNITE-12049: - Done. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Fix For: 2.9 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-12049: Description: Add user attributes to thin clients (like node attributes for server nodes). (was: Add user attributes to thin clients (like node attributes for server nodes). Make sure that custom authenticators can use these attributes.) > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Fix For: 2.9 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12648) Add user attributes to non-Java thin clients
Ryabov Dmitrii created IGNITE-12648: --- Summary: Add user attributes to non-Java thin clients Key: IGNITE-12648 URL: https://issues.apache.org/jira/browse/IGNITE-12648 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Add user attributes to non-Java thin clients (like node attributes for server nodes). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033434#comment-17033434 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], I expanded description of setters and created ticket for readme's page [1]. [1] https://issues.apache.org/jira/browse/IGNITE-12640 > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12640) Update readme's advanced security page
Ryabov Dmitrii created IGNITE-12640:
---
Summary: Update readme's advanced security page
Key: IGNITE-12640
URL: https://issues.apache.org/jira/browse/IGNITE-12640
Project: Ignite
Issue Type: Task
Reporter: Ryabov Dmitrii
Add next paragraph to advanced security page [1] as last paragraph of the
Authorization section.
{noformat}
Also, custom 'GridSecurityProcessor' let you check thin client's additional
info inside both authentication and authorization. You can get info from
'AuthenticationContext.nodeAttributes()' map. To setup additional info use
'setUserAttributes()' for client configuration or 'userAttributesFactory'
parameter for JDBC connection.
{noformat}
[1] https://apacheignite.readme.io/docs/advanced-security
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031582#comment-17031582
]
Ryabov Dmitrii commented on IGNITE-12049:
-
I don't think we need to extend the build-in authenticator to be customizable,
as we have no build-in authorizer. But custom {{GridSecurityProcessor}} allows
to customize both authentication and authorization.
This change suites better for 3.0 wishlist [1] than for current changes.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031366#comment-17031366
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov]
I reverted renaming attributes back to {{userAttrs}}. And rerun tests - nothing
broken.
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029776#comment-17029776 ] Ryabov Dmitrii edited comment on IGNITE-12049 at 2/4/20 1:55 PM: - [~ptupitsyn], we should add customization to data sent by thin clients. It will allow sending additional info like specific parameters of user program, client version, additional passwords/tokens, and allows dirty tricks for those, who need something else. If you know server node's system that also should get additional info - let's add info to it too (in a separate ticket). was (Author: somefire): [~ptupitsyn], we should add customization to data sent by thin clients. It will allow sending additional info like client version, additional passwords/tokens, and allows dirty tricks for those, who need something else. If you know a system that also should get additional info - let's add info to it too (in a separate ticket). > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029776#comment-17029776 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ptupitsyn], we should add customization to data sent by thin clients. It will allow sending additional info like client version, additional passwords/tokens, and allows dirty tricks for those, who need something else. If you know a system that also should get additional info - let's add info to it too (in a separate ticket). > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028981#comment-17028981 ] Ryabov Dmitrii commented on IGNITE-12049: - They are accessible through connection, so, when we want to do something with attributes besides authentication, we just take them from the connection. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027421#comment-17027421 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov] Currently, we can use attrs of thin clients only for authentication. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024407#comment-17024407 ] Ryabov Dmitrii edited comment on IGNITE-12049 at 1/30/20 8:34 AM: -- [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. Can we continue to review? was (Author: somefire): [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. Can we continue to review? > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024407#comment-17024407 ] Ryabov Dmitrii edited comment on IGNITE-12049 at 1/30/20 8:33 AM: -- [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. Can we continue to review? was (Author: somefire): [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024407#comment-17024407 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], I restricted attributes by `String` class as suggested on discussion. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 2h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12493) Test refactoring. Explicit method for starting client nodes
[
https://issues.apache.org/jira/browse/IGNITE-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021887#comment-17021887
]
Ryabov Dmitrii commented on IGNITE-12493:
-
Looks like no tests broken.
> Test refactoring. Explicit method for starting client nodes
> ---
>
> Key: IGNITE-12493
> URL: https://issues.apache.org/jira/browse/IGNITE-12493
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7.6
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: newbie
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> Right now there is almost 500 explicit usage of {{setClientMode}} in tests.
> Seems we should support the starting of client nodes in test framework.
> We should refactor tests to use {{startClientNode(String name)}}.
> This will simplify tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017989#comment-17017989
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov],
You are right, {{GridClientConfiguration().setMarshaller(new
GridClientJdkMarshaller())}} works for GridClients, but other thin clients have
hardcoded binary optimized marshaller and I'm not sure that replacing
marshaller is good idea.
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017834#comment-17017834
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov]
Before marshaller will write object, it will check class in
{{MarshallerContext}} to make sure that receiving node have this class too. But
{{MarshallerContext}} contains classes from {{META-INF/classnames.properties}}
only (and no classes from classpath). So, marshaller tries to send class
descriptor to node. But thin clients have no such mechanism.
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016979#comment-17016979 ] Ryabov Dmitrii edited comment on IGNITE-12049 at 1/17/20 9:12 AM: -- [~ascherbakov], may be we allow primitive types only? And add user classes later. UPD: I investigated the issue. Server nodes use discovery for loading classes, so, to enable classloading we need to add discovery manager into thin clients or make another classloading mechanism. I think these solutions are too heavy for lightweight thin clients. was (Author: somefire): [~ascherbakov], may be we allow primitive types only? And add user classes later. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016979#comment-17016979 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], may be we allow primitive types only? And add user classes later. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016911#comment-17016911
]
Ryabov Dmitrii commented on IGNITE-12049:
-
It is Ignite's magic! Class must be declared in
{{META-INF/classnames.properties}}.
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016764#comment-17016764
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov], problem is in peer classloading - it doesn't work for thin
clients. So, both server and client should have {{MyClass}}, and it should be
declared in {{META-INF/classnames.properties}}. I added appropriate message to
user attribute setters.
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014224#comment-17014224 ] Ryabov Dmitrii commented on IGNITE-12049: - I resolved merge conflict. Checking NPE. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011550#comment-17011550 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], what test fails for you? On what OS? Did you tried clean and rebuild project? > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999670#comment-16999670 ] Ryabov Dmitrii commented on IGNITE-12049: - # How? I create `ctx`, put it into writer and it should be used in `writeMap()` # Some troubles with Cache 6 suite, which is failed on the [master|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=] too. # Agree. > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-12049: Description: Add user attributes to thin clients (like node attributes for server nodes). Make sure that custom authenticators can use these attributes. (was: Add SSL certificates to AuthenticationContext, so, authenticators can make additional checks based on SSL certificates.) > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add user attributes to thin clients (like node attributes for server nodes). > Make sure that custom authenticators can use these attributes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12049) Add user attributes to thin clients
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-12049: Summary: Add user attributes to thin clients (was: Allow custom authenticators to use SSL certificates) > Add user attributes to thin clients > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add SSL certificates to AuthenticationContext, so, authenticators can make > additional checks based on SSL certificates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998179#comment-16998179
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov], I made the changes:
GridClient - {{GridClientConfiguration}} received parameter {{Map userAttrs}}. Attributes are passed in the {{GridClientMessage}}.
IgniteClient - {{ClientConfiguration}} received parameter {{Map
userAttrs}}. Attributes are passed through {{TcpClientChannel}}.
JDBC - {{ConnectionProperties}} received parameter {{userAttributes}}, which
should be filled with {{factory>}} name. Attributes are
passed through {{BinaryWriter}} as other message.
ODBC - TODO. I'd like to make it in a separate ticket.
Can you take a look?
> Allow custom authenticators to use SSL certificates
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add SSL certificates to AuthenticationContext, so, authenticators can make
> additional checks based on SSL certificates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986090#comment-16986090 ] Ryabov Dmitrii commented on IGNITE-12049: - [~ascherbakov], I thought about this task and agree that passing certificates to node attributes is enough. For a common client, attributes can be configured in `ClientConfiguration`. For JDBC/ODBC, attributes can't be passed directly to the driver, so, I propose to pass a factory class name and create attributes inside the factory. Is it ok for you? > Allow custom authenticators to use SSL certificates > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > Add SSL certificates to AuthenticationContext, so, authenticators can make > additional checks based on SSL certificates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12399) Java thin client: add cache expiry policies
[ https://issues.apache.org/jira/browse/IGNITE-12399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984947#comment-16984947 ] Ryabov Dmitrii commented on IGNITE-12399: - Looks good to me. > Java thin client: add cache expiry policies > --- > > Key: IGNITE-12399 > URL: https://issues.apache.org/jira/browse/IGNITE-12399 > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: thin > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement: > * Dynamic cache creation with expire policy. > * Put data into the cache with expire policy. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12386) The InvalidServerTest.testInvalidServer test is flacky
[
https://issues.apache.org/jira/browse/IGNITE-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980078#comment-16980078
]
Ryabov Dmitrii commented on IGNITE-12386:
-
Looks good to me.
> The InvalidServerTest.testInvalidServer test is flacky
> --
>
> Key: IGNITE-12386
> URL: https://issues.apache.org/jira/browse/IGNITE-12386
> Project: Ignite
> Issue Type: Test
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The InvalidServerTest.testInvalidServer test is flacky.
> The reason is that in the test two clusters are started, instead of one.
> Because TcpDiscoveryMulticastIpFinder is used by default.
> {noformat}
> 03:41:32] Topology snapshot [ver=1, locNode=10ecdb9c, servers=1, clients=0,
> state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB]
> [03:41:36] Topology snapshot [ver=1, locNode=20f59b4f, servers=1, clients=0,
> state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB]
> [03:41:40] Topology snapshot [ver=2, locNode=cecf2df6, servers=2, clients=0,
> state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB]
> {noformat}
> [Fail
> example.|https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=4771562&_focus=233870]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977552#comment-16977552
]
Ryabov Dmitrii commented on IGNITE-12049:
-
{quote}
User can put any value to node attributes
{quote}
Yes, user can put any certificate, but we can't get SSL certificate outside of
`ServerImpl`. User can get it inside custom SSL factory, but I don't see the
way to correlate certificate with connecting node, when several nodes
connecting simultaneously.
3. Agree, I'll do it.
> Allow custom authenticators to use SSL certificates
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add SSL certificates to AuthenticationContext, so, authenticators can make
> additional checks based on SSL certificates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976604#comment-16976604
]
Ryabov Dmitrii edited comment on IGNITE-12049 at 11/18/19 2:56 PM:
---
[~ascherbakov], thank you for review.
{quote}1. For "normal" cluster nodes attributes are already available using
ClusterNode.attributes and user can just set any attribute and use it in custom
authenticator without any changes in core by implementing [1].
Do I understand correctly the fix is only relevant for thin clients
authenticated using [2] and not having associated local attributes ?
Shouldn't we instead provide the ability for thin clients to have attributes
and avoid changing IgniteConfiguration ?
{quote}
The problem is that user can use different certificates for node-to-node
connection and put inside attributes. For "normal" cluster nodes we put
certificates from SSL connection into attributes. For thin clients we do the
same.
For local authentication we don't need certificates because there is no
node-to-node connection.
{quote}2. Why the new attribute is not available during authentication for
jdbc/odbc client types ?
{quote}
I missed it. Work in progress.
{quote}3. Can you create an example of using custom authenticator with
certificates ?
{quote}
I made tests in {{SslCertificatesCheckTest}}. Tests use
{{TestSslSecurityProcessor}}, which checks certificates during authentication.
was (Author: somefire):
[~ascherbakov], thank you for review.
{quote}1. For "normal" cluster nodes attributes are already available using
ClusterNode.attributes and user can just set any attribute and use it in custom
authenticator without any changes in core by implementing [1].
Do I understand correctly the fix is only relevant for thin clients
authenticated using [2] and not having associated local attributes ?
Shouldn't we instead provide the ability for thin clients to have attributes
and avoid changing IgniteConfiguration ?
{quote}
The problem is that user can use different certificates for node-to-node
connection and put inside attributes. For "normal" cluster nodes we put
certificates from SSL connection into attributes. For thin clients we do the
same.
For local authentication we don't need certificates because there is no
node-to-node connection.
{quote}2. Why the new attribute is not available during authentication for
jdbc/odbc client types ?
{quote}
I missed it. Work in progress.
{quote}3. Can you create an example of using custom authenticator with
certificates ?
{quote}
I made tests in SslCertificatesCheckTest. Tests use TestSslSecurityProcessor,
which checks certificates during authentication.
> Allow custom authenticators to use SSL certificates
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add SSL certificates to AuthenticationContext, so, authenticators can make
> additional checks based on SSL certificates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976604#comment-16976604
]
Ryabov Dmitrii commented on IGNITE-12049:
-
[~ascherbakov], thank you for review.
{quote}1. For "normal" cluster nodes attributes are already available using
ClusterNode.attributes and user can just set any attribute and use it in custom
authenticator without any changes in core by implementing [1].
Do I understand correctly the fix is only relevant for thin clients
authenticated using [2] and not having associated local attributes ?
Shouldn't we instead provide the ability for thin clients to have attributes
and avoid changing IgniteConfiguration ?
{quote}
The problem is that user can use different certificates for node-to-node
connection and put inside attributes. For "normal" cluster nodes we put
certificates from SSL connection into attributes. For thin clients we do the
same.
For local authentication we don't need certificates because there is no
node-to-node connection.
{quote}2. Why the new attribute is not available during authentication for
jdbc/odbc client types ?
{quote}
I missed it. Work in progress.
{quote}3. Can you create an example of using custom authenticator with
certificates ?
{quote}
I made tests in SslCertificatesCheckTest. Tests use TestSslSecurityProcessor,
which checks certificates during authentication.
> Allow custom authenticators to use SSL certificates
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Add SSL certificates to AuthenticationContext, so, authenticators can make
> additional checks based on SSL certificates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12232) NPE while node join processing
[ https://issues.apache.org/jira/browse/IGNITE-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946935#comment-16946935 ] Ryabov Dmitrii commented on IGNITE-12232: - [~mmuzaf], can you review? > NPE while node join processing > -- > > Key: IGNITE-12232 > URL: https://issues.apache.org/jira/browse/IGNITE-12232 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe > exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12232) NPE while node join processing
[ https://issues.apache.org/jira/browse/IGNITE-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-12232: --- Assignee: Ryabov Dmitrii > NPE while node join processing > -- > > Key: IGNITE-12232 > URL: https://issues.apache.org/jira/browse/IGNITE-12232 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > > ServerImpl.RingMessageWorker#processNodeAddedMessage method throws npe > exception in case DiscoverySpiNodeAuthenticator#authenticateNode returns null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
[ https://issues.apache.org/jira/browse/IGNITE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934221#comment-16934221 ] Ryabov Dmitrii commented on IGNITE-11094: - [~Jokser], tests are finished and have no new failures. [Zookeeper suite|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeper?branch=pull%2F6799%2Fhead&buildTypeTab=overview] [Zookeeper (Discovery) 1 suite|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery1?branch=pull%2F6799%2Fhead&buildTypeTab=overview] [Zookeeper (Discovery) 2 suite|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery2?branch=pull%2F6799%2Fhead&buildTypeTab=overview] [Zookeeper (Discovery) 3 suite|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery3?branch=pull%2F6799%2Fhead&buildTypeTab=overview] [Zookeeper (Discovery) 4 suite|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ZooKeeperDiscovery4?branch=pull%2F6799%2Fhead&buildTypeTab=overview] > Add SSL support for ignite zookeeper SPI > > > Key: IGNITE-11094 > URL: https://issues.apache.org/jira/browse/IGNITE-11094 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > Time Spent: 6.5h > Remaining Estimate: 0h > > ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK > server connections if Zookeeper SPI used. > 1. > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
[
https://issues.apache.org/jira/browse/IGNITE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927603#comment-16927603
]
Ryabov Dmitrii commented on IGNITE-11094:
-
Apache Zookeeper supports SSL since 3.5.x version, so, to write a test we need
to update zk version (and Curator version, because it tests Zookeeper).
I added {{ZookeeperDiscoverySpiSslTest}} class and edited
{{ZookeeperDiscoverySpiTestBase}} class to test SSL connection. In the same
time, version update requires changes in some other test classes.
In {{ZookeeperDiscoveryImpl}} class I fixed a bug - with enabled custom
security, NPE happens in {{ZookeeperDiscoveryImpl.validateJoiningNode}} on spi
validation, because currently {{ATTR_SECURITY_SUBJECT_V2}} is placed into node
attrs after validation.
> Add SSL support for ignite zookeeper SPI
>
>
> Key: IGNITE-11094
> URL: https://issues.apache.org/jira/browse/IGNITE-11094
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK
> server connections if Zookeeper SPI used.
> 1.
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (IGNITE-8622) Zookeeper and TCP discovery SPI' getSpiState method inconsistent
[ https://issues.apache.org/jira/browse/IGNITE-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-8622: -- Assignee: Ryabov Dmitrii > Zookeeper and TCP discovery SPI' getSpiState method inconsistent > > > Key: IGNITE-8622 > URL: https://issues.apache.org/jira/browse/IGNITE-8622 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Max Shonichev >Assignee: Ryabov Dmitrii >Priority: Minor > Labels: jmx > Fix For: 2.8 > > > getSpiState of TcpDiscoverySpi Mbean returns uppercased human-readable state, > e.g. 'CONNECTED' > getSpiState of ZookeeperDiscoverySpi Mbean returns camelcased one, e.g. > 'Connected' -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (IGNITE-10245) o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid SSL Cipher suite name specified
[ https://issues.apache.org/jira/browse/IGNITE-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10245: Fix Version/s: 2.8 > o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid > SSL Cipher suite name specified > - > > Key: IGNITE-10245 > URL: https://issues.apache.org/jira/browse/IGNITE-10245 > Project: Ignite > Issue Type: Task >Reporter: Alexey Kuznetsov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This issue is related to IGNITE-10189. > In case of invalid cipher suite name GridNioSslFilter failed with assertion > in org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter#sslHandler method. > Need to investigate and fix. > > See test: ClientSslParametersTest.testNonExistentCipherSuite() -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (IGNITE-10245) o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid SSL Cipher suite name specified
[ https://issues.apache.org/jira/browse/IGNITE-10245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-10245: --- Assignee: Ryabov Dmitrii > o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with Assertion if invalid > SSL Cipher suite name specified > - > > Key: IGNITE-10245 > URL: https://issues.apache.org/jira/browse/IGNITE-10245 > Project: Ignite > Issue Type: Task >Reporter: Alexey Kuznetsov >Assignee: Ryabov Dmitrii >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > This issue is related to IGNITE-10189. > In case of invalid cipher suite name GridNioSslFilter failed with assertion > in org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter#sslHandler method. > Need to investigate and fix. > > See test: ClientSslParametersTest.testNonExistentCipherSuite() -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
[ https://issues.apache.org/jira/browse/IGNITE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-11094: --- Assignee: Ryabov Dmitrii > Add SSL support for ignite zookeeper SPI > > > Key: IGNITE-11094 > URL: https://issues.apache.org/jira/browse/IGNITE-11094 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > > ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK > server connections if Zookeeper SPI used. > 1. > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (IGNITE-12049) Allow custom authenticators to use SSL certificates
[ https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-12049: --- Assignee: Ryabov Dmitrii > Allow custom authenticators to use SSL certificates > --- > > Key: IGNITE-12049 > URL: https://issues.apache.org/jira/browse/IGNITE-12049 > Project: Ignite > Issue Type: Improvement >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > > Add SSL certificates to AuthenticationContext, so, authenticators can make > additional checks based on SSL certificates. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12049) Allow custom authenticators to use SSL certificates
Ryabov Dmitrii created IGNITE-12049: --- Summary: Allow custom authenticators to use SSL certificates Key: IGNITE-12049 URL: https://issues.apache.org/jira/browse/IGNITE-12049 Project: Ignite Issue Type: Improvement Reporter: Ryabov Dmitrii Add SSL certificates to AuthenticationContext, so, authenticators can make additional checks based on SSL certificates. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11911) GridToStringBuilder allocates redundant memory
[
https://issues.apache.org/jira/browse/IGNITE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862987#comment-16862987
]
Ryabov Dmitrii commented on IGNITE-11911:
-
Looks good.
> GridToStringBuilder allocates redundant memory
> --
>
> Key: IGNITE-11911
> URL: https://issues.apache.org/jira/browse/IGNITE-11911
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A lot of classes in Ignite uses {{GridToStringBuilder}} to implement their
> {{toString()}} method. {{GridToStringBuilder}} uses thread local buffer to
> generate string representation. This buffer extended on demand but never
> shrank. On the final step {{GridToStringBuilder}} uses java {{StringBuilder}}
> class to produce output string and uses own buffer size as {{StringBuilder}}
> initial capacity. This leads to unnecessary memory allocation since we only
> need to allocate memory for meaningful data, but not for all buffer.
> Reproducer:
>
> {code:java}
> public void testSB() {
> GridToStringBuilder.toString(C1.class, new C1(1_000_000));
> GridToStringBuilder.toString(C1.class, new C1(100));
> }
> public class C1 {
> private String f;
> C1(int len) {
> f = new String(new char[len]);
> }
> }
> {code}
> Here on the second line about 1 million chars StringBuilder will be
> allocated, but only about 100 chars needed.
>
> Problem code (SBLimitedLength.java:293):
>
> {code:java}
> StringBuilder res = new StringBuilder(impl().capacity() + tailLen + 100);
> {code}
> Here {{length()}} method can be used instead of {{capacity()}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11571) Ignored critical failure
Ryabov Dmitrii created IGNITE-11571:
---
Summary: Ignored critical failure
Key: IGNITE-11571
URL: https://issues.apache.org/jira/browse/IGNITE-11571
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Ryabov Dmitrii
Critical failure in
{{TcpCommunicationSpiFaultyClientTest#testNotAcceptedConnection()}} is ignored
because of no-op failure handler.
{code:java}
[2019-03-19 15:09:18,970][WARN
][disco-event-worker-#237%tcp.TcpCommunicationSpiFaultyClientTest0%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=2d7a1e30-585f-44af-88af-60065ca2,
consistentId=2d7a1e30-585f-44af-88af-60065ca2, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:0], discPort=0, order=3, intOrder=3,
lastExchangeTime=1552997347220, loc=false, ver=2.7.0#20190319-sha1:,
isClient=true]
[2019-03-19 15:09:18,972][WARN ][tcp-disco-msg-worker-[9f201bd5
127.0.0.1:47500]-#36%tcp.TcpCommunicationSpiFaultyClientTest1%][TestTcpDiscoverySpi]
Received EVT_NODE_FAILED event with warning [nodeInitiatedEvt=TcpDiscoveryNode
[id=9f201bd5-f120-4365-8477-d9ff50e0, consistentId=127.0.0.1:47500,
addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1552997347060, loc=false,
ver=2.7.0#20190319-sha1:, isClient=false], msg=TcpCommunicationSpi
failed to establish connection to node [rmtNode=TcpDiscoveryNode
[id=2d7a1e30-585f-44af-88af-60065ca2,
consistentId=2d7a1e30-585f-44af-88af-60065ca2, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:0], discPort=0, order=3, intOrder=3,
lastExchangeTime=1552997347220, loc=false, ver=2.7.0#20190319-sha1:,
isClient=true], errs=class o.a.i.IgniteCheckedException: Failed to connect to
node (is node still alive?). Make sure that each ComputeTask and cache
Transaction has a timeout set in order to prevent parties from waiting forever
in case of network issues [nodeId=2d7a1e30-585f-44af-88af-60065ca2,
addrs=[/127.0.0.1:47200]], connectErrs=[]]]
[2019-03-19 15:09:18,973][WARN
][tcp-client-disco-msg-worker-#54%tcp.TcpCommunicationSpiFaultyClientTest3%][TestTcpDiscoverySpi]
Received EVT_NODE_FAILED event with warning [nodeInitiatedEvt=TcpDiscoveryNode
[id=9f201bd5-f120-4365-8477-d9ff50e0, consistentId=127.0.0.1:47500,
addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1552997347390, loc=false,
ver=2.7.0#20190319-sha1:, isClient=false], msg=TcpCommunicationSpi
failed to establish connection to node [rmtNode=TcpDiscoveryNode
[id=2d7a1e30-585f-44af-88af-60065ca2,
consistentId=2d7a1e30-585f-44af-88af-60065ca2, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:0], discPort=0, order=3, intOrder=3,
lastExchangeTime=1552997347220, loc=false, ver=2.7.0#20190319-sha1:,
isClient=true], errs=class o.a.i.IgniteCheckedException: Failed to connect to
node (is node still alive?). Make sure that each ComputeTask and cache
Transaction has a timeout set in order to prevent parties from waiting forever
in case of network issues [nodeId=2d7a1e30-585f-44af-88af-60065ca2,
addrs=[/127.0.0.1:47200]], connectErrs=[]]]
[2019-03-19 15:09:18,975][WARN
][disco-event-worker-#380%tcp.TcpCommunicationSpiFaultyClientTest3%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=2d7a1e30-585f-44af-88af-60065ca2,
consistentId=2d7a1e30-585f-44af-88af-60065ca2, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:0], discPort=0, order=3, intOrder=3,
lastExchangeTime=1552997347390, loc=false, ver=2.7.0#20190319-sha1:,
isClient=true]
[2019-03-19 15:09:18,975][INFO
][disco-event-worker-#380%tcp.TcpCommunicationSpiFaultyClientTest3%][GridDiscoveryManager]
Topology snapshot [ver=5, locNode=0f4451ab, servers=2, clients=1,
state=ACTIVE, CPUs=8, offheap=0.1GB, heap=3.5GB]
[2019-03-19
15:09:18,969][ERROR][sys-#240%tcp.TcpCommunicationSpiFaultyClientTest0%][TcpCommunicationSpiFaultyClientTest$TestCommunicationSpi]
Failed to send message to remote node [node=TcpDiscoveryNode
[id=2d7a1e30-585f-44af-88af-60065ca2,
consistentId=2d7a1e30-585f-44af-88af-60065ca2, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:0], discPort=0, order=3, intOrder=3,
lastExchangeTime=1552997347220, loc=false, ver=2.7.0#20190319-sha1:,
isClient=true], msg=GridIoMessage [plc=2, topic=TOPIC_CACHE, topicOrd=8,
ordered=false, timeout=0, skipOnTimeout=false, msg=GridDhtPartitionsFullMessage
[parts=HashMap {-2100569601=GridDhtPartitionFullMap
{9f201bd5-f120-4365-8477-d9ff50e0=GridDhtPartitionMap [moving=0,
top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=12, size=100],
7f025ffe-76b4-420e-b476-f6db8ff1=GridDhtPartitionMap [moving=0,
top=AffinityTopologyVersion [topVer=4, minorTopVer=1], updateSeq=109
[jira] [Created] (IGNITE-11562) Critical failure on stopping client node
Ryabov Dmitrii created IGNITE-11562:
---
Summary: Critical failure on stopping client node
Key: IGNITE-11562
URL: https://issues.apache.org/jira/browse/IGNITE-11562
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Ryabov Dmitrii
Critical failure in
{{IgniteAbstractDynamicCacheStartFailTest#testBrokenAffinityFunStartOnServerFailedOnClient()}}
is ignored because of no-op failure handler.
{code:java}
[2019-03-18
16:26:26,953][ERROR][exchange-worker-#210%clienttestBrokenAffinityFunStartOnServerFailedOnClient%][GridCachePartitionExchangeManager]
Failed to wait for completion of partition map exchange (preloading will not
start): GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryCustomEvent
[customMsg=null, affTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], topVer=4, nodeId8=7355a5c6, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1552915586506]], crd=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
discoEvt=DiscoveryCustomEvent [customMsg=null,
affTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=1],
super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=b9afbb48-3396-4ca6-b714-d2aa4e90,
consistentId=53086654-443a-44ab-88e3-a4d4f50d2477, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1552915586426, loc=false, ver=2.7.0#20190318-sha1:,
isClient=false], topVer=4, nodeId8=7355a5c6, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1552915586506]], nodeId=b9afbb48,
evt=DISCOVERY_CUSTOM_EVT], added=true, initFut=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=true, hash=731087400], init=true,
lastVer=null, partReleaseFut=null, exchActions=ExchangeActions
[startCaches=[TestDynamicCache-server-1], stopCaches=null,
startGrps=[TestDynamicCache-server-1], stopGrps=[], resetParts=null,
stateChangeRequest=null], affChangeMsg=null, initTs=1552915586506,
centralizedAff=false, forceAffReassignment=false, exchangeLocE=class
o.a.i.IgniteCheckedException: Failed to initialize exchange locally
[locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96],
cacheChangeFailureMsgSent=false, done=true, state=DONE,
registerCachesFuture=null, partitionsSent=false, partitionsReceived=false,
delayedLatestMsg=null, afterLsnrCompleteFut=GridFutureAdapter
[ignoreInterrupts=false, state=DONE, res=null, hash=1846768135],
timeBag=o.a.i.i.util.TimeBag@7682124a, startTime=20675138215608, evtLatch=0,
remaining=HashSet [7b53fbf7-537c-451a-b939-7099f492,
d63e4f5f-83b7-4449-8067-8d51bca1, b9afbb48-3396-4ca6-b714-d2aa4e90],
mergedJoinExchMsgs=null, super=GridFutureAdapter [ignoreInterrupts=false,
state=DONE, res=class o.a.i.IgniteCheckedException: Failed to initialize
exchange locally [locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96],
hash=1196794290]]
class org.apache.ignite.IgniteCheckedException: Failed to initialize exchange
locally [locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:782)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2920)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2769)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Simulated exception
[locNodeId=7355a5c6-5779-4d95-8508-c9a51f30fb96]
at
org.apache.ignite.internal.processors.cache.IgniteAbstractDynamicCacheStartFailTest$BrokenAffinityFunction.assignPartitions(IgniteAbstractDynamicCacheStartFailTest.java:920)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.calculate(GridAffinityAssignmentCache.java:369)
[jira] [Commented] (IGNITE-10963) Cache 2 suite hangs on CacheLockReleaseNodeLeaveTest#testLockNodeStop
[
https://issues.apache.org/jira/browse/IGNITE-10963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754900#comment-16754900
]
Ryabov Dmitrii commented on IGNITE-10963:
-
[~DmitriyGovorukhin], done.
> Cache 2 suite hangs on CacheLockReleaseNodeLeaveTest#testLockNodeStop
> -
>
> Key: IGNITE-10963
> URL: https://issues.apache.org/jira/browse/IGNITE-10963
> Project: Ignite
> Issue Type: Task
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Suite fails with timeout exception on
> {{CacheLockReleaseNodeLeaveTest#testLockNodeStop}} test.
> One node isn't finished and trying to send messages to left node.
> [Suite
> fails|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed],
> [build log with
> timeout|https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=2791865&_focus=44168].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-5580) Improve node failure cause information
[ https://issues.apache.org/jira/browse/IGNITE-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-5580: -- Assignee: (was: Ryabov Dmitrii) > Improve node failure cause information > -- > > Key: IGNITE-5580 > URL: https://issues.apache.org/jira/browse/IGNITE-5580 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Priority: Major > Labels: observability > Fix For: 2.8 > > > When a node fails, we do not print out any information about the root cause > of this failure. This makes it extremely hard to investigate the failure > causes - I need to find a previous node for the failed node and check the > logs on the previous node. > I suggest that we add extensive information about the reason of the node > failure and the sequence of events that led to this, e.g.: > [time] [NODE] Sending a message to next node - failed _because_ - write > timeout, read timeout, ...? > [time] [NODE] Connection check - failed - why? Connection refused, handshake > timed out, ...? > ... > [time] [NODE] Decided to drop the node because of the sequence above > Maybe we do not need to print out this information always, but we do need > this when troubleshooting logger is enabled. > Also, DiscoverySpi should collect a set of latest important events and dump > these events in case of local node segmentation. This will allow users to > match the events in the cluster and events on local node and get to the > bottom of the failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747764#comment-16747764
]
Ryabov Dmitrii edited comment on IGNITE-10978 at 1/21/19 9:05 AM:
--
[~kbolyandra], [~dpavlov], hello,
I think we should uncomment tests instead of removing. As I see, we have some
of these classes in the codebase, so, I propose to uncomment existing tests and
run [TeamCity|https://ci.ignite.apache.org/].
As for nonexisting tests - they could be renamed. Konstantin, please, find a
commit where they were removed or renamed.
was (Author: somefire):
[~kbolyandra], [~dpavlov], hello,
I think we should uncomment tests instead of removing. As I see, we have some
of these classes in the codebase, so, I propose to uncomment existing tests and
run [TeamCity|https://ci.ignite.apache.org/].
As for nonexisting tests - they could be renamed. Konstantin, please, find a
commit where they were removed or renamed?
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Konstantin Bolyandra
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10978) Remove unused tests marked with unclear todo
[
https://issues.apache.org/jira/browse/IGNITE-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747764#comment-16747764
]
Ryabov Dmitrii commented on IGNITE-10978:
-
[~kbolyandra], [~dpavlov], hello,
I think we should uncomment tests instead of removing. As I see, we have some
of these classes in the codebase, so, I propose to uncomment existing tests and
run [TeamCity|https://ci.ignite.apache.org/].
As for nonexisting tests - they could be renamed. Konstantin, please, find a
commit where they were removed or renamed?
> Remove unused tests marked with unclear todo
>
>
> Key: IGNITE-10978
> URL: https://issues.apache.org/jira/browse/IGNITE-10978
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Konstantin Bolyandra
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> IgniteCacheTestSuite3
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheDeploymentOffHeapValuesSelfTest.class,
> ignoredTests);
> IgniteCacheInterceptorSelfTestSuite
> // TODO GG-11141.
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
> ignoredTests);
> //
> GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
> ignoredTests);
> {noformat}
> Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10590) IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky
[ https://issues.apache.org/jira/browse/IGNITE-10590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10590: Description: Sometimes `expireTime` resets to 0 after node restart. [Test History|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4867852032903128088&tab=testDetails&branch_IgniteTests24Java8=]. was: Sometimes `expireTime` resets to 0 after node restart. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4867852032903128088&tab=testDetails&branch_IgniteTests24Java8= > IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky > -- > > Key: IGNITE-10590 > URL: https://issues.apache.org/jira/browse/IGNITE-10590 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Sometimes `expireTime` resets to 0 after node restart. > [Test > History|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4867852032903128088&tab=testDetails&branch_IgniteTests24Java8=]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10963) Cache 2 suite hangs on CacheLockReleaseNodeLeaveTest#testLockNodeStop
Ryabov Dmitrii created IGNITE-10963:
---
Summary: Cache 2 suite hangs on
CacheLockReleaseNodeLeaveTest#testLockNodeStop
Key: IGNITE-10963
URL: https://issues.apache.org/jira/browse/IGNITE-10963
Project: Ignite
Issue Type: Task
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
Suite fails with timeout exception on
{{CacheLockReleaseNodeLeaveTest#testLockNodeStop}} test.
One node isn't finished and trying to send messages to left node.
[Suite
fails|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache2&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E&state=failed],
[build log with
timeout|https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=2791865&_focus=44168].
--
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&focusedCommentId=16743775#comment-16743775 ] Ryabov Dmitrii commented on IGNITE-8227: [~dpavlov], I reworked failure handler, can you review [PR|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-1000]? > 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] [Commented] (IGNITE-6826) Change default DiscoverySpi ipFinder type for examples
[
https://issues.apache.org/jira/browse/IGNITE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741976#comment-16741976
]
Ryabov Dmitrii commented on IGNITE-6826:
[~avinogradov],
1. Reasons were discussed on devlist
([1|http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html],
[2|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-IGNITE-6826-forward-td32777.html],
[3|http://apache-ignite-developers.2346864.n4.nabble.com/Re-Pushing-forward-IGNITE-6826-Change-default-DiscoverySpi-ipFinder-type-for-examples-td32756.html]).
Summary:
* Multicast ipFinder adds some instability when several persons try & debug
samples or evaluate a new Ignite version at the same local network.
* Speedup for node start.
2. ExampleNodeStartup use the same configuration as examples, so it works as
usual.
See the master branch: {{ExampleNodeStartup}} and {{ignite.bat/sh}} are
*incompatible* because ignite.bat/sh uses default IgniteConfiguration with
disabled peer class loading, but ExampleNodeStartup uses configuration with
enabled peer class loading.
3. I assemled release version asa described in DEVNOTES.txt and checked some
examples manually. They work normally with nodes started by ExampleNodeStartup.
> Change default DiscoverySpi ipFinder type for examples
> --
>
> Key: IGNITE-6826
> URL: https://issues.apache.org/jira/browse/IGNITE-6826
> Project: Ignite
> Issue Type: Improvement
> Components: examples
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Ryabov Dmitrii
>Priority: Major
> Labels: newbie
> Fix For: 2.8
>
>
> It is better to change multicast ipFinder to static (vm) ipFinder for java
> examples, .NET examples and C++ examples.
> http://apache-ignite-developers.2346864.n4.nabble.com/ipFinder-configuration-for-Samples-td23818.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10811) Add new TC build-config to test Service Grid new and old implementations
[ https://issues.apache.org/jira/browse/IGNITE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730114#comment-16730114 ] Ryabov Dmitrii commented on IGNITE-10811: - Tests looks good, no test is lost. [~NIzhikov], let's merge! > Add new TC build-config to test Service Grid new and old implementations > > > Key: IGNITE-10811 > URL: https://issues.apache.org/jira/browse/IGNITE-10811 > Project: Ignite > Issue Type: Task > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-17 > Fix For: 2.8 > > > It's necessary to add new build configuration on TeamCity (after merge > IGNITE-9607) to have ability testing new and old implementations of the > service processor. > In general, new build plan should contain 2 test suites: > 1) To place Service Grid related tests which *do not depend on* service > processor's implementation (like classic unit tests) and *should be executed > once*; > 2) To place Service Grid related tests which *depend* *on* service > processor's implementation and *should be executed twice* in the new mode and > old mode (-DIGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED=false) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10805) [TC Bot] Gather info from investigations for page with muted tests
Ryabov Dmitrii created IGNITE-10805: --- Summary: [TC Bot] Gather info from investigations for page with muted tests Key: IGNITE-10805 URL: https://issues.apache.org/jira/browse/IGNITE-10805 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Some mutes have no ticket in the description [1], but its investigations [2] could have it. 1. We should periodically gather investigations like mutes and save them in a separate cache. 2. We should combine mutes and investigations before sending as response for mutes page. For this, we need to separate mutes to keep at most one test (e.g. send 7 mutes with 1 test in each instead of 1 mute with 7 tests). [1] https://ci.ignite.apache.org/app/rest/mutes/id:6626 [2] https://ci.ignite.apache.org/app/rest/investigations/test:(id:1284555489623943735),assignmentProject:(id:IgniteTests24Java8) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10593) Proper NoOpHandler injection
Ryabov Dmitrii created IGNITE-10593: --- Summary: Proper NoOpHandler injection Key: IGNITE-10593 URL: https://issues.apache.org/jira/browse/IGNITE-10593 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Fix For: 2.8 Improve no-op failure handler usage by replacing copy-pasted code by extending from class with changed default handler as recommended in [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Default-failure-handler-was-changed-for-tests-tp38900p39010.html]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10590) IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky
[ https://issues.apache.org/jira/browse/IGNITE-10590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10590: Fix Version/s: 2.8 > IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky > -- > > Key: IGNITE-10590 > URL: https://issues.apache.org/jira/browse/IGNITE-10590 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > Sometimes `expireTime` resets to 0 after node restart. > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4867852032903128088&tab=testDetails&branch_IgniteTests24Java8= -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10590) IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky
Ryabov Dmitrii created IGNITE-10590: --- Summary: IgnitePersistentStoreCacheGroupsTest.testExpiryPolicy is flaky Key: IGNITE-10590 URL: https://issues.apache.org/jira/browse/IGNITE-10590 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Sometimes `expireTime` resets to 0 after node restart. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4867852032903128088&tab=testDetails&branch_IgniteTests24Java8= -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10568) [TC Bot] Replace type for test id from long to String
[ https://issues.apache.org/jira/browse/IGNITE-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10568: Summary: [TC Bot] Replace type for test id from long to String (was: [TC Bot] Replace type for test id from long by String) > [TC Bot] Replace type for test id from long to String > - > > Key: IGNITE-10568 > URL: https://issues.apache.org/jira/browse/IGNITE-10568 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Trivial > > JS long type have less bits for long numbers, so we loose last digits of the > number. > We should use string instead of long for requests, but keep long for cached > objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10568) [TC Bot] Replace type for test id from long by String
Ryabov Dmitrii created IGNITE-10568: --- Summary: [TC Bot] Replace type for test id from long by String Key: IGNITE-10568 URL: https://issues.apache.org/jira/browse/IGNITE-10568 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii JS long type have less bits for long numbers, so we loose last digits of the number. We should use string instead of long for requests, but keep long for cached objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708918#comment-16708918
]
Ryabov Dmitrii commented on IGNITE-10437:
-
[~ilantukh], I made loop as you suggested. Tests are ok.
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707196#comment-16707196
]
Ryabov Dmitrii commented on IGNITE-10437:
-
Good idea, I'll do it.
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707140#comment-16707140
]
Ryabov Dmitrii commented on IGNITE-10437:
-
[~ilantukh], I suppose because of delay, threads worked separately, one by one.
With high delay there was more often situations when overflow doesn't happened.
With lower delay overflow happened is more often, but test still was flaky. So,
I removed delay to be sure that overflow is happened.
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8903) IgniteCacheGetRestartTest.testGetRestartReplicated fails in master
[
https://issues.apache.org/jira/browse/IGNITE-8903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii resolved IGNITE-8903.
Resolution: Duplicate
Fix Version/s: 2.8
I agree. Test don't fails anymore.
> IgniteCacheGetRestartTest.testGetRestartReplicated fails in master
> --
>
> Key: IGNITE-8903
> URL: https://issues.apache.org/jira/browse/IGNITE-8903
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Maxim Muzafarov
>Assignee: Ruslan Gilemzyanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, newbie
> Fix For: 2.8
>
>
> Test {{IgniteCacheGetRestartTest.testGetRestartReplicated}} fails with
> message:
> {code:java}
> org.apache.ignite.IgniteCheckedException: Ignite instance with this name has
> already been started: distributed.IgniteCacheGetRestartTest5{code}
> Probably some grids remains not stopped between test-cases within
> IgniteCacheGetRestartTest.
>
> TC (master):
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7917326378982816549&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702831#comment-16702831
]
Ryabov Dmitrii commented on IGNITE-10437:
-
Inspections were fixed in 2418d87.
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10454) [TC Bot] Create page with muted tests
Ryabov Dmitrii created IGNITE-10454: --- Summary: [TC Bot] Create page with muted tests Key: IGNITE-10454 URL: https://issues.apache.org/jira/browse/IGNITE-10454 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii We need a page with muted tests. On this page we should have possibility to filter tests by fail reason (fail with ticket link or not) and fail rate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-10437:
Labels: MakeTeamcityGreenAgain (was: )
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
[
https://issues.apache.org/jira/browse/IGNITE-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-10437:
Fix Version/s: 2.8
> GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
> is flaky
>
>
> Key: IGNITE-10437
> URL: https://issues.apache.org/jira/browse/IGNITE-10437
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Fails periodically on
> [TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
> {code:java}
> junit.framework.AssertionFailedError: No cache overflows detected (a bug or
> too few keys or too few delay?)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
> at
> org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
> 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.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10437) GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing is flaky
Ryabov Dmitrii created IGNITE-10437:
---
Summary:
GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing
is flaky
Key: IGNITE-10437
URL: https://issues.apache.org/jira/browse/IGNITE-10437
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
Fails periodically on
[TeamCity|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-2991182438861864832&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E].
{code:java}
junit.framework.AssertionFailedError: No cache overflows detected (a bug or too
few keys or too few delay?)
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThread(GridCacheWriteBehindStoreMultithreadedSelfTest.java:215)
at
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStoreMultithreadedSelfTest.testFlushFromTheSameThreadWithCoalescing(GridCacheWriteBehindStoreMultithreadedSelfTest.java:166)
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.access$001(GridAbstractTest.java:150)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10375) Fix inspection failures
[ https://issues.apache.org/jira/browse/IGNITE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10375: Labels: MakeTeamcityGreenAgain (was: ) > Fix inspection failures > --- > > Key: IGNITE-10375 > URL: https://issues.apache.org/jira/browse/IGNITE-10375 > Project: Ignite > Issue Type: Bug >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > 4 failures in the master > https://ci.ignite.apache.org/viewLog.html?buildId=2376109&buildTypeId=IgniteTests24Java8_InspectionsCore&tab=Inspection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10375) Fix inspection failures
[ https://issues.apache.org/jira/browse/IGNITE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii updated IGNITE-10375: Fix Version/s: 2.8 > Fix inspection failures > --- > > Key: IGNITE-10375 > URL: https://issues.apache.org/jira/browse/IGNITE-10375 > Project: Ignite > Issue Type: Bug >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > > 4 failures in the master > https://ci.ignite.apache.org/viewLog.html?buildId=2376109&buildTypeId=IgniteTests24Java8_InspectionsCore&tab=Inspection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10375) Fix inspection failures
Ryabov Dmitrii created IGNITE-10375: --- Summary: Fix inspection failures Key: IGNITE-10375 URL: https://issues.apache.org/jira/browse/IGNITE-10375 Project: Ignite Issue Type: Bug Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii 4 failures in the master https://ci.ignite.apache.org/viewLog.html?buildId=2376109&buildTypeId=IgniteTests24Java8_InspectionsCore&tab=Inspection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10184) Missed TODO: IGNITE-5380 uncomment after fix
[
https://issues.apache.org/jira/browse/IGNITE-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690888#comment-16690888
]
Ryabov Dmitrii commented on IGNITE-10184:
-
Inspections failure was fixed in
[IGNITE-10237|https://github.com/apache/ignite/pull/5378/files].
[~aliskhakov], move ticket to Patch Available status.
[~dpavlov], test is succesfully finished on TC. Can you merge PR?
> Missed TODO: IGNITE-5380 uncomment after fix
>
>
> Key: IGNITE-10184
> URL: https://issues.apache.org/jira/browse/IGNITE-10184
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Albert Iskhakov
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8
>
>
> Ticket is resolved, so test
> {{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed
> (remove "\_" symbol) and fixed - this test should check that second cache
> creation throws exception about conflict in the schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10301) GridToStringBuilder is broken for classes with inheritance
[
https://issues.apache.org/jira/browse/IGNITE-10301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii reassigned IGNITE-10301:
---
Assignee: Ryabov Dmitrii
> GridToStringBuilder is broken for classes with inheritance
> --
>
> Key: IGNITE-10301
> URL: https://issues.apache.org/jira/browse/IGNITE-10301
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Alexey Goncharuk
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.7
>
>
> Given the following class hierarchy
> {code}
> /** */
> private static class Parent {
> /** */
> private int a;
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Parent.class, this);
> }
> }
> /** */
> private static class Child extends Parent {
> /** */
> private int b;
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Child.class, this, super.toString());
> }
> }
> private static class Wrapper {
> /** */
> @GridToStringInclude
> Parent p = new Child();
> /** {@inheritDoc} */
> @Override public String toString() {
> return S.toString(Wrapper.class, this);
> }
> }
> {code}
> the next test fails:
> {code}
> /**
> */
> public void testHierarchy() {
> Wrapper w = new Wrapper();
> Parent p = w.p;
> String wS = w.toString();
> String pS = p.toString();
> // Expect wS to be "Wrapper [p=" + pS + ']'.
> assertEquals("Wrapper [p=" + pS + ']', wS);
> }
> {code}
> {code}
> Expected :Wrapper [p=Child [b=0, super=Parent [a=0]]]
> Actual :Wrapper [p=Parent [a=0]Child [b=0, super=]]
> {code}
> This is a regression from IGNITE-602. We need to fix this in 2.7 or revert
> IGNITE-602.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10188) Move tests with persistence to the convenient suite
[
https://issues.apache.org/jira/browse/IGNITE-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681156#comment-16681156
]
Ryabov Dmitrii commented on IGNITE-10188:
-
[~EdShangGG], ok, should I remove public static field with this property too?
> Move tests with persistence to the convenient suite
> ---
>
> Key: IGNITE-10188
> URL: https://issues.apache.org/jira/browse/IGNITE-10188
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> Tests with persistence from {{IgniteCachePartitionLossPolicySelfTest}} must
> be moved to another class and suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (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:all-tabpanel ] Ryabov Dmitrii reassigned IGNITE-8227: -- Assignee: Ryabov Dmitrii (was: Dmitriy Pavlov) > 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 > Fix For: 2.8 > > > 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] [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&focusedCommentId=16681044#comment-16681044 ] Ryabov Dmitrii commented on IGNITE-8227: [~dpavlov], I made handler, which stops the node and fails the test. Can you look it? I set no-op handler for tests with node restarts and for tests, where we check failure cases. Also, failure handler works only when test is running, so critical failures happened on node start/end outside of the test don't affect the test. > 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: Dmitriy Pavlov >Priority: Major > Fix For: 2.8 > > > 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] [Commented] (IGNITE-10188) Move tests with persistence to the convenient suite
[
https://issues.apache.org/jira/browse/IGNITE-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681003#comment-16681003
]
Ryabov Dmitrii commented on IGNITE-10188:
-
[~EdShangGG], I made as you suggested, [{{Cache 5}} suite is finished
successfully|https://ci.ignite.apache.org/viewLog.html?buildId=2273604&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache5].
> Move tests with persistence to the convenient suite
> ---
>
> Key: IGNITE-10188
> URL: https://issues.apache.org/jira/browse/IGNITE-10188
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Major
>
> Tests with persistence from {{IgniteCachePartitionLossPolicySelfTest}} must
> be moved to another class and suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10184) Missed TODO: IGNITE-5380 uncomment after fix
Ryabov Dmitrii created IGNITE-10184:
---
Summary: Missed TODO: IGNITE-5380 uncomment after fix
Key: IGNITE-10184
URL: https://issues.apache.org/jira/browse/IGNITE-10184
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Ticket is resolved, so test
{{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed (remove
"_") and fixed - this test should check that second cache creation throws
exception about conflict in the schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10190) [TC Bot] Failed tests don't count as blockers if they were created in the PR
Ryabov Dmitrii created IGNITE-10190: --- Summary: [TC Bot] Failed tests don't count as blockers if they were created in the PR Key: IGNITE-10190 URL: https://issues.apache.org/jira/browse/IGNITE-10190 Project: Ignite Issue Type: Bug Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Failed tests don't count as blockers if they were created in the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10188) Move tests with persistence to the convenient suite
Ryabov Dmitrii created IGNITE-10188:
---
Summary: Move tests with persistence to the convenient suite
Key: IGNITE-10188
URL: https://issues.apache.org/jira/browse/IGNITE-10188
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
Tests with persistence from {{IgniteCachePartitionLossPolicySelfTest}} must be
moved to another class and suite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10184) Missed TODO: IGNITE-5380 uncomment after fix
[
https://issues.apache.org/jira/browse/IGNITE-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-10184:
Fix Version/s: 2.8
> Missed TODO: IGNITE-5380 uncomment after fix
>
>
> Key: IGNITE-10184
> URL: https://issues.apache.org/jira/browse/IGNITE-10184
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Priority: Trivial
> Labels: newbie
> Fix For: 2.8
>
>
> Ticket is resolved, so test
> {{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed
> (remove "\_" symbol) and fixed - this test should check that second cache
> creation throws exception about conflict in the schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10184) Missed TODO: IGNITE-5380 uncomment after fix
[
https://issues.apache.org/jira/browse/IGNITE-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-10184:
Description: Ticket is resolved, so test
{{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed (remove
"\_") and fixed - this test should check that second cache creation throws
exception about conflict in the schema. (was: Ticket is resolved, so test
{{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed (remove
"_") and fixed - this test should check that second cache creation throws
exception about conflict in the schema.)
> Missed TODO: IGNITE-5380 uncomment after fix
>
>
> Key: IGNITE-10184
> URL: https://issues.apache.org/jira/browse/IGNITE-10184
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Priority: Trivial
> Labels: newbie
>
> Ticket is resolved, so test
> {{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed
> (remove "\_") and fixed - this test should check that second cache creation
> throws exception about conflict in the schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10184) Missed TODO: IGNITE-5380 uncomment after fix
[
https://issues.apache.org/jira/browse/IGNITE-10184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryabov Dmitrii updated IGNITE-10184:
Description: Ticket is resolved, so test
{{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed (remove
"\_" symbol) and fixed - this test should check that second cache creation
throws exception about conflict in the schema. (was: Ticket is resolved, so
test {{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed
(remove "\_") and fixed - this test should check that second cache creation
throws exception about conflict in the schema.)
> Missed TODO: IGNITE-5380 uncomment after fix
>
>
> Key: IGNITE-10184
> URL: https://issues.apache.org/jira/browse/IGNITE-10184
> Project: Ignite
> Issue Type: Test
>Reporter: Ryabov Dmitrii
>Priority: Trivial
> Labels: newbie
>
> Ticket is resolved, so test
> {{SqlSchemaSelfTest._testTypeConflictInPublicSchema}} should be renamed
> (remove "\_" symbol) and fixed - this test should check that second cache
> creation throws exception about conflict in the schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10150) DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
[
https://issues.apache.org/jira/browse/IGNITE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678041#comment-16678041
]
Ryabov Dmitrii commented on IGNITE-10150:
-
Hello, Stanislav! Test will succesfully finished if the exception is not
thrown, please, fix test to ensure that exception was thrown.
> DisappearedCacheWasNotFoundMessageSelfTest fails with NPE
> -
>
> Key: IGNITE-10150
> URL: https://issues.apache.org/jira/browse/IGNITE-10150
> Project: Ignite
> Issue Type: Bug
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.8
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2226328&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Queries2
> {code}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.nodesForPartitions(GridReduceQueryExecutor.java:1702)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:690)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1801)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$9.iterator(IgniteH2Indexing.java:1869)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.DisappearedCacheWasNotFoundMessageSelfTest.testDisappearedCacheWasNotFoundMessage(DisappearedCacheWasNotFoundMessageSelfTest.java:59)
> 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:2206)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2121)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
