[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] [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] [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] [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] [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] [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] [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],
[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] [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=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E=failed],
[build log with
timeout|https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=2791865&_focus=44168].
--
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] [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=4867852032903128088=testDetails_IgniteTests24Java8= -- 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] [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] [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=-2991182438861864832=testDetails_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-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=IgniteTests24Java8_InspectionsCore=Inspection -- 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] [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-10127) GridCacheRebalancingSyncSelfTest ignores check result
Ryabov Dmitrii created IGNITE-10127:
---
Summary: GridCacheRebalancingSyncSelfTest ignores check result
Key: IGNITE-10127
URL: https://issues.apache.org/jira/browse/IGNITE-10127
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Fix For: 2.8
{{checkSupplyContextMapIsEmpty()}} method checks that map is empty, but ignores
result of this check.
{code:java}
GridTestUtils.waitForCondition(new PA() {
@Override public boolean apply() {
synchronized (map) {
return map.isEmpty();
}
}
}, 15_000);
{code}
We should check that {{waitForCondition()}} returns true to be sure that map is
cleared.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10091) [TC Bot] Replace PR source for autocompleting branch fields
Ryabov Dmitrii created IGNITE-10091: --- Summary: [TC Bot] Replace PR source for autocompleting branch fields Key: IGNITE-10091 URL: https://issues.apache.org/jira/browse/IGNITE-10091 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Currently, client receive PRs info for autocompletion list separately from the server. Instead, we should get this info from the Bot, because it is cached here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9986) TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished is flaky
Ryabov Dmitrii created IGNITE-9986: -- Summary: TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished is flaky Key: IGNITE-9986 URL: https://issues.apache.org/jira/browse/IGNITE-9986 Project: Ignite Issue Type: Bug Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Fails: https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-6988766947783986136=TEST_STATUS_DESC=50_IgniteTests24Java8= -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9961) GridMessageListenSelfTest#testNullTopic() duplicates #testNonNullTopic()
Ryabov Dmitrii created IGNITE-9961:
--
Summary: GridMessageListenSelfTest#testNullTopic() duplicates
#testNonNullTopic()
Key: IGNITE-9961
URL: https://issues.apache.org/jira/browse/IGNITE-9961
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Assignee: Ryabov Dmitrii
Currently, the test {{GridMessageListenSelfTest.testNonNullTopic()}} has the
same code as {{GridMessageListenSelfTest.testNullTopic()}}, and thus, testing
the same thing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9769) Replace sleep by fut.get() in the IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 test
Ryabov Dmitrii created IGNITE-9769: -- Summary: Replace sleep by fut.get() in the IgniteCacheAtomicProtocolTest.testPutReaderUpdate1 test Key: IGNITE-9769 URL: https://issues.apache.org/jira/browse/IGNITE-9769 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Replace sleep with fut.get(getTestTimeout()) to gather statistics. If test is flaky because 2 seconds isn't enough and test needs a bit more time - it's ok. If test really hangs - we should investigate the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9697) [TC Bot] Autocomplete branch for TC field
Ryabov Dmitrii created IGNITE-9697: -- Summary: [TC Bot] Autocomplete branch for TC field Key: IGNITE-9697 URL: https://issues.apache.org/jira/browse/IGNITE-9697 Project: Ignite Issue Type: Bug Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Get last updated PRs from GitHub and use them to autocomplete branch for TC fields. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9668) Comment JIRA from pr.html
Ryabov Dmitrii created IGNITE-9668: -- Summary: Comment JIRA from pr.html Key: IGNITE-9668 URL: https://issues.apache.org/jira/browse/IGNITE-9668 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Show button to comment Jira ticket on the pr.html page. If ticket can't be detected automatically, then ticket should be gained from user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9643) [TC Bot] update cwiki
Ryabov Dmitrii created IGNITE-9643: -- Summary: [TC Bot] update cwiki Key: IGNITE-9643 URL: https://issues.apache.org/jira/browse/IGNITE-9643 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii We need to update [wiki page|https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot] with latest changes and new implemented features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9617) Different input possibilities for services page
Ryabov Dmitrii created IGNITE-9617: -- Summary: Different input possibilities for services page Key: IGNITE-9617 URL: https://issues.apache.org/jira/browse/IGNITE-9617 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii We should improve usability. Currently branch field requieres full TeamCity branch name like on index page. It should accept PR number too. Same about JIRA ticket field. It should accept "IGNITE-XXX" and number only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9588) Separate page for JIRA, GitHub actions
Ryabov Dmitrii created IGNITE-9588: -- Summary: Separate page for JIRA, GitHub actions Key: IGNITE-9588 URL: https://issues.apache.org/jira/browse/IGNITE-9588 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii To separate JIRA and GitHub actions from other action on index page we need to create an additional page, opened by tab on the panel with Home and Compare Builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9378) Automatical print of critical failures in the PR after Run All
Ryabov Dmitrii created IGNITE-9378: -- Summary: Automatical print of critical failures in the PR after Run All Key: IGNITE-9378 URL: https://issues.apache.org/jira/browse/IGNITE-9378 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Replace button by webhook for TeamCity (for Run All), which will start analysis on TCH and write results in the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9377) Handle print critical failures to the PR
Ryabov Dmitrii created IGNITE-9377: -- Summary: Handle print critical failures to the PR Key: IGNITE-9377 URL: https://issues.apache.org/jira/browse/IGNITE-9377 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Create a button by clicking on which the info about critical failures will be written in the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9376) Create table with critical failures
Ryabov Dmitrii created IGNITE-9376: -- Summary: Create table with critical failures Key: IGNITE-9376 URL: https://issues.apache.org/jira/browse/IGNITE-9376 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Create separate table for critical failures (suite timouts, suite non-zero exit codes, etc) and new tests (failure rate 0.0%) on the PR analysis page of TCH. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9375) [TC Bot] Highlight critical failures in the PR
Ryabov Dmitrii created IGNITE-9375: -- Summary: [TC Bot] Highlight critical failures in the PR Key: IGNITE-9375 URL: https://issues.apache.org/jira/browse/IGNITE-9375 Project: Ignite Issue Type: Improvement Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Show table with critical failures (suite timouts, suite non-zero exit codes, etc) and new tests (failure rate 0.0%) in the GitHub's PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9209) GridDistributedTxMapping.toString() returns broken string
Ryabov Dmitrii created IGNITE-9209:
--
Summary: GridDistributedTxMapping.toString() returns broken string
Key: IGNITE-9209
URL: https://issues.apache.org/jira/browse/IGNITE-9209
Project: Ignite
Issue Type: Bug
Reporter: Ryabov Dmitrii
Something wrong with `GridDistributedTxMapping` when we try to get string
representation by `GridToStringBuilder`.
It should looks like
{noformat}
GridDistributedTxMapping [entries=LinkedHashSet [/*values here*/],
explicitLock=false, dhtVer=null, last=false, nearEntries=0, clientFirst=false,
node=cd268979-ccf2-4a4c-bfbb-f8406060]
{noformat}
But currently it looks like
{noformat}
KeyCacheObjectImpl [part=1, val=1, hasValBytes=false]KeyCacheObjectImpl
[part=1, val=1, hasValBytes=false],// more text
{noformat}
Reproducer:
{code:java}
public class GridToStringBuilderSelfTest extends GridCommonAbstractTest {
/**
* @throws Exception
*/
public void testGridDistributedTxMapping() throws Exception {
IgniteEx ignite = startGrid(0);
IgniteCache cache =
ignite.createCache(defaultCacheConfiguration());
try (Transaction tx = ignite.transactions().txStart()) {
cache.put(1, 1);
GridDistributedTxMapping mapping = new
GridDistributedTxMapping(grid(0).localNode());
assertTrue("Wrong string: " + mapping,
mapping.toString().startsWith("GridDistributedTxMapping ["));
mapping.add(((TransactionProxyImpl)tx).tx().txState().allEntries().stream().findAny().get());
assertTrue("Wrong string: " + mapping,
mapping.toString().startsWith("GridDistributedTxMapping ["));
}
stopAllGrids();
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9110) Tx commit hangs after cross-cache operations with LOCAL cache
Ryabov Dmitrii created IGNITE-9110:
--
Summary: Tx commit hangs after cross-cache operations with LOCAL
cache
Key: IGNITE-9110
URL: https://issues.apache.org/jira/browse/IGNITE-9110
Project: Ignite
Issue Type: Task
Components: cache
Reporter: Ryabov Dmitrii
Commit hangs when tx contains operations on LOCAL and PARTITIONED or REPLICATED
caches in some cases. Example:
{code:java}
public class LocalCacheFails extends GridCommonAbstractTest {
/** */
public void testLocalCache() throws Exception {
IgniteEx ignite = startGrid(0);
IgniteCache locCache =
ignite.createCache(getConfig(LOCAL));
IgniteCache partCache =
ignite.createCache(getConfig(PARTITIONED));
try (Transaction tx = ignite.transactions().txStart(OPTIMISTIC,
SERIALIZABLE)) {
locCache.put(1, 1);
partCache.put(1, 1);
tx.commit(); // Fails here.
}
}
/** */
private CacheConfiguration getConfig(CacheMode cacheMode)
{
CacheConfiguration cfg = new CacheConfiguration<>();
cfg.setCacheMode(cacheMode);
cfg.setName(cacheMode.name());
cfg.setAtomicityMode(TRANSACTIONAL);
return cfg;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8801) Change default behaviour of atomic operations inside transactions
Ryabov Dmitrii created IGNITE-8801: -- Summary: Change default behaviour of atomic operations inside transactions Key: IGNITE-8801 URL: https://issues.apache.org/jira/browse/IGNITE-8801 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Fix For: 3.0 Need to change default behaviour of atomic operations to fail inside transactions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-5748) Extend JTA test coverage
Ryabov Dmitrii created IGNITE-5748:
--
Summary: Extend JTA test coverage
Key: IGNITE-5748
URL: https://issues.apache.org/jira/browse/IGNITE-5748
Project: Ignite
Issue Type: Test
Reporter: Ryabov Dmitrii
Priority: Minor
The goal is to have every method of CacheJtaResource called inside tests.
Please add tests that will enlist fake XA resources to transaction (to the one
enlisted for proper cache tx). You can use this snippet:
{code:java}
jotm.getTransactionManager().getTransaction().enlistResource(new XAResource()
{.. });
{code}
We need to do this because with only one resource transaction manager calls
commit() without calling prepare(). Therefore, a lot of code is not covered
with tests. Please add them and add invocations counters and asserts for them.
[Task
source.|https://issues.apache.org/jira/browse/IGNITE-4648?focusedCommentId=16085532=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16085532]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
