[jira] [Created] (IGNITE-11809) Missing help for control.sh --baseline collect command.
Sergey Antonov created IGNITE-11809: --- Summary: Missing help for control.sh --baseline collect command. Key: IGNITE-11809 URL: https://issues.apache.org/jira/browse/IGNITE-11809 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov I found enum value {{BaselineCommand#COLLECT}}, but I don't see this option in help output. We should add example with {{BaselineCommand#COLLECT}} to {{control.sh --help output}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10913) Reduce heap occupation by o.a.i.i.processors.cache.persistence.file.FilePageStore instances.
[ https://issues.apache.org/jira/browse/IGNITE-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826438#comment-16826438 ] Denis Chudov commented on IGNITE-10913: --- [~antkr], please review > Reduce heap occupation by > o.a.i.i.processors.cache.persistence.file.FilePageStore instances. > > > Key: IGNITE-10913 > URL: https://issues.apache.org/jira/browse/IGNITE-10913 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > With large topology and large amount of caches/partitions and enabled > persistence could be millions of FilePageStore objects in heap (for each > partition). > Each instance has a reference to a File (field cfgFile) storing as String > absolute path to a partition. > Also internal File inplementation (on example UnixFile) also allocates space > for file path. > I observed about 2Gb of heap space occupied by these objects in one of > environments. > Solution: dereference (set to null) cfgFile after object creation, create > File object lazily on demand when needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10913) Reduce heap occupation by o.a.i.i.processors.cache.persistence.file.FilePageStore instances.
[ https://issues.apache.org/jira/browse/IGNITE-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826436#comment-16826436 ] Denis Chudov commented on IGNITE-10913: --- Blocker is not related to this commit. > Reduce heap occupation by > o.a.i.i.processors.cache.persistence.file.FilePageStore instances. > > > Key: IGNITE-10913 > URL: https://issues.apache.org/jira/browse/IGNITE-10913 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > With large topology and large amount of caches/partitions and enabled > persistence could be millions of FilePageStore objects in heap (for each > partition). > Each instance has a reference to a File (field cfgFile) storing as String > absolute path to a partition. > Also internal File inplementation (on example UnixFile) also allocates space > for file path. > I observed about 2Gb of heap space occupied by these objects in one of > environments. > Solution: dereference (set to null) cfgFile after object creation, create > File object lazily on demand when needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10913) Reduce heap occupation by o.a.i.i.processors.cache.persistence.file.FilePageStore instances.
[ https://issues.apache.org/jira/browse/IGNITE-10913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826433#comment-16826433 ] Ignite TC Bot commented on IGNITE-10913: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}[Javadoc]{color} [[tests 0 BuildFailureOnMessage |https://ci.ignite.apache.org/viewLog.html?buildId=3700048]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3690255&buildTypeId=IgniteTests24Java8_RunAll] > Reduce heap occupation by > o.a.i.i.processors.cache.persistence.file.FilePageStore instances. > > > Key: IGNITE-10913 > URL: https://issues.apache.org/jira/browse/IGNITE-10913 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > With large topology and large amount of caches/partitions and enabled > persistence could be millions of FilePageStore objects in heap (for each > partition). > Each instance has a reference to a File (field cfgFile) storing as String > absolute path to a partition. > Also internal File inplementation (on example UnixFile) also allocates space > for file path. > I observed about 2Gb of heap space occupied by these objects in one of > environments. > Solution: dereference (set to null) cfgFile after object creation, create > File object lazily on demand when needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11579) Add new commands to deal with garbage in partitions which left after cache destroy in shared cache groups
[ https://issues.apache.org/jira/browse/IGNITE-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826343#comment-16826343 ] Ivan Rakov commented on IGNITE-11579: - Looks good now. Thanks, merged to master. > Add new commands to deal with garbage in partitions which left after cache > destroy in shared cache groups > - > > Key: IGNITE-11579 > URL: https://issues.apache.org/jira/browse/IGNITE-11579 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > The scenario of how to get to this situation (garbage in partition) described > in IGNITE-11578. > We need to add a new command for control.sh: > - show such keys; > - remove such keys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11579) Add new commands to deal with garbage in partitions which left after cache destroy in shared cache groups
[ https://issues.apache.org/jira/browse/IGNITE-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-11579: Fix Version/s: 2.8 > Add new commands to deal with garbage in partitions which left after cache > destroy in shared cache groups > - > > Key: IGNITE-11579 > URL: https://issues.apache.org/jira/browse/IGNITE-11579 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.8 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > The scenario of how to get to this situation (garbage in partition) described > in IGNITE-11578. > We need to add a new command for control.sh: > - show such keys; > - remove such keys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11808) Scale test execution time constant along in IgniteCacheCrossCacheTxFailoverTest
Ivan Pavlukhin created IGNITE-11808: --- Summary: Scale test execution time constant along in IgniteCacheCrossCacheTxFailoverTest Key: IGNITE-11808 URL: https://issues.apache.org/jira/browse/IGNITE-11808 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin Execution time of {{IgniteCacheCrossCacheTxFailoverTest}} is scaled by using {{ScaleFactorUtil}}. Currently an explicit constant is used to define test execution timeout and a magic constant is used after scaling to define a duration of the test. It is better to use the explicit constant throughout. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11592) NPE in case of continuing tx and cache stop operation.
[ https://issues.apache.org/jira/browse/IGNITE-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826251#comment-16826251 ] Ignite TC Bot commented on IGNITE-11592: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Cache (Restarts) 2{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3698348]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3698401&buildTypeId=IgniteTests24Java8_RunAll] > NPE in case of continuing tx and cache stop operation. > --- > > Key: IGNITE-11592 > URL: https://issues.apache.org/jira/browse/IGNITE-11592 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Parallel cache stop and tx operations may lead to NPE. > {code} > java.lang.NullPointerException > at > org.apache.ignite.internal.processors.cache.CacheObjectImpl.finishUnmarshal(CacheObjectImpl.java:129) > at > org.apache.ignite.internal.processors.cache.transactions.TxEntryValueHolder.unmarshal(TxEntryValueHolder.java:151) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:964) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.unmarshal(IgniteTxHandler.java:306) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:338) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:154) > at > org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.lambda$null$0(IgniteTxHandler.java:580) > 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:748) > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches and --cache-filter
[ https://issues.apache.org/jira/browse/IGNITE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-11076: - Summary: Add documentation for control.sh idle_verify --exclude-caches and --cache-filter (was: Add documentation for control.sh idle_verify --exclude-caches) > Add documentation for control.sh idle_verify --exclude-caches and > --cache-filter > > > Key: IGNITE-11076 > URL: https://issues.apache.org/jira/browse/IGNITE-11076 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > control.sh cache --help output > {noformat} > The '--cache subcommand' is used to get information about and perform actions > with caches. The command has the following syntax: > control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password > PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT] > [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]] > [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]] > [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE] > [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD] > [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH] > [--truststore-password TRUSTSTORE_PASSWORD] --cache [subcommand] > > The subcommands that take [nodeId] as an argument ('list', 'contention' and > 'validate_indexes') will be executed on the given node or on all server nodes > if the option is not specified. Other commands will run on a random server > node. > Subcommands: > > --cache list regexPattern [--groups|--seq] [nodeId] [--config] > [--output-format multi-line] > Show information about caches, groups or sequences that match a regular > expression. When executed without parameters, this subcommand prints the list > of caches. > Parameters: > --config - print all configuration parameters for each cache. > --output-format multi-line - print configuration parameters per line. This > option has effect only when used with --config and without [--groups|--seq]. > --groups - print information about groups. > --seq - print information about sequences. > > --cache contention minQueueSize [nodeId] [maxPrint] > Show the keys that are point of contention for multiple transactions. > > --cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches > cacheName1,...,cacheNameN)|(--cache-filter > ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN] > Verify counters and hash sums of primary and backup partitions for the > specified caches on an idle cluster and print out the differences, if any. > Parameters: > --check-crc - check the CRC-sum of pages stored on disk before verifying data > consistency in partitions between primary and backup nodes. > > --cache validate_indexes [cacheName1,...,cacheNameN] [nodeId] [--check-first > N|--check-through K] > Validate indexes on an idle cluster and print out the keys that are missing > in the indexes. > Parameters: > --check-first N - validate only the first N keys > --check-through K - validate every Kth key > > --cache distribution nodeId|null [cacheName1,...,cacheNameN] > [--user-attributes attrName1,...,attrNameN] > Prints the information about partition distribution. > > --cache reset_lost_partitions cacheName1,...,cacheNameN > Reset the state of lost partitions for the specified caches.{noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-11103: - Ignite Flags: (was: Docs Required) > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug > Components: UI >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches
[ https://issues.apache.org/jira/browse/IGNITE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826201#comment-16826201 ] Ilya Kasnacheev commented on IGNITE-11076: -- Please also document --cache-filter > Add documentation for control.sh idle_verify --exclude-caches > - > > Key: IGNITE-11076 > URL: https://issues.apache.org/jira/browse/IGNITE-11076 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > control.sh cache --help output > {noformat} > The '--cache subcommand' is used to get information about and perform actions > with caches. The command has the following syntax: > control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password > PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT] > [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]] > [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]] > [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE] > [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD] > [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH] > [--truststore-password TRUSTSTORE_PASSWORD] --cache [subcommand] > > The subcommands that take [nodeId] as an argument ('list', 'contention' and > 'validate_indexes') will be executed on the given node or on all server nodes > if the option is not specified. Other commands will run on a random server > node. > Subcommands: > > --cache list regexPattern [--groups|--seq] [nodeId] [--config] > [--output-format multi-line] > Show information about caches, groups or sequences that match a regular > expression. When executed without parameters, this subcommand prints the list > of caches. > Parameters: > --config - print all configuration parameters for each cache. > --output-format multi-line - print configuration parameters per line. This > option has effect only when used with --config and without [--groups|--seq]. > --groups - print information about groups. > --seq - print information about sequences. > > --cache contention minQueueSize [nodeId] [maxPrint] > Show the keys that are point of contention for multiple transactions. > > --cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches > cacheName1,...,cacheNameN)|(--cache-filter > ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN] > Verify counters and hash sums of primary and backup partitions for the > specified caches on an idle cluster and print out the differences, if any. > Parameters: > --check-crc - check the CRC-sum of pages stored on disk before verifying data > consistency in partitions between primary and backup nodes. > > --cache validate_indexes [cacheName1,...,cacheNameN] [nodeId] [--check-first > N|--check-through K] > Validate indexes on an idle cluster and print out the keys that are missing > in the indexes. > Parameters: > --check-first N - validate only the first N keys > --check-through K - validate every Kth key > > --cache distribution nodeId|null [cacheName1,...,cacheNameN] > [--user-attributes attrName1,...,attrNameN] > Prints the information about partition distribution. > > --cache reset_lost_partitions cacheName1,...,cacheNameN > Reset the state of lost partitions for the specified caches.{noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-11103: - Component/s: UI > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug > Components: UI >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11807) Index validation control.sh command may provide false-positive error results
[ https://issues.apache.org/jira/browse/IGNITE-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Rakov updated IGNITE-11807: Description: There are two possible issues in validate_indexes command: 1. In case index validation is performed under load, there's a chance that we'll fetch link from B+ tree and won't found this key in partition cache data store as per it was conurrently removed. We may work it around by double-checking partition update counters (before and after indexes validation procedure). 2. Since indexes validation is subscribed to checkpoint start (reason: we perform CRC validation of file page store pages which is sensitive to concurrent disk page writes), we may bump into the following situation: - User fairly stops all load - A few moments later users triggers validate_indexes - Checkpoint starts due to timeout, pages that were modified before validate_indexes start are being written to the disk - validate_indexes fails We may work it around by triggering checkpoint forcibly before start of indexes validation activities. was: There are two possible issues in validate_indexes command: 1. In case index validation is performed under load, there's a chance that we'll fetch link from B+ tree and won't found this key in partition cache data store as per it was conurrently removed. We may work it around by double-checking partition update counters (before and after indexes validation procedure). 2. Since indexes validation is subscribed to checkpoint start (reason: we perform CRC validation of file page store pages which is sensitive to concurrent disk page writes), we may bump into the following situation: - User fairly stops all load - A few moments later users triggers validate_indexes - Checkpoint starts due to timeout, pages that were modified before validate_indexes start are being written to the disk - validate_indexes fails We may work it around by triggering checkpoint forcibly before start of indexes validation activities. > Index validation control.sh command may provide false-positive error results > > > Key: IGNITE-11807 > URL: https://issues.apache.org/jira/browse/IGNITE-11807 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Priority: Major > Fix For: 2.8 > > > There are two possible issues in validate_indexes command: > 1. In case index validation is performed under load, there's a chance that > we'll fetch link from B+ tree and won't found this key in partition cache > data store as per it was conurrently removed. > We may work it around by double-checking partition update counters (before > and after indexes validation procedure). > 2. Since indexes validation is subscribed to checkpoint start (reason: we > perform CRC validation of file page store pages which is sensitive to > concurrent disk page writes), we may bump into the following situation: > - User fairly stops all load > - A few moments later users triggers validate_indexes > - Checkpoint starts due to timeout, pages that were modified before > validate_indexes start are being written to the disk > - validate_indexes fails > We may work it around by triggering checkpoint forcibly before start of > indexes validation activities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11807) Index validation control.sh command may provide false-positive error results
Ivan Rakov created IGNITE-11807: --- Summary: Index validation control.sh command may provide false-positive error results Key: IGNITE-11807 URL: https://issues.apache.org/jira/browse/IGNITE-11807 Project: Ignite Issue Type: Bug Reporter: Ivan Rakov Fix For: 2.8 There are two possible issues in validate_indexes command: 1. In case index validation is performed under load, there's a chance that we'll fetch link from B+ tree and won't found this key in partition cache data store as per it was conurrently removed. We may work it around by double-checking partition update counters (before and after indexes validation procedure). 2. Since indexes validation is subscribed to checkpoint start (reason: we perform CRC validation of file page store pages which is sensitive to concurrent disk page writes), we may bump into the following situation: - User fairly stops all load - A few moments later users triggers validate_indexes - Checkpoint starts due to timeout, pages that were modified before validate_indexes start are being written to the disk - validate_indexes fails We may work it around by triggering checkpoint forcibly before start of indexes validation activities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826116#comment-16826116 ] Sergey Antonov commented on IGNITE-11103: - [~ilyak] Changes looks good to me. Thank you! > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826108#comment-16826108 ] Ilya Kasnacheev commented on IGNITE-11103: -- [~antonovsergey93] I did, one resolved, the other one doesn't seem immediately fixable. > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826089#comment-16826089 ] Sergey Antonov commented on IGNITE-11103: - [~ilyak] I left 2 comments. please look at them. > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11470) Views don't show in Dbeaver
[ https://issues.apache.org/jira/browse/IGNITE-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826061#comment-16826061 ] Pavel Kuznetsov commented on IGNITE-11470: -- 7) I would add {{@Nullable}} annotation to {{org.apache.ignite.internal.processors.query.TableInformation#affinityKeyColumn()}}. Doc could be more clear, if we added what "is not applicable" mean: "In case of affinity key is the same as _KEY" > Views don't show in Dbeaver > --- > > Key: IGNITE-11470 > URL: https://issues.apache.org/jira/browse/IGNITE-11470 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 4h 10m > Remaining Estimate: 0h > > At Database navigator tab we can see no a views. As of now we should see at > least SQL system views. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11776) IgnitePdsStartWIthEmptyArchive is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826038#comment-16826038 ] Dmitriy Govorukhin commented on IGNITE-11776: - [~slava.koptilin] Looks good to me, merged to master. Thanks for your contribution! > IgnitePdsStartWIthEmptyArchive is flaky > --- > > Key: IGNITE-11776 > URL: https://issues.apache.org/jira/browse/IGNITE-11776 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > It looks like the root cause of the issue is late registration of the > listener. It should be done statically via {{IgniteConfiguration}} I think. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11776) IgnitePdsStartWIthEmptyArchive is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826022#comment-16826022 ] Vyacheslav Koptilin commented on IGNITE-11776: -- Hello [~DmitriyGovorukhin], Could you please take a look at this PR? > IgnitePdsStartWIthEmptyArchive is flaky > --- > > Key: IGNITE-11776 > URL: https://issues.apache.org/jira/browse/IGNITE-11776 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > It looks like the root cause of the issue is late registration of the > listener. It should be done statically via {{IgniteConfiguration}} I think. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11699) Node can't start after forced shutdown if the wal archiver disabled
[ https://issues.apache.org/jira/browse/IGNITE-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826018#comment-16826018 ] Vyacheslav Koptilin commented on IGNITE-11699: -- Hello [~dpavlov], Could you please take a look at this PR? Additionally, I incorporated changes from IGNITE-11796. > Node can't start after forced shutdown if the wal archiver disabled > --- > > Key: IGNITE-11699 > URL: https://issues.apache.org/jira/browse/IGNITE-11699 > Project: Ignite > Issue Type: Bug > Components: persistence >Affects Versions: 2.7 >Reporter: Pavel Vinokurov >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.8 > > Attachments: disabled-wal-archive-reproducer.zip > > Time Spent: 10m > Remaining Estimate: 0h > > If a server node killed with the disabled wal archive, it could fail on start > with following exception: > {code:java} > [18:37:53,887][SEVERE][sys-stripe-1-#2][G] Failed to execute runnable. > java.lang.IllegalStateException: Failed to get page IO instance (page content > is corrupted) > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85) > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97) > at > org.apache.ignite.internal.pagemem.wal.record.delta.MetaPageUpdatePartitionDataRecord.applyDelta(MetaPageUpdatePartitionDataRecord.java:109) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyPageDelta(GridCacheDatabaseSharedManager.java:2532) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$performBinaryMemoryRestore$11(GridCacheDatabaseSharedManager.java:2327) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApplyPage$12(GridCacheDatabaseSharedManager.java:2441) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApply$13(GridCacheDatabaseSharedManager.java:2479) > at > org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550) > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at java.lang.Thread.run(Thread.java:748) > {code} > The reproducer is attached(works only on Linux). > Steps to run the reproducer. > 1. Copy config/server.xml into IGNITE_HOME/config folder; > 2. Set IGNITE_HOME in the CorruptionReproducer class; > 3. Launch CorruptionReproducer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11775) IgnitePdsWithTtlTest is flaky
[ https://issues.apache.org/jira/browse/IGNITE-11775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826020#comment-16826020 ] Vyacheslav Koptilin commented on IGNITE-11775: -- Hi [~agura], Could you please take a look at this PR? > IgnitePdsWithTtlTest is flaky > - > > Key: IGNITE-11775 > URL: https://issues.apache.org/jira/browse/IGNITE-11775 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > It seems the reason for test failure is the fact that TTL manager cannot > clean up all entries because of TTL throttling (see > {{GridCacheTtlManager#expire}} and > {{GridCacheOffheapManager.GridCacheDataStore#purgeExpired}}). It does not > seem a bug/problem, it just required to set the > {{IgniteSystemProperties.IGNITE_UNWIND_THROTTLING_TIMEOUT}} to a smaller > value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11406) NullPointerException may occur on client start
[ https://issues.apache.org/jira/browse/IGNITE-11406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11406: -- Summary: NullPointerException may occur on client start (was: NullPointerException may occurs on client start) > NullPointerException may occur on client start > -- > > Key: IGNITE-11406 > URL: https://issues.apache.org/jira/browse/IGNITE-11406 > Project: Ignite > Issue Type: Bug >Reporter: Dmitry Sherstobitov >Priority: Critical > > During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878 > # Start cluster, create caches with no persistence and load data into it > # Restart each node in cluster by order (coordinator first) > Do not wait until topology message occurs > # Try to run utilities: activate, baseline (to check that cluster is alive) > # Run clients and load data into alive caches > On 4th step one of the clients throw NPE on start > {code:java} > 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi] > Connection closed, local node received force fail message, will not try to > restore connection > 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi] > Failed to restore closed connection, will try to reconnect > [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage > [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client > node considered as unreachable and will be dropped from cluster, because no > metrics update messages received in interval: > TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by > network problems or long GC pause on client node, try to increase this > parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, > clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage > [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, > id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, > verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, > pendingIdx=0, failedNodes=null, isClient=false]]] > 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi] > Discovery notification [node=TcpDiscoveryNode > [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], > sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, > intOrder=0, lastExchangeTime=1550936128313, loc=true, > ver=2.4.15#20190222-sha1:36b1d676, isClient=true], > type=CLIENT_NODE_DISCONNECTED, topVer=166] > 2019-02-23T18:36:24,049][INFO > ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish > exchange future [startVer=AffinityTopologyVersion [topVer=165, > minorTopVer=0], resVer=null, err=class > org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client > node disconnected: null] > [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while > starting (will rollback startup routine). > java.lang.NullPointerException: null > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886) > ~[ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858) > ~[ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290) > ~[ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233) > ~[ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221) > ~[ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) > [ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973) > [ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716) > [ignite-core-2.4.15.jar:2.4.15] > at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144) > [ignite-core-2.4.15.jar:2.4.15] > at > org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1062) > [ignite-core-2.4.15.jar:2.4.15] > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:948) > [ignite-core-2.4.15.jar:2.4.15] > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847) > [ignite-core-2.4.15.jar:2.4.15] > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:717) > [ignite-core-2.4.15.jar:2.4.15] > at org.apache.ignite.
[jira] [Commented] (IGNITE-11804) Assertion error on affinity initialization
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826004#comment-16826004 ] Andrey Gura commented on IGNITE-11804: -- [~ascherbakov] Just good practice. In many cases you can understand the problem just looking to stack trace. Thanks a lot! > Assertion error on affinity initialization > -- > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and commits by > intercepting messages and releasing then > * in user defined order. > */ > public class TxPartitionCounterStateAbstractTest extends > GridCommonAbstractTest { > /** IP finder. */ > private static final TcpDiscoveryVmIpFinder IP_FINDER = new > TcpDiscoveryVmIpFinder(true); > /** */ > private static final int MB = 1024 * 1024; > /** */ > protected int backups; > /** */ > public static final int TEST_TIMEOUT = 30_000; > public static final String DEFAULT_CACHE_NAME_2 = DEFAULT_CACHE_NAME + > "2"; > /** */ > private AtomicReference testFailed = new AtomicReference<>(); > /** Number of keys to preload before txs to enable historical rebalance. > */ > protected static final int PRELOAD_KEYS_CNT = 1; > /** */ > protected static final String CLIENT_GRID_NAME = "client"; > /** */ > protected static final int PARTS_CNT = 32; > /** {@inheritDoc} */ > @Override protected IgniteConfiguration getConfiguration(String > igniteInstanceName) throws Exception { > IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName); > cfg.setConsistentId("node" + igniteInstanceName); > cfg.setFailureHandler(new StopNodeFailureHandler()); > cfg.setRebalanceThreadPoolSize(4); // Necessary to reproduce some > issues. > ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER); > // TODO set this only for historical rebalance tests. > cfg.setCommunicationSpi(new > IgniteWalRebalanceTest.WalRebalanceCheckingCommunicationSpi()); >
[jira] [Updated] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
[ https://issues.apache.org/jira/browse/IGNITE-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11784: Description: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from {{TcpDiscoveryNodesRing}} on target node. (was: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from {{TcpDiscoveryNodesRing }} on target node. ) > Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages > -- > > Key: IGNITE-11784 > URL: https://issues.apache.org/jira/browse/IGNITE-11784 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} > have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to > node attributes. We could sent only nodeId and get TcpDiscoveryNode from > {{TcpDiscoveryNodesRing}} on target node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
[ https://issues.apache.org/jira/browse/IGNITE-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11784: Description: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from {{TcpDiscoveryNodesRing }} on target node. (was: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from DiscoCache on target node. ) > Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages > -- > > Key: IGNITE-11784 > URL: https://issues.apache.org/jira/browse/IGNITE-11784 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} > have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to > node attributes. We could sent only nodeId and get TcpDiscoveryNode from > {{TcpDiscoveryNodesRing }} on target node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10281) Log to file all jars in classpath on start node.
[ https://issues.apache.org/jira/browse/IGNITE-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov reassigned IGNITE-10281: - Assignee: Denis Chudov > Log to file all jars in classpath on start node. > > > Key: IGNITE-10281 > URL: https://issues.apache.org/jira/browse/IGNITE-10281 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > > We should print all jars in classpath for analize jar's hell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
[ https://issues.apache.org/jira/browse/IGNITE-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825996#comment-16825996 ] Ilya Kasnacheev commented on IGNITE-11103: -- [~antonovsergey93] did that, please take a look. > "Control utility --cache idle_verify --dump --cache-filter ALL" comand result > doesn't contain ignite-sys-cache group > > > Key: IGNITE-11103 > URL: https://issues.apache.org/jira/browse/IGNITE-11103 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 > and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer
[ https://issues.apache.org/jira/browse/IGNITE-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11704: - Labels: rebalance (was: ) > Write tombstones during rebalance to get rid of deferred delete buffer > -- > > Key: IGNITE-11704 > URL: https://issues.apache.org/jira/browse/IGNITE-11704 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Labels: rebalance > > Currently Ignite relies on deferred delete buffer in order to handle > write-remove conflicts during rebalance. Given the limit size of the buffer, > this approach is fundamentally flawed, especially in case when persistence is > enabled. > I suggest to extend the logic of data storage to be able to store key > tombstones - to keep version for deleted entries. The tombstones will be > stored when rebalance is in progress and should be cleaned up when rebalance > is completed. > Later this approach may be used to implement fast partition rebalance based > on merkle trees (in this case, tombstones should be written on an incomplete > baseline). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11803) Re-balancing is cancelled if client node joins, reinvestigate.
[ https://issues.apache.org/jira/browse/IGNITE-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11803: - Labels: rebalance (was: ) > Re-balancing is cancelled if client node joins, reinvestigate. > -- > > Key: IGNITE-11803 > URL: https://issues.apache.org/jira/browse/IGNITE-11803 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Maxim Muzafarov >Priority: Major > Labels: rebalance > > Improvement [1] looks needs to be solved this problem, but in logs i see > different behavior. > {code:java} > 2019-04-23 15:22:56.351[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=4c9427d7-5d06-4460-98ad-6586cf177192, addrs=ArrayList [], sockAddrs= > HashSet [, discPort=0, order=159, intOrder=159, > lastExchangeTime=1556022094000, loc=false, ver=2.5.1#20190327-sha1:6edfea1b, > isClient=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Topology snapshot [ver=159, servers=, clients=1, CPUs=8848, > offheap=19.0GB, heap=4900.0GB] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Node [id=80FC83EB-F125-48F0-ACBE-8ADB80A065A3, clusterState=ACTIVE] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Baseline [id=0, size=158, online=158, offline=0] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Data Regions Configured: > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=592.0 GiB, > persistenceEnabled=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- not-persisted [initSize=256.0 MiB, maxSize=576.0 GiB, > persistenceEnabled=false] > 2019-04-23 15:22:56.356[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Started exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false, evt=NODE_JOINED, evtNode=4c9427d7-5d06 > -4460-98ad-6586cf177192, customEvt=null, allowMerge=true] > 2019-04-23 15:22:56.393[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], resVer=AffinityTopologyVersion > [topVer=159, minorTopVer=0], err=null] > 2019-04-23 15:22:56.417[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Finished exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false] > 2019-04-23 15:22:56.637[INFO > ][wal-file-archiver%DPL_GRID%DplGridNodeName-#188%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.w.FileWriteAheadLogManager] > Copied file > [src=/gridgain/ssd/data/wal/10_124_133_10_47500/0008.wal, > dst=/gridgain/sa > s/wal_archive/10_124_133_10_47500/0008.wal] > 2019-04-23 15:22:57.442[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes > [grp=SYSTEM_CACHEGROUP_DTR_union-module, topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=SYSTEM_CACHEGROUP_DTR_union-module], topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6], rebalanceId=1003, routines=3] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [grp=CACHEGROUP_SYSTEM_COMPONENT, > topVer=AffinityTopologyVersion [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.444[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=CACHEGROUP_SYSTEM_COMPONENT], topVer=AffinityTopologyVersion [ > {code} > [1] https://issues.apache.org/jira/browse/IGNITE-7165 > [~Mmuzaf] [~v.pyatkov] do u have ideas? thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11803) Re-balancing is cancelled if client node joins, reinvestigate.
[ https://issues.apache.org/jira/browse/IGNITE-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825966#comment-16825966 ] Maxim Muzafarov commented on IGNITE-11803: -- [~zstan] Thank you for the report, I'll take a look. > Re-balancing is cancelled if client node joins, reinvestigate. > -- > > Key: IGNITE-11803 > URL: https://issues.apache.org/jira/browse/IGNITE-11803 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Maxim Muzafarov >Priority: Major > Labels: rebalance > > Improvement [1] looks needs to be solved this problem, but in logs i see > different behavior. > {code:java} > 2019-04-23 15:22:56.351[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=4c9427d7-5d06-4460-98ad-6586cf177192, addrs=ArrayList [], sockAddrs= > HashSet [, discPort=0, order=159, intOrder=159, > lastExchangeTime=1556022094000, loc=false, ver=2.5.1#20190327-sha1:6edfea1b, > isClient=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Topology snapshot [ver=159, servers=, clients=1, CPUs=8848, > offheap=19.0GB, heap=4900.0GB] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Node [id=80FC83EB-F125-48F0-ACBE-8ADB80A065A3, clusterState=ACTIVE] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Baseline [id=0, size=158, online=158, offline=0] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Data Regions Configured: > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=592.0 GiB, > persistenceEnabled=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- not-persisted [initSize=256.0 MiB, maxSize=576.0 GiB, > persistenceEnabled=false] > 2019-04-23 15:22:56.356[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Started exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false, evt=NODE_JOINED, evtNode=4c9427d7-5d06 > -4460-98ad-6586cf177192, customEvt=null, allowMerge=true] > 2019-04-23 15:22:56.393[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], resVer=AffinityTopologyVersion > [topVer=159, minorTopVer=0], err=null] > 2019-04-23 15:22:56.417[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Finished exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false] > 2019-04-23 15:22:56.637[INFO > ][wal-file-archiver%DPL_GRID%DplGridNodeName-#188%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.w.FileWriteAheadLogManager] > Copied file > [src=/gridgain/ssd/data/wal/10_124_133_10_47500/0008.wal, > dst=/gridgain/sa > s/wal_archive/10_124_133_10_47500/0008.wal] > 2019-04-23 15:22:57.442[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes > [grp=SYSTEM_CACHEGROUP_DTR_union-module, topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=SYSTEM_CACHEGROUP_DTR_union-module], topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6], rebalanceId=1003, routines=3] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [grp=CACHEGROUP_SYSTEM_COMPONENT, > topVer=AffinityTopologyVersion [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.444[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=CACHEGROUP_SYSTEM_COMPONENT], topVer=AffinityTopologyVersion [ > {code} > [1] https://issues.apache.org/jira/browse/IGNITE-7165 > [~Mmuzaf] [~v.pyatkov] do u have ideas? thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11803) Re-balancing is cancelled if client node joins, reinvestigate.
[ https://issues.apache.org/jira/browse/IGNITE-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-11803: Assignee: Maxim Muzafarov > Re-balancing is cancelled if client node joins, reinvestigate. > -- > > Key: IGNITE-11803 > URL: https://issues.apache.org/jira/browse/IGNITE-11803 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Stanilovsky Evgeny >Assignee: Maxim Muzafarov >Priority: Major > > Improvement [1] looks needs to be solved this problem, but in logs i see > different behavior. > {code:java} > 2019-04-23 15:22:56.351[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Added new node to topology: TcpDiscoveryNode > [id=4c9427d7-5d06-4460-98ad-6586cf177192, addrs=ArrayList [], sockAddrs= > HashSet [, discPort=0, order=159, intOrder=159, > lastExchangeTime=1556022094000, loc=false, ver=2.5.1#20190327-sha1:6edfea1b, > isClient=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Topology snapshot [ver=159, servers=, clients=1, CPUs=8848, > offheap=19.0GB, heap=4900.0GB] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Node [id=80FC83EB-F125-48F0-ACBE-8ADB80A065A3, clusterState=ACTIVE] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- Baseline [id=0, size=158, online=158, offline=0] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] > Data Regions Configured: > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- dpl_mem_plc [initSize=256.0 MiB, maxSize=592.0 GiB, > persistenceEnabled=true] > 2019-04-23 15:22:56.353[INFO > ][disco-event-worker-#159%DPL_GRID%DplGridNodeName%][o.a.i.i.m.d.GridDiscoveryManager] >^-- not-persisted [initSize=256.0 MiB, maxSize=576.0 GiB, > persistenceEnabled=false] > 2019-04-23 15:22:56.356[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Started exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false, evt=NODE_JOINED, evtNode=4c9427d7-5d06 > -4460-98ad-6586cf177192, customEvt=null, allowMerge=true] > 2019-04-23 15:22:56.393[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture] > Finish exchange future [startVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], resVer=AffinityTopologyVersion > [topVer=159, minorTopVer=0], err=null] > 2019-04-23 15:22:56.417[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.ignite.internal.exchange.time] > Finished exchange init [topVer=AffinityTopologyVersion [topVer=159, > minorTopVer=0], crd=false] > 2019-04-23 15:22:56.637[INFO > ][wal-file-archiver%DPL_GRID%DplGridNodeName-#188%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.w.FileWriteAheadLogManager] > Copied file > [src=/gridgain/ssd/data/wal/10_124_133_10_47500/0008.wal, > dst=/gridgain/sa > s/wal_archive/10_124_133_10_47500/0008.wal] > 2019-04-23 15:22:57.442[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes > [grp=SYSTEM_CACHEGROUP_DTR_union-module, topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=SYSTEM_CACHEGROUP_DTR_union-module], topVer=AffinityTopologyVersion > [topVer=158, minorTopVer=6], rebalanceId=1003, routines=3] > 2019-04-23 15:22:57.443[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Cancelled rebalancing from all nodes [grp=CACHEGROUP_SYSTEM_COMPONENT, > topVer=AffinityTopologyVersion [topVer=158, minorTopVer=6]] > 2019-04-23 15:22:57.444[INFO > ][exchange-worker-#160%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.p.GridDhtPartitionDemander] > Completed rebalance future: RebalanceFuture [grp=CacheGroupContext > [grp=CACHEGROUP_SYSTEM_COMPONENT], topVer=AffinityTopologyVersion [ > {code} > [1] https://issues.apache.org/jira/browse/IGNITE-7165 > [~Mmuzaf] [~v.pyatkov] do u have ideas? thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
[ https://issues.apache.org/jira/browse/IGNITE-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov reassigned IGNITE-11784: --- Assignee: Sergey Antonov > Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages > -- > > Key: IGNITE-11784 > URL: https://issues.apache.org/jira/browse/IGNITE-11784 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > > {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} > have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to > node attributes. We could sent only nodeId and get TcpDiscoveryNode from > DiscoCache on target node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825947#comment-16825947 ] Sergey Antonov commented on IGNITE-11256: - Both suites are timed out in master branch too. > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825948#comment-16825948 ] Sergey Antonov commented on IGNITE-11256: - [~ascherbakov] Could you review my changes? > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[ https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825946#comment-16825946 ] Ignite TC Bot commented on IGNITE-11256: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3696981]] {color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3696983]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3688992&buildTypeId=IgniteTests24Java8_RunAll] > Implement read-only mode for grid > - > > Key: IGNITE-11256 > URL: https://issues.apache.org/jira/browse/IGNITE-11256 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Sergey Antonov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Should be triggered from control.sh utility. > Useful for maintenance work, for example checking partition consistency > (idle_verify) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11804) Assertion error on affinity initialization
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-11804: --- Summary: Assertion error on affinity initialization (was: Assertion error during assignment calculation) > Assertion error on affinity initialization > -- > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and commits by > intercepting messages and releasing then > * in user defined order. > */ > public class TxPartitionCounterStateAbstractTest extends > GridCommonAbstractTest { > /** IP finder. */ > private static final TcpDiscoveryVmIpFinder IP_FINDER = new > TcpDiscoveryVmIpFinder(true); > /** */ > private static final int MB = 1024 * 1024; > /** */ > protected int backups; > /** */ > public static final int TEST_TIMEOUT = 30_000; > public static final String DEFAULT_CACHE_NAME_2 = DEFAULT_CACHE_NAME + > "2"; > /** */ > private AtomicReference testFailed = new AtomicReference<>(); > /** Number of keys to preload before txs to enable historical rebalance. > */ > protected static final int PRELOAD_KEYS_CNT = 1; > /** */ > protected static final String CLIENT_GRID_NAME = "client"; > /** */ > protected static final int PARTS_CNT = 32; > /** {@inheritDoc} */ > @Override protected IgniteConfiguration getConfiguration(String > igniteInstanceName) throws Exception { > IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName); > cfg.setConsistentId("node" + igniteInstanceName); > cfg.setFailureHandler(new StopNodeFailureHandler()); > cfg.setRebalanceThreadPoolSize(4); // Necessary to reproduce some > issues. > ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER); > // TODO set this only for historical rebalance tests. > cfg.setCommunicationSpi(new > IgniteWalRebalanceTest.WalRebalanceCheckingCommunicationSpi()); > boolean client = igniteInstanceName.startsWith(CLIENT
[jira] [Commented] (IGNITE-11804) Assertion error on affinity initialization
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825939#comment-16825939 ] Alexei Scherbakov commented on IGNITE-11804: {noformat} java.lang.AssertionError at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedGroup(CacheAffinitySharedManager.java:1361) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.lambda$initAffinityOnCacheGroupsStart$641a38d$1(CacheAffinitySharedManager.java:1025) at org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10949) at org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10851) at org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10831) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initAffinityOnCacheGroupsStart(CacheAffinitySharedManager.java:1021) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:999) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:855) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1273) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:795) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3065) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2914) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120){noformat} > Assertion error on affinity initialization > -- > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and
[jira] [Updated] (IGNITE-11804) Assertion error during assignment calculation
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-11804: --- Summary: Assertion error during assignment calculation (was: Assertion error) > Assertion error during assignment calculation > - > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and commits by > intercepting messages and releasing then > * in user defined order. > */ > public class TxPartitionCounterStateAbstractTest extends > GridCommonAbstractTest { > /** IP finder. */ > private static final TcpDiscoveryVmIpFinder IP_FINDER = new > TcpDiscoveryVmIpFinder(true); > /** */ > private static final int MB = 1024 * 1024; > /** */ > protected int backups; > /** */ > public static final int TEST_TIMEOUT = 30_000; > public static final String DEFAULT_CACHE_NAME_2 = DEFAULT_CACHE_NAME + > "2"; > /** */ > private AtomicReference testFailed = new AtomicReference<>(); > /** Number of keys to preload before txs to enable historical rebalance. > */ > protected static final int PRELOAD_KEYS_CNT = 1; > /** */ > protected static final String CLIENT_GRID_NAME = "client"; > /** */ > protected static final int PARTS_CNT = 32; > /** {@inheritDoc} */ > @Override protected IgniteConfiguration getConfiguration(String > igniteInstanceName) throws Exception { > IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName); > cfg.setConsistentId("node" + igniteInstanceName); > cfg.setFailureHandler(new StopNodeFailureHandler()); > cfg.setRebalanceThreadPoolSize(4); // Necessary to reproduce some > issues. > ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER); > // TODO set this only for historical rebalance tests. > cfg.setCommunicationSpi(new > IgniteWalRebalanceTest.WalRebalanceCheckingCommunicationSpi()); > boolean client = igniteInstanceName.startsWith(CLIENT_GRID_NAME); >
[jira] [Commented] (IGNITE-11671) Thin client: Client may hang when connected to a starting server
[ https://issues.apache.org/jira/browse/IGNITE-11671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825935#comment-16825935 ] Amelchev Nikita commented on IGNITE-11671: -- I prepared a PR to fix this issue. Connection id (long) consists of two 32-bits parts: 1. Node order (first part 32-bits) 2. Unique identifier (int) I removed node order and make unique identifier long type. Node order was used only for assertion on dropping a connection. Moreover, this assertion fails after 2^31 attempts to connect. If node order using to generate unique connection id per cluster and 2^31 is ok (24 days with 1ms attempt to connect), I will rework fix to wait for local node initialized. Another way is to revisit the generation of connection id (For example, extend it to uuid). [~amashenkov], I see that you author of this feature. Could you take a look, please? > Thin client: Client may hang when connected to a starting server > > > Key: IGNITE-11671 > URL: https://issues.apache.org/jira/browse/IGNITE-11671 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If the server start process has not completed yet, but NIO listeners already > started, the client may never get a response for the handshake request. > Exception on the server-side: > > {noformat} > [client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%][ClientListenerProcessor] > Runtime error caught during grid runnable execution: GridWorker > [name=message-received-notify, > igniteInstanceName=f3b837aa-d726-46b0-a58b-8cc6267c9f96, finished=false, > heartbeatTs=1554209548706, hashCode=519781823, interrupted=false, > runner=client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%] > java.lang.NullPointerException > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.nextConnectionId(ClientListenerNioListener.java:334) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.prepareContext(ClientListenerNioListener.java:313) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onHandshake(ClientListenerNioListener.java:251) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:132) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:48) > at > org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279) > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109) > at > org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97) > at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at > org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70){noformat} > > This happens because NIO listeners start before {{GridDiscoveryManager}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11804) Assertion error
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825922#comment-16825922 ] Ivan Rakov commented on IGNITE-11804: - [~ascherbakov], can you change issue summary to something that describes what is broken? "Assertion Error" is definitely not enough to understand what's going on. > Assertion error > --- > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and commits by > intercepting messages and releasing then > * in user defined order. > */ > public class TxPartitionCounterStateAbstractTest extends > GridCommonAbstractTest { > /** IP finder. */ > private static final TcpDiscoveryVmIpFinder IP_FINDER = new > TcpDiscoveryVmIpFinder(true); > /** */ > private static final int MB = 1024 * 1024; > /** */ > protected int backups; > /** */ > public static final int TEST_TIMEOUT = 30_000; > public static final String DEFAULT_CACHE_NAME_2 = DEFAULT_CACHE_NAME + > "2"; > /** */ > private AtomicReference testFailed = new AtomicReference<>(); > /** Number of keys to preload before txs to enable historical rebalance. > */ > protected static final int PRELOAD_KEYS_CNT = 1; > /** */ > protected static final String CLIENT_GRID_NAME = "client"; > /** */ > protected static final int PARTS_CNT = 32; > /** {@inheritDoc} */ > @Override protected IgniteConfiguration getConfiguration(String > igniteInstanceName) throws Exception { > IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName); > cfg.setConsistentId("node" + igniteInstanceName); > cfg.setFailureHandler(new StopNodeFailureHandler()); > cfg.setRebalanceThreadPoolSize(4); // Necessary to reproduce some > issues. > ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER); > // TODO set this only for historical rebalance tests. > cfg.setCommunicationSpi(new > IgniteWalRebalanceTest.WalRebalanceCheckingCommunicationSpi()); > boolean cl
[jira] [Assigned] (IGNITE-11697) Suspended optimistic transaction automatically resumes to last thread after a timeout.
[ https://issues.apache.org/jira/browse/IGNITE-11697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov reassigned IGNITE-11697: -- Assignee: Aleksey Plekhanov > Suspended optimistic transaction automatically resumes to last thread after a > timeout. > -- > > Key: IGNITE-11697 > URL: https://issues.apache.org/jira/browse/IGNITE-11697 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-34 > > This leads to unpredictable results from a user's point of view. > Reproducer: > > {code:java} > public class IgniteTxSuspendAndTimeoutTest extends GridCommonAbstractTest { > @Test > public void testSuspendAndTimeout() throws Exception { > Ignite ignite = startGrid(0); > IgniteCache cache = ignite.createCache(new > CacheConfiguration<>().setName("c").setAtomicityMode(TRANSACTIONAL)); > Transaction tx1 = ignite.transactions().txStart(OPTIMISTIC, > TransactionIsolation.REPEATABLE_READ, 100, 0); > cache.put(1, 1); > tx1.suspend(); > assertNull(cache.get(1)); // Pass here. > doSleep(200); > assertNull(cache.get(1)); // Fail here. But we don't expect any > explicitly running transaction at this point. > } > } > {code} > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11624) Discovery SPI: The client can handle events from the previous cluster after reconnect.
[ https://issues.apache.org/jira/browse/IGNITE-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825911#comment-16825911 ] Amelchev Nikita edited comment on IGNITE-11624 at 4/25/19 9:42 AM: --- [~akalashnikov] Thank you for review. I have answered in the upsource. Check it, please. was (Author: nsamelchev): [~akalashnikov] Thank you for taking a look. I have answered in the upsource. Check it, please. > Discovery SPI: The client can handle events from the previous cluster after > reconnect. > -- > > Key: IGNITE-11624 > URL: https://issues.apache.org/jira/browse/IGNITE-11624 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Discovery has a queue for events. It's processed by event thread. If we hold > up event processing using a listener on the client side and restarts cluster > - the client will reconnect. After it reconnects it will continue processing > events from the previous cluster. > This behavior produces bugs in MvccProcessor (IGNITE-11460) and [hanging of > partitions exchange|https://github.com/NSAmelchev/ignite/pull/26/files] on > the client side. The reason is that discovery notifies components about > reconnection in the notifier thread by calling the 'onLocalJoin' method. > After it (or at the same time), components can process events from the > previous cluster in their listeners and break their logic. > The order of events is fine - after processing previous cluster events - it > will process client disconnection/reconnection and new cluster events. > The possible solution is to fix discovery logic. Make a guarantee that no one > event from the previous cluster will be processed after the client reconnect > ('onLocalJoin' called). For example, wait for the client disconnect event > will be processed in the discovery event thread. Then start attempt to > reconnect. > [Dev-list > discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/The-client-can-handle-events-from-the-previous-cluster-after-reconnect-td41392.html] > [Reproducer.|https://github.com/NSAmelchev/ignite/pull/26/files] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11624) Discovery SPI: The client can handle events from the previous cluster after reconnect.
[ https://issues.apache.org/jira/browse/IGNITE-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825911#comment-16825911 ] Amelchev Nikita commented on IGNITE-11624: -- [~akalashnikov] Thank you for taking a look. I have answered in the upsource. Check it, please. > Discovery SPI: The client can handle events from the previous cluster after > reconnect. > -- > > Key: IGNITE-11624 > URL: https://issues.apache.org/jira/browse/IGNITE-11624 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Discovery has a queue for events. It's processed by event thread. If we hold > up event processing using a listener on the client side and restarts cluster > - the client will reconnect. After it reconnects it will continue processing > events from the previous cluster. > This behavior produces bugs in MvccProcessor (IGNITE-11460) and [hanging of > partitions exchange|https://github.com/NSAmelchev/ignite/pull/26/files] on > the client side. The reason is that discovery notifies components about > reconnection in the notifier thread by calling the 'onLocalJoin' method. > After it (or at the same time), components can process events from the > previous cluster in their listeners and break their logic. > The order of events is fine - after processing previous cluster events - it > will process client disconnection/reconnection and new cluster events. > The possible solution is to fix discovery logic. Make a guarantee that no one > event from the previous cluster will be processed after the client reconnect > ('onLocalJoin' called). For example, wait for the client disconnect event > will be processed in the discovery event thread. Then start attempt to > reconnect. > [Dev-list > discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/The-client-can-handle-events-from-the-previous-cluster-after-reconnect-td41392.html] > [Reproducer.|https://github.com/NSAmelchev/ignite/pull/26/files] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11671) Thin client: Client may hang when connected to a starting server
[ https://issues.apache.org/jira/browse/IGNITE-11671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825906#comment-16825906 ] Ignite TC Bot commented on IGNITE-11671: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3696991]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3689239&buildTypeId=IgniteTests24Java8_RunAll] > Thin client: Client may hang when connected to a starting server > > > Key: IGNITE-11671 > URL: https://issues.apache.org/jira/browse/IGNITE-11671 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Aleksey Plekhanov >Assignee: Amelchev Nikita >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If the server start process has not completed yet, but NIO listeners already > started, the client may never get a response for the handshake request. > Exception on the server-side: > > {noformat} > [client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%][ClientListenerProcessor] > Runtime error caught during grid runnable execution: GridWorker > [name=message-received-notify, > igniteInstanceName=f3b837aa-d726-46b0-a58b-8cc6267c9f96, finished=false, > heartbeatTs=1554209548706, hashCode=519781823, interrupted=false, > runner=client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%] > java.lang.NullPointerException > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.nextConnectionId(ClientListenerNioListener.java:334) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.prepareContext(ClientListenerNioListener.java:313) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onHandshake(ClientListenerNioListener.java:251) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:132) > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:48) > at > org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279) > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109) > at > org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97) > at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at > org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70){noformat} > > This happens because NIO listeners start before {{GridDiscoveryManager}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11624) Discovery SPI: The client can handle events from the previous cluster after reconnect.
[ https://issues.apache.org/jira/browse/IGNITE-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825880#comment-16825880 ] Anton Kalashnikov commented on IGNITE-11624: [~NSAmelchev] thanks for your changes. I left one comment into upsource(https://reviews.ignite.apache.org/ignite/review/IGNT-CR-1033?filePath=/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java). Can you check it out? > Discovery SPI: The client can handle events from the previous cluster after > reconnect. > -- > > Key: IGNITE-11624 > URL: https://issues.apache.org/jira/browse/IGNITE-11624 > Project: Ignite > Issue Type: Bug >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Discovery has a queue for events. It's processed by event thread. If we hold > up event processing using a listener on the client side and restarts cluster > - the client will reconnect. After it reconnects it will continue processing > events from the previous cluster. > This behavior produces bugs in MvccProcessor (IGNITE-11460) and [hanging of > partitions exchange|https://github.com/NSAmelchev/ignite/pull/26/files] on > the client side. The reason is that discovery notifies components about > reconnection in the notifier thread by calling the 'onLocalJoin' method. > After it (or at the same time), components can process events from the > previous cluster in their listeners and break their logic. > The order of events is fine - after processing previous cluster events - it > will process client disconnection/reconnection and new cluster events. > The possible solution is to fix discovery logic. Make a guarantee that no one > event from the previous cluster will be processed after the client reconnect > ('onLocalJoin' called). For example, wait for the client disconnect event > will be processed in the discovery event thread. Then start attempt to > reconnect. > [Dev-list > discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/The-client-can-handle-events-from-the-previous-cluster-after-reconnect-td41392.html] > [Reproducer.|https://github.com/NSAmelchev/ignite/pull/26/files] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8578) .NET: Add baseline auto-adjust parameters (definition, run-time change)
[ https://issues.apache.org/jira/browse/IGNITE-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-8578: --- Fix Version/s: 2.8 > .NET: Add baseline auto-adjust parameters (definition, run-time change) > --- > > Key: IGNITE-8578 > URL: https://issues.apache.org/jira/browse/IGNITE-8578 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Eduard Shangareev >Assignee: Alexandr Shapkin >Priority: Major > Labels: .NET, IEP-4, Phase-2 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We would introduce at IGNITE-8571 new parameters. > We need their support in .Net side. > See new methods on IgniteCluster interface IGNITE-11509 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11804) Assertion error
[ https://issues.apache.org/jira/browse/IGNITE-11804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825845#comment-16825845 ] Alexei Scherbakov commented on IGNITE-11804: [~agura] Doesn't the reproducer work for you ? > Assertion error > --- > > Key: IGNITE-11804 > URL: https://issues.apache.org/jira/browse/IGNITE-11804 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Priority: Major > > Reproducer (needs some cleanup) > {noformat} > /* > * Licensed to the Apache Software Foundation (ASF) under one or more > * contributor license agreements. See the NOTICE file distributed with > * this work for additional information regarding copyright ownership. > * The ASF licenses this file to You under the Apache License, Version 2.0 > * (the "License"); you may not use this file except in compliance with > * the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > package org.apache.ignite.internal.processors.cache.transactions; > import java.util.ArrayList; > import java.util.List; > import java.util.concurrent.atomic.AtomicReference; > import org.apache.ignite.Ignite; > import org.apache.ignite.IgniteCache; > import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction; > import org.apache.ignite.configuration.CacheConfiguration; > import org.apache.ignite.configuration.DataRegionConfiguration; > import org.apache.ignite.configuration.DataStorageConfiguration; > import org.apache.ignite.configuration.IgniteConfiguration; > import org.apache.ignite.failure.StopNodeFailureHandler; > import org.apache.ignite.internal.IgniteEx; > import org.apache.ignite.internal.processors.cache.GridCacheContext; > import org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl; > import > org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest; > import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi; > import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder; > import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest; > import org.apache.ignite.transactions.Transaction; > import org.junit.Test; > import static java.util.concurrent.TimeUnit.DAYS; > import static java.util.concurrent.TimeUnit.MILLISECONDS; > import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL; > import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC; > import static org.apache.ignite.configuration.WALMode.LOG_ONLY; > import static > org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC; > import static > org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ; > /** > * Test framework for ordering transaction's prepares and commits by > intercepting messages and releasing then > * in user defined order. > */ > public class TxPartitionCounterStateAbstractTest extends > GridCommonAbstractTest { > /** IP finder. */ > private static final TcpDiscoveryVmIpFinder IP_FINDER = new > TcpDiscoveryVmIpFinder(true); > /** */ > private static final int MB = 1024 * 1024; > /** */ > protected int backups; > /** */ > public static final int TEST_TIMEOUT = 30_000; > public static final String DEFAULT_CACHE_NAME_2 = DEFAULT_CACHE_NAME + > "2"; > /** */ > private AtomicReference testFailed = new AtomicReference<>(); > /** Number of keys to preload before txs to enable historical rebalance. > */ > protected static final int PRELOAD_KEYS_CNT = 1; > /** */ > protected static final String CLIENT_GRID_NAME = "client"; > /** */ > protected static final int PARTS_CNT = 32; > /** {@inheritDoc} */ > @Override protected IgniteConfiguration getConfiguration(String > igniteInstanceName) throws Exception { > IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName); > cfg.setConsistentId("node" + igniteInstanceName); > cfg.setFailureHandler(new StopNodeFailureHandler()); > cfg.setRebalanceThreadPoolSize(4); // Necessary to reproduce some > issues. > ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER); > // TODO set this only for historical rebalance tests. > cfg.setCommunicationSpi(new > IgniteWalRebalanceTest.WalRebalanceCheckingCommunicationSpi()); > boolean client = igniteInstanceName.startsWith(CLIENT_GRID_NAME); > cfg.setClientMode(client); >
[jira] [Commented] (IGNITE-11470) Views don't show in Dbeaver
[ https://issues.apache.org/jira/browse/IGNITE-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825844#comment-16825844 ] Ignite TC Bot commented on IGNITE-11470: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3688467]] {color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3688471]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3679731&buildTypeId=IgniteTests24Java8_RunAll] > Views don't show in Dbeaver > --- > > Key: IGNITE-11470 > URL: https://issues.apache.org/jira/browse/IGNITE-11470 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > Fix For: 2.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > At Database navigator tab we can see no a views. As of now we should see at > least SQL system views. -- This message was sent by Atlassian JIRA (v7.6.3#76005)