[jira] [Assigned] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11591:
---
Assignee: (was: Andrey Kalinin)
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11957) IdleVerify command should print end time of execution.
[ https://issues.apache.org/jira/browse/IGNITE-11957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-11957: Reviewer: Dmitriy Govorukhin (was: Stanilovsky Evgeny) > IdleVerify command should print end time of execution. > -- > > Key: IGNITE-11957 > URL: https://issues.apache.org/jira/browse/IGNITE-11957 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11957) IdleVerify command should print end time of execution.
[ https://issues.apache.org/jira/browse/IGNITE-11957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-11957: Ignite Flags: (was: Docs Required) > IdleVerify command should print end time of execution. > -- > > Key: IGNITE-11957 > URL: https://issues.apache.org/jira/browse/IGNITE-11957 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11957) IdleVerify command should print end time of execution.
[ https://issues.apache.org/jira/browse/IGNITE-11957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877690#comment-16877690 ] Andrey Kalinin commented on IGNITE-11957: - [~zstan], please, review. > IdleVerify command should print end time of execution. > -- > > Key: IGNITE-11957 > URL: https://issues.apache.org/jira/browse/IGNITE-11957 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11957) IdleVerify command should print end time of execution.
[ https://issues.apache.org/jira/browse/IGNITE-11957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-11957: Reviewer: Stanilovsky Evgeny > IdleVerify command should print end time of execution. > -- > > Key: IGNITE-11957 > URL: https://issues.apache.org/jira/browse/IGNITE-11957 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9934) Improve logging on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9934: --- Reviewer: Dmitriy Govorukhin (was: Stanilovsky Evgeny) > Improve logging on partition map exchange > - > > Key: IGNITE-9934 > URL: https://issues.apache.org/jira/browse/IGNITE-9934 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Partition Map Exchange (PME) is a cluster wide process, be the reason it does > not completed before then each node do not done its part of job. > Coordinator, as a not witch managed the process, can to print quantity nodes > finished its stage of PME and other than, which not yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9934) Improve logging on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877670#comment-16877670 ] Andrey Kalinin commented on IGNITE-9934: [~DmitriyGovorukhin], plese review. > Improve logging on partition map exchange > - > > Key: IGNITE-9934 > URL: https://issues.apache.org/jira/browse/IGNITE-9934 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Partition Map Exchange (PME) is a cluster wide process, be the reason it does > not completed before then each node do not done its part of job. > Coordinator, as a not witch managed the process, can to print quantity nodes > finished its stage of PME and other than, which not yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9934) Improve logging on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877635#comment-16877635 ] Andrey Kalinin commented on IGNITE-9934: [~zstan], please review > Improve logging on partition map exchange > - > > Key: IGNITE-9934 > URL: https://issues.apache.org/jira/browse/IGNITE-9934 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Partition Map Exchange (PME) is a cluster wide process, be the reason it does > not completed before then each node do not done its part of job. > Coordinator, as a not witch managed the process, can to print quantity nodes > finished its stage of PME and other than, which not yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9934) Improve logging on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9934: --- Reviewer: Stanilovsky Evgeny > Improve logging on partition map exchange > - > > Key: IGNITE-9934 > URL: https://issues.apache.org/jira/browse/IGNITE-9934 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Partition Map Exchange (PME) is a cluster wide process, be the reason it does > not completed before then each node do not done its part of job. > Coordinator, as a not witch managed the process, can to print quantity nodes > finished its stage of PME and other than, which not yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11957) IdleVerify command should print end time of execution.
Andrey Kalinin created IGNITE-11957: --- Summary: IdleVerify command should print end time of execution. Key: IGNITE-11957 URL: https://issues.apache.org/jira/browse/IGNITE-11957 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin Assignee: Andrey Kalinin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874166#comment-16874166 ] Andrey Kalinin commented on IGNITE-11844: - [~sergey-chugunov], just fix it. Please, check again. > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-11844: Reviewer: Dmitriy Govorukhin (was: Alexey Goncharuk) > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-11844: Reviewer: Alexey Goncharuk > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857434#comment-16857434 ] Andrey Kalinin commented on IGNITE-11844: - [~v.pyatkov]. Please review again. > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856576#comment-16856576 ] Andrey Kalinin commented on IGNITE-11844: - [~v.pyatkov], looks reasonable. Fixed. > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856550#comment-16856550 ] Andrey Kalinin commented on IGNITE-11844: - [~v.pyatkov] please review. > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11844) Should to filtered indexes by cache name instead of validate all caches in group
[ https://issues.apache.org/jira/browse/IGNITE-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11844: --- Assignee: Andrey Kalinin > Should to filtered indexes by cache name instead of validate all caches in > group > > > Key: IGNITE-11844 > URL: https://issues.apache.org/jira/browse/IGNITE-11844 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > > control.sh utility method validate_indexes checks all indexes of all caches > in group. Just do specify one caches (from generic group) in caches list, > then all indexes from all caches (that group) will be start to validate and > this can consume more time, than checks indexes only specified caches. > Will be correct to validate only indexes of specified caches, for the purpose > need to filtered caches, by list from parameters, in shared group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11812) control.sh ignores quotes in passed arguments
[
https://issues.apache.org/jira/browse/IGNITE-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin resolved IGNITE-11812.
-
Resolution: Not A Problem
Fix Version/s: (was: 2.8)
This problem cannot be reproduced in real-world situations. Commas in
consistentId are only found on older versions of Ignite when persistence is
disabled.
> control.sh ignores quotes in passed arguments
> -
>
> Key: IGNITE-11812
> URL: https://issues.apache.org/jira/browse/IGNITE-11812
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Andrey Kalinin
>Priority: Major
>
> Control.sh should consider quotes in incoming arguments. i.e. I expect that
> {code:java}
> control.sh --baseline set "p1,p2,p3","p4,p5,p6" --yes
> {code}
> set BLT with two nodes with consistent ids: {{p1,p2,p3}} and {{p4,p5,p6}},
> but now it tries to set BLT with six nodes {{p1}}, {{p2}}, {{p3}}, {{p4}},
> {{p5}}, {{p6}}
> Reproducer. (Add this test to {{CommandHandlerParsingTest}})
> {code:java}
> @Test
> public void testQuotesWillNotIgnored() throws Exception {
> CommandHandler hnd = new CommandHandler();
> Arguments args = hnd.parseAndValidate(
> Arrays.asList(
> BASELINE.text(),
> BaselineCommand.SET.text(),
> "\"1,2,3\",\"3,2,1\""
> )
> );
> assertEquals(BASELINE, args.command());
> assertEquals(BaselineCommand.SET, args.baselineArguments().getCmd());
> // FIx me: expected 2, actual 6
> assertEquals(2, args.baselineArguments().getConsistentIds().size());
> assertEquals("1,2,3",
> args.baselineArguments().getConsistentIds().get(0));
> assertEquals("3,2,1",
> args.baselineArguments().getConsistentIds().get(1));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11812) control.sh ignores quotes in passed arguments
[
https://issues.apache.org/jira/browse/IGNITE-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11812:
---
Assignee: Andrey Kalinin
> control.sh ignores quotes in passed arguments
> -
>
> Key: IGNITE-11812
> URL: https://issues.apache.org/jira/browse/IGNITE-11812
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
>
> Control.sh should consider quotes in incoming arguments. i.e. I expect that
> {code:java}
> control.sh --baseline set "p1,p2,p3","p4,p5,p6" --yes
> {code}
> set BLT with two nodes with consistent ids: {{p1,p2,p3}} and {{p4,p5,p6}},
> but now it tries to set BLT with six nodes {{p1}}, {{p2}}, {{p3}}, {{p4}},
> {{p5}}, {{p6}}
> Reproducer. (Add this test to {{CommandHandlerParsingTest}})
> {code:java}
> @Test
> public void testQuotesWillNotIgnored() throws Exception {
> CommandHandler hnd = new CommandHandler();
> Arguments args = hnd.parseAndValidate(
> Arrays.asList(
> BASELINE.text(),
> BaselineCommand.SET.text(),
> "\"1,2,3\",\"3,2,1\""
> )
> );
> assertEquals(BASELINE, args.command());
> assertEquals(BaselineCommand.SET, args.baselineArguments().getCmd());
> // FIx me: expected 2, actual 6
> assertEquals(2, args.baselineArguments().getConsistentIds().size());
> assertEquals("1,2,3",
> args.baselineArguments().getConsistentIds().get(0));
> assertEquals("3,2,1",
> args.baselineArguments().getConsistentIds().get(1));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-11733) IdleVerify command should print end time of execution
[ https://issues.apache.org/jira/browse/IGNITE-11733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin closed IGNITE-11733. --- Ignite Flags: (was: Docs Required) > IdleVerify command should print end time of execution > - > > Key: IGNITE-11733 > URL: https://issues.apache.org/jira/browse/IGNITE-11733 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > > Idle_verufy now prints only start time of execution. Need to improve output > by add end time to output. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11733) IdleVerify command should print end time of execution
[ https://issues.apache.org/jira/browse/IGNITE-11733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin resolved IGNITE-11733. - Resolution: Invalid > IdleVerify command should print end time of execution > - > > Key: IGNITE-11733 > URL: https://issues.apache.org/jira/browse/IGNITE-11733 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Assignee: Andrey Kalinin >Priority: Minor > > Idle_verufy now prints only start time of execution. Need to improve output > by add end time to output. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11733) IdleVerify command should print end time of execution
Andrey Kalinin created IGNITE-11733: --- Summary: IdleVerify command should print end time of execution Key: IGNITE-11733 URL: https://issues.apache.org/jira/browse/IGNITE-11733 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin Assignee: Andrey Kalinin Idle_verufy now prints only start time of execution. Need to improve output by add end time to output. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11147) Dynamic cache start during rebalance leads to start rebalance for all cache groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true
[ https://issues.apache.org/jira/browse/IGNITE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11147: --- Assignee: Vladislav Pyatkov (was: Ivan Daschinskiy) > Dynamic cache start during rebalance leads to start rebalance for all cache > groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true > -- > > Key: IGNITE-11147 > URL: https://issues.apache.org/jira/browse/IGNITE-11147 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Sergey Antonov >Assignee: Vladislav Pyatkov >Priority: Blocker > Fix For: 2.8 > > > Scenario: > 1) Start cluster with PDS and option (IGNITE_DISABLE_WAL_DURING_REBALANCING = > true). Activate cluster and start few dinymic caches. > 2) Stop one node and clean its PDS. > 3) Start the node again. It's come back to the cluster. Rebalance started. > 4) During rebalance start some caches (part of them should be already started > on nodes). > Expected: > Rebalance will be started only for new caches. For other nodes rebalance > willn't canceled. > Actual: > Rebalance wiil be canceled and starts again for all cache groups (including > rebalanced yet) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin resolved IGNITE-11591.
-
Resolution: Duplicate
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11591) Add info about lock candidates that are ahead in queue to transaction timeout error message
[
https://issues.apache.org/jira/browse/IGNITE-11591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11591:
---
Assignee: Andrey Kalinin
> Add info about lock candidates that are ahead in queue to transaction timeout
> error message
> ---
>
> Key: IGNITE-11591
> URL: https://issues.apache.org/jira/browse/IGNITE-11591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
>
> If transaction is timed out due to lock acquisition failure, corresponding
> error will show up in server log on DHT (primary) node:
> {code:java}
> [2019-03-20
> 21:13:10,831][ERROR][grid-timeout-worker-#23%transactions.TxRollbackOnTimeoutTest0%][GridDhtColocatedCache]
> Failed to acquire lock for request: GridNearLockRequest
> [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], miniId=1,
> dhtVers=GridCacheVersion[] [null],
> subjId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, taskNameHash=0, createTtl=-1,
> accessTtl=-1, flags=6, txLbl=null, filter=null,
> super=GridDistributedLockRequest
> [nodeId=651a30e1-45ac-4b35-86d2-028d1f81d8dc, nearXidVer=GridCacheVersion
> [topVer=164585585, order=1553105588524, nodeOrder=4], threadId=262,
> futId=5967e4c9961-d32ea2a6-1789-47d7-bdbf-aa66e6d8c35b, timeout=890,
> isInTx=true, isInvalidate=false, isRead=false, isolation=REPEATABLE_READ,
> retVals=[false], txSize=2, flags=0, keysCnt=1,
> super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=164585585,
> order=1553105588524, nodeOrder=4], committedVers=null, rolledbackVers=null,
> cnt=0, super=GridCacheIdMessage [cacheId=3556498
> class
> org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
> Failed to acquire lock within provided timeout for transaction [timeout=890,
> tx=GridDhtTxLocal[xid=f219e4c9961--09cf-6071--0001,
> xidVersion=GridCacheVersion [topVer=164585585, order=1553105588527,
> nodeOrder=1], concurrency=PESSIMISTIC, isolation=REPEATABLE_READ,
> state=MARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c7dccddb-dee1-4499-94b1-03896350, timeout=890, duration=891]]
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1766)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter$PostLockClosure1.apply(IgniteTxLocalAdapter.java:1714)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$2.applyx(GridEmbeddedFuture.java:86)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:292)
> at
> org.apache.ignite.internal.util.future.GridEmbeddedFuture$AsyncListener1.apply(GridEmbeddedFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundIdentityFuture.onDone(GridCacheCompoundIdentityFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:793)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:89)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1189)
> at
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:234)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.j
> {code}
> It would be much more useful if this message also contained information about
> transaction that actually owns corresponding lock (or information about all
> transactions that are ahead in queue if there are several).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9934) Improve logging on partition map exchange
[ https://issues.apache.org/jira/browse/IGNITE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-9934: -- Assignee: Andrey Kalinin > Improve logging on partition map exchange > - > > Key: IGNITE-9934 > URL: https://issues.apache.org/jira/browse/IGNITE-9934 > Project: Ignite > Issue Type: Improvement >Reporter: Vladislav Pyatkov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Partition Map Exchange (PME) is a cluster wide process, be the reason it does > not completed before then each node do not done its part of job. > Coordinator, as a not witch managed the process, can to print quantity nodes > finished its stage of PME and other than, which not yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10797) Remove unused methods from IgniteCacheSnapshotManager.
[ https://issues.apache.org/jira/browse/IGNITE-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-10797: --- Assignee: Andrey Kalinin (was: Stanilovsky Evgeny) > Remove unused methods from IgniteCacheSnapshotManager. > -- > > Key: IGNITE-10797 > URL: https://issues.apache.org/jira/browse/IGNITE-10797 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Andrey Kalinin >Priority: Major > Fix For: 2.8 > > > Remove unused methods: > IgniteCacheSnapshotManager#flushDirtyPageHandler > IgniteCacheSnapshotManager#onPageWrite -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11245) Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter.
[ https://issues.apache.org/jira/browse/IGNITE-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781512#comment-16781512 ] Andrey Kalinin edited comment on IGNITE-11245 at 3/1/19 12:46 PM: -- [~v.pyatkov], this scenario is fully covered by _*BinaryMetadataConcurrentUpdateWithIndexesTest*_ written by [~ascherbakov] in IGNITE-9830. was (Author: 6uest): [~v.pyatkov], this scenario is fully covered by _*BinaryMetadataConcurrentUpdateWithIndexesTest*_ written by [~ascherbakov] on IGNITE-9830. > Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter. > --- > > Key: IGNITE-11245 > URL: https://issues.apache.org/jira/browse/IGNITE-11245 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Andrey Kalinin >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT with > IGNITE_WAIT_SCHEMA_UPDATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11245) Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter.
[ https://issues.apache.org/jira/browse/IGNITE-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781512#comment-16781512 ] Andrey Kalinin commented on IGNITE-11245: - [~v.pyatkov], this scenario is fully covered by _*BinaryMetadataConcurrentUpdateWithIndexesTest*_ written by [~ascherbakov] on IGNITE-9830. > Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter. > --- > > Key: IGNITE-11245 > URL: https://issues.apache.org/jira/browse/IGNITE-11245 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Andrey Kalinin >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT with > IGNITE_WAIT_SCHEMA_UPDATE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11322) [USABILITY] Extend Node FAILED message by add consistentId if it exist
[ https://issues.apache.org/jira/browse/IGNITE-11322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16778800#comment-16778800 ] Andrey Kalinin commented on IGNITE-11322: - [~antonovsergey93], please review again. > [USABILITY] Extend Node FAILED message by add consistentId if it exist > -- > > Key: IGNITE-11322 > URL: https://issues.apache.org/jira/browse/IGNITE-11322 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: ARomantsov >Assignee: Andrey Kalinin >Priority: Major > Labels: newbie, usability > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Now I having only this > [GridDiscoveryManager] Node FAILED: TcpDiscoveryNode > [id=f8cd73a1-8da5-4a07-b298-55634dd7c9f8, addrs=ArrayList [127.0.0.1], > sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, > lastExchangeTime=1550141566893, loc=false, isClient=false] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11199) Add extra logging for client-server connections in TCP discovery
[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1635#comment-1635
]
Andrey Kalinin commented on IGNITE-11199:
-
> "Initialized connection with remote " message - maybe consistent ID is not
> really needed in this message
[~ivan.glukos], in this message, only nodeId and socketAddress are printed.
> below there's code that prints nearly the same message with DEBUG level.
> Maybe we should remove it?
Got it.
> Add extra logging for client-server connections in TCP discovery
>
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11199) Add extra logging for client-server connections in TCP discovery
[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1621#comment-1621
]
Andrey Kalinin commented on IGNITE-11199:
-
[~ivan.glukos], look at [IGNITE-11322]. In that ticket I added consistent ID in
toString representation.
> Add extra logging for client-server connections in TCP discovery
>
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11322) [USABILITY] Extend Node FAILED message by add consistentId if it exist
[ https://issues.apache.org/jira/browse/IGNITE-11322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11322: --- Assignee: Andrey Kalinin > [USABILITY] Extend Node FAILED message by add consistentId if it exist > -- > > Key: IGNITE-11322 > URL: https://issues.apache.org/jira/browse/IGNITE-11322 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: ARomantsov >Assignee: Andrey Kalinin >Priority: Major > Labels: newbie, usability > Fix For: 2.8 > > > Now I having only this > [GridDiscoveryManager] Node FAILED: TcpDiscoveryNode > [id=f8cd73a1-8da5-4a07-b298-55634dd7c9f8, addrs=ArrayList [127.0.0.1], > sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, > lastExchangeTime=1550141566893, loc=false, isClient=false] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11199) Add extra logging for client-server connections in TCP discovery
[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin updated IGNITE-11199:
Ignite Flags: (was: Docs Required)
> Add extra logging for client-server connections in TCP discovery
>
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11139) Remove deprecated snapshot tags from PageMetaIO.
[ https://issues.apache.org/jira/browse/IGNITE-11139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11139: --- Assignee: (was: Andrey Kalinin) > Remove deprecated snapshot tags from PageMetaIO. > > > Key: IGNITE-11139 > URL: https://issues.apache.org/jira/browse/IGNITE-11139 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinskiy >Priority: Major > Fix For: 3.0 > > > After resolving IGNITE-9672, unnecessary methods from PageMetaIO should be > removed. > Also corresponding PageDeltaRecords should be also removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11149) Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc
[ https://issues.apache.org/jira/browse/IGNITE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764132#comment-16764132 ] Andrey Kalinin commented on IGNITE-11149: - [~antonovsergey93] please, review again. > Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc > - > > Key: IGNITE-11149 > URL: https://issues.apache.org/jira/browse/IGNITE-11149 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Sergey Antonov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > After IGNITE-10505 default value of IGNITE_DISABLE_WAL_DURING_REBALANCING was > changed from false to true. But javadoc wasn't updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10917) IgniteCacheQueryNodeRestartSelfTest2.testRestarts stable failure
[
https://issues.apache.org/jira/browse/IGNITE-10917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762329#comment-16762329
]
Andrey Kalinin commented on IGNITE-10917:
-
This is more accurate link:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=973762188903143807=testDetails
> IgniteCacheQueryNodeRestartSelfTest2.testRestarts stable failure
>
>
> Key: IGNITE-10917
> URL: https://issues.apache.org/jira/browse/IGNITE-10917
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test
>
> {{IgniteCacheQueryNodeRestartSelfTest2.testRestarts}} fails on master. It was
> broken by extending exception details when query fails by linked ticked.
> Messages were changed but test expects old ones. You can find test statistics
> on TC
> https://ci.ignite.apache.org/viewLog.html?buildId=2789190=buildResultsDiv=IgniteTests24Java8_Queries2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11139) Remove deprecated snapshot tags from PageMetaIO.
[ https://issues.apache.org/jira/browse/IGNITE-11139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11139: --- Assignee: Andrey Kalinin > Remove deprecated snapshot tags from PageMetaIO. > > > Key: IGNITE-11139 > URL: https://issues.apache.org/jira/browse/IGNITE-11139 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Daschinskiy >Assignee: Andrey Kalinin >Priority: Major > Fix For: 3.0 > > > After resolving IGNITE-9672, unnecessary methods from PageMetaIO should be > removed. > Also corresponding PageDeltaRecords should be also removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11149) Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc
[ https://issues.apache.org/jira/browse/IGNITE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-11149: --- Assignee: Andrey Kalinin > Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc > - > > Key: IGNITE-11149 > URL: https://issues.apache.org/jira/browse/IGNITE-11149 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Sergey Antonov >Assignee: Andrey Kalinin >Priority: Major > > After IGNITE-10505 default value of IGNITE_DISABLE_WAL_DURING_REBALANCING was > changed from false to true. But javadoc wasn't updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11199) Add extra logging for client-server connections in TCP discovery
[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11199:
---
Assignee: Andrey Kalinin
> Add extra logging for client-server connections in TCP discovery
>
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Andrey Kalinin
>Priority: Major
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11120) Remove static fields from GridDhtLockFuture
[
https://issues.apache.org/jira/browse/IGNITE-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11120:
---
Assignee: (was: Andrey Kalinin)
> Remove static fields from GridDhtLockFuture
> ---
>
> Key: IGNITE-11120
> URL: https://issues.apache.org/jira/browse/IGNITE-11120
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Priority: Major
> Labels: newbie
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> /** Logger reference. */
> private static final AtomicReference logRef = new
> AtomicReference<>();
> /** Logger. */
> private static IgniteLogger log;
> /** Logger. */
> private static IgniteLogger msgLog;
> {code}
>
> In that case we can to miss log messages, when restart node without restart
> JVM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11175) Add support for maven local xml config file
Andrey Kalinin created IGNITE-11175:
---
Summary: Add support for maven local xml config file
Key: IGNITE-11175
URL: https://issues.apache.org/jira/browse/IGNITE-11175
Project: Ignite
Issue Type: Test
Reporter: Andrey Kalinin
Assignee: Andrey Kalinin
PublicTC builds require custom settings.xml with local Artifactory maven proxy
for builds speed up and stability.
Settins file path must be taken from new environmental variable
{{LOCAL_PROXY_MAVEN_SETTINGS}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11120) Remove static fields from GridDhtLockFuture
[
https://issues.apache.org/jira/browse/IGNITE-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11120:
---
Assignee: Andrey Kalinin
> Remove static fields from GridDhtLockFuture
> ---
>
> Key: IGNITE-11120
> URL: https://issues.apache.org/jira/browse/IGNITE-11120
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Andrey Kalinin
>Priority: Major
> Labels: newbie
>
> {code}
> /** Logger reference. */
> private static final AtomicReference logRef = new
> AtomicReference<>();
> /** Logger. */
> private static IgniteLogger log;
> /** Logger. */
> private static IgniteLogger msgLog;
> {code}
>
> In that case we can to miss log messages, when restart node without restart
> JVM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11112) control.sh incorrect work with the key '--force'.
Andrey Kalinin created IGNITE-2:
---
Summary: control.sh incorrect work with the key '--force'.
Key: IGNITE-2
URL: https://issues.apache.org/jira/browse/IGNITE-2
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: Andrey Kalinin
control.sh --wal delete with the key --force produces the error
control.sh --host --wal delete --force
{code:java}
Control utility [ver. 2.5.1-p142#20181016-sha1:f983e74f]
2018 Copyright(C) Apache Software Foundation
User: ***
Warning: the command will delete unused WAL segments.
Press 'y' to continue . . . Error: Task map operation produced no mapped jobs:
GridTaskSessionImpl
[taskName=org.apache.ignite.internal.visor.misc.VisorWalTask,
dep=GridDeployment [...]
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:528)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:489)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsyncUnsafe(GridTaskCommandHandler.java:227)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler.handleAsync(GridTaskCommandHandler.java:163)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:318)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:99)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:174)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11086) IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of seconds.
[
https://issues.apache.org/jira/browse/IGNITE-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin reassigned IGNITE-11086:
---
Assignee: Andrey Kalinin
> IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of
> seconds.
> --
>
> Key: IGNITE-11086
> URL: https://issues.apache.org/jira/browse/IGNITE-11086
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.7
>Reporter: Vitaliy Biryukov
>Assignee: Andrey Kalinin
>Priority: Major
> Labels: newbie
>
> According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should be set in
> seconds.
> Can be fixed by multiplying this parameter by 1000 instead of 100 in
> GridRestProcessor's constructor:
> {code:java}
> sesTokTtl =
> IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT,
> DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8407) Wrong memory size printing in IgniteCacheDatabaseSnaredManager
[
https://issues.apache.org/jira/browse/IGNITE-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin resolved IGNITE-8407.
Resolution: Duplicate
> Wrong memory size printing in IgniteCacheDatabaseSnaredManager
> --
>
> Key: IGNITE-8407
> URL: https://issues.apache.org/jira/browse/IGNITE-8407
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Priority: Trivial
>
> In checkDataRegionSize regCfg printing in "si" format (based on 1000, not
> 1024). Need to fix it and any other usages of getInitialSize()/getMaxSize())
> with U.readableSize(*, true)
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), true) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), true) + "]"
> {noformat}
> should be replaced with
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), false) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), false) +
> "]"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-8407) Wrong memory size printing in IgniteCacheDatabaseSnaredManager
[
https://issues.apache.org/jira/browse/IGNITE-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin closed IGNITE-8407.
--
> Wrong memory size printing in IgniteCacheDatabaseSnaredManager
> --
>
> Key: IGNITE-8407
> URL: https://issues.apache.org/jira/browse/IGNITE-8407
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Priority: Trivial
>
> In checkDataRegionSize regCfg printing in "si" format (based on 1000, not
> 1024). Need to fix it and any other usages of getInitialSize()/getMaxSize())
> with U.readableSize(*, true)
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), true) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), true) + "]"
> {noformat}
> should be replaced with
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), false) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), false) +
> "]"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-5463) Weird CPU load reported
[
https://issues.apache.org/jira/browse/IGNITE-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin closed IGNITE-5463.
--
> Weird CPU load reported
> ---
>
> Key: IGNITE-5463
> URL: https://issues.apache.org/jira/browse/IGNITE-5463
> Project: Ignite
> Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Minor
> Labels: newbie
>
> {noformat}
> 2017-06-09 16:27:55,827 INFO [IgniteKernal%187358542614215] -
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=56495ffd, name=187358542614215, uptime=00:46:42:936]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=4]
> ^-- CPU [cur=100%, avg=12.85%, GC=125.47%]
> ^-- PageMemory [pages=314674]
> ^-- Heap [used=4777MB, free=12.52%, comm=5461MB]
> ^-- Non heap [used=71MB, free=-1%, comm=77MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=1, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> Need to investigate strange numbers reported and fix. My Ignite process had
> no free heap at the moment I noticed that in the logs but OOME was not thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-5463) Weird CPU load reported
[
https://issues.apache.org/jira/browse/IGNITE-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin resolved IGNITE-5463.
Resolution: Cannot Reproduce
Closed due to lack of response from the creator of the ticket
> Weird CPU load reported
> ---
>
> Key: IGNITE-5463
> URL: https://issues.apache.org/jira/browse/IGNITE-5463
> Project: Ignite
> Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Minor
> Labels: newbie
>
> {noformat}
> 2017-06-09 16:27:55,827 INFO [IgniteKernal%187358542614215] -
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=56495ffd, name=187358542614215, uptime=00:46:42:936]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=4]
> ^-- CPU [cur=100%, avg=12.85%, GC=125.47%]
> ^-- PageMemory [pages=314674]
> ^-- Heap [used=4777MB, free=12.52%, comm=5461MB]
> ^-- Non heap [used=71MB, free=-1%, comm=77MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=1, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> Need to investigate strange numbers reported and fix. My Ignite process had
> no free heap at the moment I noticed that in the logs but OOME was not thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8407) Wrong memory size printing in IgniteCacheDatabaseSnaredManager
[
https://issues.apache.org/jira/browse/IGNITE-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745416#comment-16745416
]
Andrey Kalinin commented on IGNITE-8407:
This ticket looks like a duplicate of IGNITE-5755. [~sbberkov] I propose to
close this ticket. What do you think?
> Wrong memory size printing in IgniteCacheDatabaseSnaredManager
> --
>
> Key: IGNITE-8407
> URL: https://issues.apache.org/jira/browse/IGNITE-8407
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Priority: Trivial
>
> In checkDataRegionSize regCfg printing in "si" format (based on 1000, not
> 1024). Need to fix it and any other usages of getInitialSize()/getMaxSize())
> with U.readableSize(*, true)
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), true) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), true) + "]"
> {noformat}
> should be replaced with
> {noformat}
> throw new IgniteCheckedException("DataRegion must have size more than 10MB
> (use " +
> "DataRegionConfiguration.initialSize and .maxSize properties
> to set correct size in bytes) " +
> "[name=" + regCfg.getName() + ", initialSize=" +
> U.readableSize(regCfg.getInitialSize(), false) +
> ", maxSize=" + U.readableSize(regCfg.getMaxSize(), false) +
> "]"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10476) Merge similar tests.
[ https://issues.apache.org/jira/browse/IGNITE-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-10476: --- Assignee: Andrey Kalinin > Merge similar tests. > > > Key: IGNITE-10476 > URL: https://issues.apache.org/jira/browse/IGNITE-10476 > Project: Ignite > Issue Type: Test >Reporter: Andrew Mashenkov >Assignee: Andrey Kalinin >Priority: Minor > Labels: MakeTeamcityGreenAgain > > CacheNamesSelfTest and CacheNamesWithSpecialCharactersTest looks similar and > can be merged. > We already have test suite these tests are related to, so we can merge them > into GridCacheConfigurationValidationSelfTest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-3622) BinaryObject: print idHash in toString() method only in debug mode
[
https://issues.apache.org/jira/browse/IGNITE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744059#comment-16744059
]
Andrey Kalinin commented on IGNITE-3622:
[~vozerov] I would like to know your opinion about the presence of idHash in
the toString() method output. Can it be safely removed?
> BinaryObject: print idHash in toString() method only in debug mode
> --
>
> Key: IGNITE-3622
> URL: https://issues.apache.org/jira/browse/IGNITE-3622
> Project: Ignite
> Issue Type: Task
> Components: binary
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Rohit Mohta
>Priority: Trivial
> Labels: newbie
>
> Current implementation of BinaryObject.toString() method print idHash for
> internal objects, for example, for AffinityKey.
> This lead to "unstable" result of toString() method, you will get different
> strings on each toString() invocation.
> Possible fix: introduce
> {code}
> private static final boolean debug = false;
> {code}
> And check this flag in toString().
> If some one will need idHash for debug reasons he could change this flag in
> its private build and debug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5463) Weird CPU load reported
[
https://issues.apache.org/jira/browse/IGNITE-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744011#comment-16744011
]
Andrey Kalinin commented on IGNITE-5463:
[~yzhdanov] This ticket was created more than a year and a half ago and, as it
seems to me, the attached information is not enough to reproduce this
situation. In addition, since then the product progress has gone far ahead.
Thus, I propose to close this ticket as irrelevant.
> Weird CPU load reported
> ---
>
> Key: IGNITE-5463
> URL: https://issues.apache.org/jira/browse/IGNITE-5463
> Project: Ignite
> Issue Type: Bug
>Reporter: Yakov Zhdanov
>Priority: Minor
> Labels: newbie
>
> {noformat}
> 2017-06-09 16:27:55,827 INFO [IgniteKernal%187358542614215] -
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=56495ffd, name=187358542614215, uptime=00:46:42:936]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=4]
> ^-- CPU [cur=100%, avg=12.85%, GC=125.47%]
> ^-- PageMemory [pages=314674]
> ^-- Heap [used=4777MB, free=12.52%, comm=5461MB]
> ^-- Non heap [used=71MB, free=-1%, comm=77MB]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=1, qSize=0]
> ^-- Outbound messages queue [size=0]
> {noformat}
> Need to investigate strange numbers reported and fix. My Ignite process had
> no free heap at the moment I noticed that in the logs but OOME was not thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10949) org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE
[ https://issues.apache.org/jira/browse/IGNITE-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-10949: --- Assignee: Andrey Kalinin > org.apache.ignite.internal.MarshallerContextImpl.CombinedMap generates NPE > -- > > Key: IGNITE-10949 > URL: https://issues.apache.org/jira/browse/IGNITE-10949 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.7 >Reporter: Alexand Polyakov >Assignee: Andrey Kalinin >Priority: Major > Labels: newbie > > method entrySet return null then generates NullPointerException in method > hashCode, toString and all classes that use an instance of this object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10941) Ignite won't build with Java 11
[
https://issues.apache.org/jira/browse/IGNITE-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kalinin updated IGNITE-10941:
Description:
*sun.misc*, *sun.nio.ch*, *com.sun.jmx.mbeanserver* is no longer supported in
Java 11. This makes it impossible to build Apache Ignite for this version.
When I run the _Buil Progect_ from the IDEA IDE, I get the following error
messages (Warnings removed):
{code:java}
Information:java: Errors occurred while compiling module 'ignite-core'
Information:javac 11.0.1 was used to compile java sources
Information:15.01.19 14:07 - Compilation completed with 33 errors and 100
warnings in 33 s 148 ms
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java
Error:(258, 16) java: package sun.misc does not exist
Error:(8743, 29) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.IgniteUtils
Error:(8743, 49) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.IgniteUtils
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/util/GridUnsafe.java
Error:(32, 16) java: package sun.misc does not exist
Error:(60, 26) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1389, 20) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1391, 20) java: cannot find symbol
symbol: variable Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1396, 52) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1397, 42) java: cannot find symbol
symbol: class Unsafe
Error:(1398, 39) java: cannot find symbol
symbol: class Unsafe
Error:(1402, 37) java: cannot find symbol
symbol: class Unsafe
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryMarshaller.java
Error:(31, 16) java: package sun.misc does not exist
Error:(56, 29) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.binary.BinaryMarshaller
Error:(56, 49) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.binary.BinaryMarshaller
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedMarshaller.java
Error:(34, 16) java: package sun.misc does not exist
Error:(285, 29) java: cannot find symbol
symbol: class Unsafe
location: class
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller
Error:(285, 49) java: cannot find symbol
symbol: class Unsafe
location: class
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/jsr166/ConcurrentLinkedDeque8.java
Error:(30, 16) java: package sun.misc does not exist
Error:(327, 38) java: package sun.misc does not exist
Error:(1693, 34) java: package sun.misc does not exist
Error:(1716, 12) java: cannot find symbol
symbol: class Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1718, 20) java: cannot find symbol
symbol: variable Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1723, 52) java: cannot find symbol
symbol: class Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1725, 32) java: cannot find symbol
symbol: class Unsafe
Error:(1726, 39) java: cannot find symbol
symbol: class Unsafe
Error:(1730, 37) java: cannot find symbol
symbol: class Unsafe
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/mem/file/MappedFile.java
Error:(29, 18) java: package sun.nio.ch does not exist
Error:(33, 62) java: cannot find symbol
symbol: class FileChannelImpl
location: class org.apache.ignite.internal.mem.file.MappedFile
Error:(36, 64) java: cannot find symbol
symbol: class FileChannelImpl
location: class org.apache.ignite.internal.mem.file.MappedFile
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/tck/TCKMBeanServerBuilder.java
Error:(20, 31) java: package com.sun.jmx.mbeanserver does not exist
Error:(37, 16) java: cannot find symbol
symbol: variable JmxMBeanServer
location: class org.apache.ignite.internal.tck.TCKMBeanServerBuilder
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/util/UnsafeDirectBufferCleaner.java
Error:(22, 16) java: package sun.misc does not exist
Error:(36, 26) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.UnsafeDirectBufferCleaner
---{code}
Trying to build with Maven produces the same result.
{code:java}
$ mvn compile -Plgpl
[jira] [Created] (IGNITE-10941) Ignite won't build with Java 11
Andrey Kalinin created IGNITE-10941:
---
Summary: Ignite won't build with Java 11
Key: IGNITE-10941
URL: https://issues.apache.org/jira/browse/IGNITE-10941
Project: Ignite
Issue Type: Bug
Environment: ~$ /usr/lib/jvm/java-11-oracle/bin/java -version
java version "11.0.1" 2018-10-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
Reporter: Andrey Kalinin
*sun.misc*, *sun.nio.ch*, *com.sun.jmx.mbeanserver* is no longer supported in
Java 11. This makes it impossible to build Apache Ignite for this version.
When I run the build from the IDE, I get the following error messages (Warnings
removed):
{code:java}
Information:java: Errors occurred while compiling module 'ignite-core'
Information:javac 11.0.1 was used to compile java sources
Information:15.01.19 14:07 - Compilation completed with 33 errors and 100
warnings in 33 s 148 ms
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java
Error:(258, 16) java: package sun.misc does not exist
Error:(8743, 29) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.IgniteUtils
Error:(8743, 49) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.IgniteUtils
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/util/GridUnsafe.java
Error:(32, 16) java: package sun.misc does not exist
Error:(60, 26) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1389, 20) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1391, 20) java: cannot find symbol
symbol: variable Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1396, 52) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.util.GridUnsafe
Error:(1397, 42) java: cannot find symbol
symbol: class Unsafe
Error:(1398, 39) java: cannot find symbol
symbol: class Unsafe
Error:(1402, 37) java: cannot find symbol
symbol: class Unsafe
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryMarshaller.java
Error:(31, 16) java: package sun.misc does not exist
Error:(56, 29) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.binary.BinaryMarshaller
Error:(56, 49) java: cannot find symbol
symbol: class Unsafe
location: class org.apache.ignite.internal.binary.BinaryMarshaller
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedMarshaller.java
Error:(34, 16) java: package sun.misc does not exist
Error:(285, 29) java: cannot find symbol
symbol: class Unsafe
location: class
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller
Error:(285, 49) java: cannot find symbol
symbol: class Unsafe
location: class
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/jsr166/ConcurrentLinkedDeque8.java
Error:(30, 16) java: package sun.misc does not exist
Error:(327, 38) java: package sun.misc does not exist
Error:(1693, 34) java: package sun.misc does not exist
Error:(1716, 12) java: cannot find symbol
symbol: class Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1718, 20) java: cannot find symbol
symbol: variable Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1723, 52) java: cannot find symbol
symbol: class Unsafe
location: class org.jsr166.ConcurrentLinkedDeque8
Error:(1725, 32) java: cannot find symbol
symbol: class Unsafe
Error:(1726, 39) java: cannot find symbol
symbol: class Unsafe
Error:(1730, 37) java: cannot find symbol
symbol: class Unsafe
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/mem/file/MappedFile.java
Error:(29, 18) java: package sun.nio.ch does not exist
Error:(33, 62) java: cannot find symbol
symbol: class FileChannelImpl
location: class org.apache.ignite.internal.mem.file.MappedFile
Error:(36, 64) java: cannot find symbol
symbol: class FileChannelImpl
location: class org.apache.ignite.internal.mem.file.MappedFile
---
/home/kalinin/git/incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/tck/TCKMBeanServerBuilder.java
Error:(20, 31) java: package com.sun.jmx.mbeanserver does not exist
Error:(37, 16) java: cannot find symbol
symbol: variable JmxMBeanServer
location: class
[jira] [Assigned] (IGNITE-10138) Description is not provided for operations of org.apache.ignite.mxbean.TransactionMetricsMxBean
[ https://issues.apache.org/jira/browse/IGNITE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin reassigned IGNITE-10138: --- Assignee: Andrey Kalinin > Description is not provided for operations of > org.apache.ignite.mxbean.TransactionMetricsMxBean > --- > > Key: IGNITE-10138 > URL: https://issues.apache.org/jira/browse/IGNITE-10138 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Max Shonichev >Assignee: Andrey Kalinin >Priority: Minor > Fix For: 2.5 > > Time Spent: 10m > Remaining Estimate: 0h > > Description mismatch for bean > 'TransactionMetrics.TransactionMetricsMxBeanImpl' > operation 'commitTime()': expected 'Last commit time.', actual 'Operation > exposed for management' > operation 'rollbackTime()': expected 'Last rollback time.', actual 'Operation > exposed for management' > operation 'txCommits()': expected 'Number of transaction commits.', actual > 'Operation exposed for management' > operation 'txRollbacks()': expected 'Number of transaction rollbacks.', > actual 'Operation exposed for management' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9954) An error in rolling back the transaction caused the cluster to hang
Andrey Kalinin created IGNITE-9954:
--
Summary: An error in rolling back the transaction caused the
cluster to hang
Key: IGNITE-9954
URL: https://issues.apache.org/jira/browse/IGNITE-9954
Project: Ignite
Issue Type: Bug
Reporter: Andrey Kalinin
Starts a transaction with a small timeout
on one node, we observe the rollback of the transaction by timeout:
{code:java}
2018-10-18 02:14:13.339
[ERROR][sys-stripe-48-#49%GRID%GridNodeName%][o.a.i.i.p.c.t.IgniteTxHandler]
Failed to process prepare request: GridDhtTxPrepareRequest
[nearNodeId=ab0c3e9f-1642-4779-a6a0-dd10a6efd387,
futId=54208048661-53dd6648-cc70-4076-a608-f6072645e609, miniId=1,
topVer=AffinityTopologyVersion [topVer=338, minorTopVer=0],
invalidateNearEntries={}, nearWrites=null, owned=null,
nearXidVer=GridCacheVersion [topVer=151260338, order=1543126364337,
nodeOrder=172], subjId=ab0c3e9f-1642-4779-a6a0-dd10a6efd387, taskNameHash=0,
preloadKeys=null, skipCompletedVers=false,
super=GridDistributedTxPrepareRequest [threadId=732, concurrency=PESSIMISTIC,
isolation=REPEATABLE_READ, writeVer=GridCacheVersion [topVer=151260338,
order=1543126439977, nodeOrder=81], timeout=9, reads=null, writes=ArrayList
[IgniteTxEntry [key=KeyCacheObjectImpl [part=12715, val=ids_name,
hasValBytes=true], cacheId=-1934881220, txKey=IgniteTxKey
[key=KeyCacheObjectImpl [part=12715, val=ids_name, hasValBytes=true],
cacheId=-1934881220], val=CacheObjectImpl [val=null,
hasValBytes=true][op=UPDATE, val=], prevVal=[op=NOOP, val=null],
oldVal=CacheObjectImpl [val=null, hasValBytes=true][op=UPDATE, val=],
entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null,
explicitVer=null, dhtVer=null, filters=CacheEntryPredicate[] [],
filtersPassed=false, filtersSet=false, entry=GridCacheMapEntry
[key=KeyCacheObjectImpl [part=12715, val=ids_name, hasValBytes=true], val=null,
startVer=1543128775655, ver=GridCacheVersion [topVer=151260338,
order=1543126364674, nodeOrder=81], hash=-864500235,
extras=GridCacheObsoleteEntryExtras [obsoleteVer=GridCacheVersion
[topVer=2147483647, order=0, nodeOrder=0]], flags=2]GridDistributedCacheEntry
[super=]GridDhtCacheEntry [rdrs=ReaderId[] [], part=12715, super=], prepared=0,
locked=false, nodeId=null, locMapped=false, expiryPlc=null,
transferExpiryPlc=false, flags=2, partUpdateCntr=0, serReadVer=null,
xidVer=null]], dhtVers=null, txSize=0, plc=2, txState=null,
flags=onePhase|last, super=GridDistributedBaseMessage [ver=GridCacheVersion
[topVer=151260338, order=1543126439864, nodeOrder=81], committedVers=null,
rolledbackVers=null, cnt=0, super=GridCacheIdMessage [cacheId=0
org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
Transaction timed out: GridCacheSharedManagerAdapter [starting=true, stop=false]
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.prepareTx(IgniteTxManager.java:868)
at
org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.prepareRemoteTx(GridDistributedTxRemoteAdapter.java:406)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.startRemoteTx(IgniteTxHandler.java:1754)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxPrepareRequest(IgniteTxHandler.java:1121)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$400(IgniteTxHandler.java:101)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:205)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$5.apply(IgniteTxHandler.java:203)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1058)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:583)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:382)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1$2$1.run(GridCacheIoManager.java:277)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
at the same time on another node:
{code:java}
2018-10-18 02:14:03.948 [WARN
][sys-stripe-36-#37%GRID%GridNodeName%][o.apache.ignite.cache.msg.tx.finish]
Received finish request for completed transaction (the message may be too late)
[txId=GridCacheVersion
[jira] [Updated] (IGNITE-9701) Create pass-through identifier for every single Parrtition Map Exchange
[ https://issues.apache.org/jira/browse/IGNITE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9701: --- Priority: Minor (was: Major) > Create pass-through identifier for every single Parrtition Map Exchange > --- > > Key: IGNITE-9701 > URL: https://issues.apache.org/jira/browse/IGNITE-9701 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Priority: Minor > > In order to improve the monitoring of PME, we can provide each message about > this event in the logs with a unique identifier that will allow us to more > clearly determine the start and end time, as well as to accurately identify > events related to this PME. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9701) Create pass-through identifier for every single Parrtition Map Exchange
Andrey Kalinin created IGNITE-9701: -- Summary: Create pass-through identifier for every single Parrtition Map Exchange Key: IGNITE-9701 URL: https://issues.apache.org/jira/browse/IGNITE-9701 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin In order to improve the monitoring of PME, we can provide each message about this event in the logs with a unique identifier that will allow us to more clearly determine the start and end time, as well as to accurately identify events related to this PME. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9599) Add ability to manage compression level for compressed WAL archives
[ https://issues.apache.org/jira/browse/IGNITE-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9599: --- Description: In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We did some tests: the file size of 1GB is compressed at the default compression level for 1 minute, the output file size is ~120MB. After that, the compression rate was tested with compression-level=-1: 1 GB file is compressed in 13 seconds, the output file size is ~125MB. So we need add an option to change the default compression level in the ignite configuration file. was:In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We need add an option to change the default compression level in the ignite configuration file. > Add ability to manage compression level for compressed WAL archives > --- > > Key: IGNITE-9599 > URL: https://issues.apache.org/jira/browse/IGNITE-9599 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Priority: Minor > > In some cases, WAL compression performance is not sufficient, i.e. new > archives accumulate faster than old ones are compressed. > We did some tests: the file size of 1GB is compressed at the default > compression level for 1 minute, the output file size is ~120MB. > After that, the compression rate was tested with compression-level=-1: 1 GB > file is compressed in 13 seconds, the output file size is ~125MB. > So we need add an option to change the default compression level in the > ignite configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9599) Add ability to manage compression level for compressed WAL archives
[ https://issues.apache.org/jira/browse/IGNITE-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9599: --- Description: In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We need add an option to change the default compression level. (was: In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We must add an option to change the default compression level.) > Add ability to manage compression level for compressed WAL archives > --- > > Key: IGNITE-9599 > URL: https://issues.apache.org/jira/browse/IGNITE-9599 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Priority: Minor > > In some cases, WAL compression performance is not sufficient, i.e. new > archives accumulate faster than old ones are compressed. We need add an > option to change the default compression level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9599) Add ability to manage compression level for compressed WAL archives
[ https://issues.apache.org/jira/browse/IGNITE-9599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kalinin updated IGNITE-9599: --- Description: In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We need add an option to change the default compression level in the ignite configuration file. (was: In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We need add an option to change the default compression level.) > Add ability to manage compression level for compressed WAL archives > --- > > Key: IGNITE-9599 > URL: https://issues.apache.org/jira/browse/IGNITE-9599 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Kalinin >Priority: Minor > > In some cases, WAL compression performance is not sufficient, i.e. new > archives accumulate faster than old ones are compressed. We need add an > option to change the default compression level in the ignite configuration > file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9599) Add ability to manage compression level for compressed WAL archives
Andrey Kalinin created IGNITE-9599: -- Summary: Add ability to manage compression level for compressed WAL archives Key: IGNITE-9599 URL: https://issues.apache.org/jira/browse/IGNITE-9599 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin In some cases, WAL compression performance is not sufficient, i.e. new archives accumulate faster than old ones are compressed. We must add an option to change the default compression level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9061) Add ability to specify a set of partitions for ScanQuery
Andrey Kalinin created IGNITE-9061: -- Summary: Add ability to specify a set of partitions for ScanQuery Key: IGNITE-9061 URL: https://issues.apache.org/jira/browse/IGNITE-9061 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin The ability to specify a set of partitions for ScanQuery will allow to optimize in the form of a grouping of nodes on which the transferred partitions are located, and send only one request to each node and immediately return all the data on the specified partitions from each node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
