[jira] [Created] (IGNITE-14621) Ignite Extensions: change spring-data-*-ext modules names to align with a directory name
Amelchev Nikita created IGNITE-14621: Summary: Ignite Extensions: change spring-data-*-ext modules names to align with a directory name Key: IGNITE-14621 URL: https://issues.apache.org/jira/browse/IGNITE-14621 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Change the following modules names: {{ignite-spring-data_2.2-ext}} {{ignite-spring-data_2.0-ext}} on {{ignite-spring-data-2.2-ext}} {{ignite-spring-data-2.0-ext}} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14570) Ignite Extensions: Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler
Amelchev Nikita created IGNITE-14570: Summary: Ignite Extensions: Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler Key: IGNITE-14570 URL: https://issues.apache.org/jira/browse/IGNITE-14570 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler to fix compilation after [IGNITE-14385|https://issues.apache.org/jira/browse/IGNITE-14385]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14568) Add LICENSE and NOTICE files to release package of performance-statistics-ext extension
Amelchev Nikita created IGNITE-14568: Summary: Add LICENSE and NOTICE files to release package of performance-statistics-ext extension Key: IGNITE-14568 URL: https://issues.apache.org/jira/browse/IGNITE-14568 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14480) Add release notes for performance-statistics-ext, spring-data*-ext, spring-tx-ext extensions 1.0.0 version
Amelchev Nikita created IGNITE-14480: Summary: Add release notes for performance-statistics-ext, spring-data*-ext, spring-tx-ext extensions 1.0.0 version Key: IGNITE-14480 URL: https://issues.apache.org/jira/browse/IGNITE-14480 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14456) Ignite Extensions: change copyrights to 2021
Amelchev Nikita created IGNITE-14456: Summary: Ignite Extensions: change copyrights to 2021 Key: IGNITE-14456 URL: https://issues.apache.org/jira/browse/IGNITE-14456 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita The copyrights must be changed to 2021. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14433) Update README file for the performance statistics extension
Amelchev Nikita created IGNITE-14433: Summary: Update README file for the performance statistics extension Key: IGNITE-14433 URL: https://issues.apache.org/jira/browse/IGNITE-14433 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Document the {{print-statistics.sh}} script. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14417) Document performance-statistics-ext module
Amelchev Nikita created IGNITE-14417: Summary: Document performance-statistics-ext module Key: IGNITE-14417 URL: https://issues.apache.org/jira/browse/IGNITE-14417 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita It's needed to document performance-statistics-ext module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14191) Add command to control.(sh|bin) to manage performance statistics
Amelchev Nikita created IGNITE-14191: Summary: Add command to control.(sh|bin) to manage performance statistics Key: IGNITE-14191 URL: https://issues.apache.org/jira/browse/IGNITE-14191 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.11 Add command to control.(sh|bin) to manage performance statistics: {noformat} --perf-stat [start|stop|started] {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13984) Provide the ability to collect Services performance statistics
Amelchev Nikita created IGNITE-13984: Summary: Provide the ability to collect Services performance statistics Key: IGNITE-13984 URL: https://issues.apache.org/jira/browse/IGNITE-13984 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability to collect Services performance statistics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13983) Provide the ability to collect CQ performance statistics
Amelchev Nikita created IGNITE-13983: Summary: Provide the ability to collect CQ performance statistics Key: IGNITE-13983 URL: https://issues.apache.org/jira/browse/IGNITE-13983 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability to collect CQ performance statistics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13982) Add documentation for new checkpoint, cluster and cache metrics
Amelchev Nikita created IGNITE-13982: Summary: Add documentation for new checkpoint, cluster and cache metrics Key: IGNITE-13982 URL: https://issues.apache.org/jira/browse/IGNITE-13982 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.10 Add documentation for new metrics: * LastCheckpointbeforeLockDuration * LastCheckpointListenersExecuteDuration * LastCheckpointLockHoldDuration * LastCheckpointWalCpRecordFsyncDuration * LastCheckpointWriteCheckpointEntryDuration * LastCheckpointSplitAndSortPagesDuration * CheckpointBeforeLockHistogram * CheckpointLockWaitHistogram * CheckpointListenersExecuteHistogram * CheckpointMarkHistogram * CheckpointLockHoldHistogram * CheckpointPagesWriteHistogram * CheckpointFsyncHistogram * CheckpointWalRecordFsyncHistogram * CheckpointWriteEntryHistogram * CheckpointSplitAndSortPagesHistogram * CheckpointHistogram * TopologyVersion * TotalNodes * TotalBaselineNodes * TotalServerNodes * TotalClientNodes * ActiveBaselineNodes * OffHeapEntriesCount * OffHeapBackupEntriesCount * OffHeapPrimaryEntriesCount * HeapEntriesCount * CacheSize -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13893) Optimize memory usage on export performance statistics to JSON
Amelchev Nikita created IGNITE-13893: Summary: Optimize memory usage on export performance statistics to JSON Key: IGNITE-13893 URL: https://issues.apache.org/jira/browse/IGNITE-13893 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Optimize memory usage on export performance statistics to JSON -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13892) Improve log message of start/stop performance statistics collection
Amelchev Nikita created IGNITE-13892: Summary: Improve log message of start/stop performance statistics collection Key: IGNITE-13892 URL: https://issues.apache.org/jira/browse/IGNITE-13892 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Improve log message of start/stop performance statistics collection -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13890) Remove zip-file with web-resources from the jar
Amelchev Nikita created IGNITE-13890: Summary: Remove zip-file with web-resources from the jar Key: IGNITE-13890 URL: https://issues.apache.org/jira/browse/IGNITE-13890 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Remove zip-file with web-resources from the jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13891) Provide the ability to configure performance report
Amelchev Nikita created IGNITE-13891: Summary: Provide the ability to configure performance report Key: IGNITE-13891 URL: https://issues.apache.org/jira/browse/IGNITE-13891 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Provide the ability to configure performance report: - maximum top slow operations - histograms bounds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13889) Remove web-resources from the source of the performance report
Amelchev Nikita created IGNITE-13889: Summary: Remove web-resources from the source of the performance report Key: IGNITE-13889 URL: https://issues.apache.org/jira/browse/IGNITE-13889 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Remove web-resources from the source of the performance report -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13888) Provide the utility to output performance statistics operations to the console
Amelchev Nikita created IGNITE-13888: Summary: Provide the utility to output performance statistics operations to the console Key: IGNITE-13888 URL: https://issues.apache.org/jira/browse/IGNITE-13888 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Provide the utility to output performance statistics operations to the console (to integrate with the other cmd tools) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13861) Add logical/physical reads checks to existing tests
Amelchev Nikita created IGNITE-13861: Summary: Add logical/physical reads checks to existing tests Key: IGNITE-13861 URL: https://issues.apache.org/jira/browse/IGNITE-13861 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add logical/physical reads checks to existing tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13860) Provide the tool to build cluster performance report
Amelchev Nikita created IGNITE-13860: Summary: Provide the tool to build cluster performance report Key: IGNITE-13860 URL: https://issues.apache.org/jira/browse/IGNITE-13860 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the tool to build cluster performance report -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13854) Add documentation for the cluster performance profiling tool
Amelchev Nikita created IGNITE-13854: Summary: Add documentation for the cluster performance profiling tool Key: IGNITE-13854 URL: https://issues.apache.org/jira/browse/IGNITE-13854 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add documentation for the cluster performance profiling tool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13850) Improve the TracingSpi interface
Amelchev Nikita created IGNITE-13850: Summary: Improve the TracingSpi interface Key: IGNITE-13850 URL: https://issues.apache.org/jira/browse/IGNITE-13850 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Assignee: Amelchev Nikita Need to investigate and improve the TracingSpi interface: 1. Add support for non-strings tags and log points: primitives, arrays etc 2. Add ability to postpone adding span tags and log points 3. Investigate ability to cache some tags -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13845) Add checkpoint lock hold metrics
Amelchev Nikita created IGNITE-13845: Summary: Add checkpoint lock hold metrics Key: IGNITE-13845 URL: https://issues.apache.org/jira/browse/IGNITE-13845 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add last checkpoint lock hold duration and durations histogram metrics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13741) NPE on client reconnect with static caches configured
Amelchev Nikita created IGNITE-13741: Summary: NPE on client reconnect with static caches configured Key: IGNITE-13741 URL: https://issues.apache.org/jira/browse/IGNITE-13741 Project: Ignite Issue Type: Bug Affects Versions: 2.8.1 Reporter: Amelchev Nikita There was NPE during the client node reconnect to the cluster. 1. Configure static replicated persisted cache. 2. Start 2 server nodes and 1 client node. Activate the cluster and fill the cache with any values. 3. Restart all servers. 4. When client reconnected it throws the exception from {{CacheAffinitySharedManager#processClientCachesRequests}}: {noformat} // Get ready exchange version. AffinityTopologyVersion topVer = cctx.exchange().readyAffinityVersion(); DiscoCache discoCache = cctx.discovery().discoCache(topVer); // discoCache was null ClusterNode node = discoCache.oldestAliveServerNode(); {noformat} {noformat} 2020-11-17 17:22:59.471 [INFO ][exchange-worker-#65][org.apache.ignite.internal.processors.cache.GridCacheProcessor] Stopped cache [cacheName=test-persist-partitioned-atomic-cache] 2020-11-17 17:22:59.472 [WARN ][tcp-client-disco-msg-worker-#4][org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi] Client node was reconnected after it was already considered failed by the server topology (this could happen after all servers restarted or due to a long network outage between the client and servers). All continuous queries and remote event listeners created by this client will be unsubscribed, consider listening to EVT_CLIENT_NODE_RECONNECTED event to restore them. 2020-11-17 17:22:59.473 [INFO ][sys-#56][org.apache.ignite.internal.processors.cluster.ClusterProcessor] Writing cluster ID and tag to metastorage on ready for write ClusterIdAndTag [id=b4d4e0b1-23ca-4399-bf0d-5238bb42eccb, tag=admiring_herschel] 2020-11-17 17:22:59.473 [INFO ][disco-event-worker-#52][org.apache.ignite.internal.managers.discovery.GridDiscoveryManager] Client node reconnected to topology: TcpDiscoveryNode [id=9864d053-9100-4ab1-892b-540f19b30c32, consistentId=Example_3, addrs=ArrayList [*], sockAddrs=HashSet [*], discPort=0, order=2, intOrder=0, lastExchangeTime=1605622970162, loc=true, ver=2.8.1, isClient=true] 2020-11-17 17:22:59.474 [INFO ][disco-event-worker-#52][org.apache.ignite.internal.managers.discovery.GridDiscoveryManager] Topology snapshot [ver=2, locNode=9864d053, servers=1, clients=1, state=ACTIVE, CPUs=8, offheap=4.0GB, heap=6.9GB] 2020-11-17 17:22:59.474 [INFO ][disco-event-worker-#52][org.apache.ignite.internal.managers.discovery.GridDiscoveryManager] ^-- Baseline [id=0, size=2, online=1, offline=1] 2020-11-17 17:22:59.476 [INFO ][disco-notifier-worker-#50][org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor] Received state change finish message: true 2020-11-17 17:22:59.477 [ERROR][exchange-worker-#65][org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager] Failed to process custom exchange task: ClientCacheChangeDummyDiscoveryMessage [reqId=9eb245bd-5cdc-4d13-8eac-9e7c7585c83f, cachesToClose=null, startCaches= [test-persist-partitioned-atomic-cache]] java.lang.NullPointerException: null at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesRequests(CacheAffinitySharedManager.java:666) ~[ignite-core-2.8.1.jar:2.8.1] at org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:408) ~[ignite-core-2.8.1.jar:2.8.1] at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:2997) [ignite-core-2.8.1.jar:2.8.1] at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3145) [ignite-core-2.8.1.jar:2.8.1] at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3063) [ignite-core-2.8.1.jar:2.8.1] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) [ignite-core-2.8.1.jar:2.8.1] at java.lang.Thread.run(Thread.java:748) 2020-11-17 17:22:59.479 [INFO ][exchange-worker-#65][org.apache.ignite.internal.exchange.time] Started exchange init [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], crd=false, evt=NODE_JOINED, evtNode=9864d053-9100-4ab1-892b-540f19b30c32, customEvt=null, allowMerge=true, exchangeFreeSwitch=false] {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13583) Check current master key digest on key change request
Amelchev Nikita created IGNITE-13583: Summary: Check current master key digest on key change request Key: IGNITE-13583 URL: https://issues.apache.org/jira/browse/IGNITE-13583 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Need to check the current master key digest on the key change request. Concurrent key change produces unclear reject message in case: 1. The first thread creates a request but not send to the cluster. A request contains an encrypted MK name. 2. The second thread performs MK change. The cluster set a new MK. 3. The first thread sends a request but the cluster can't decrypt MK name under the new MK. The change request will be rejected with the message: {noformat} class org.apache.ignite.IgniteException: Master key change was rejected [nodeId=00e9fe88-d0c3-430a-93f4-27341ee8a000] at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.prepareMasterKeyChange(GridEncryptionManager.java:1044) at org.apache.ignite.internal.util.distributed.DistributedProcess.lambda$new$2(DistributedProcess.java:149) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:722) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:531) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2696) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2734) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.IgniteException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.withMasterKeyChangeReadLock(GridEncryptionManager.java:1185) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.decryptKeyName(GridEncryptionManager.java:1251) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.prepareMasterKeyChange(GridEncryptionManager.java:1029) ... 7 more Caused by: class org.apache.ignite.spi.IgniteSpiException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. at org.apache.ignite.spi.encryption.keystore.KeystoreEncryptionSpi.decrypt(KeystoreEncryptionSpi.java:209) at org.apache.ignite.spi.encryption.keystore.KeystoreEncryptionSpi.decryptKey(KeystoreEncryptionSpi.java:280) at org.apache.ignite.spi.encryption.keystore.KeystoreEncryptionSpi.decryptKey(KeystoreEncryptionSpi.java:64) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.lambda$decryptKeyName$10(GridEncryptionManager.java:1264) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.withMasterKeyChangeReadLock(GridEncryptionManager.java:1182) ... 9 more Caused by: javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. at com.sun.crypto.provider.CipherCore.unpad(CipherCore.java:975) at com.sun.crypto.provider.CipherCore.fillOutputBuffer(CipherCore.java:1056) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:853) at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at javax.crypto.Cipher.doFinal(Cipher.java:) at org.apache.ignite.spi.encryption.keystore.KeystoreEncryptionSpi.decrypt(KeystoreEncryptionSpi.java:205) ... 13 more {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13567) TcpDiscoverySpi: incorrect value of the joiningNodeClient flag for the joining client
Amelchev Nikita created IGNITE-13567: Summary: TcpDiscoverySpi: incorrect value of the joiningNodeClient flag for the joining client Key: IGNITE-13567 URL: https://issues.apache.org/jira/browse/IGNITE-13567 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita The TcpDiscoverySpi sets incorrect value of the {{joiningNodeClient}} flag for the joining client: - local client node on join gets {{false}} - all nodes gets {{true}} See {{DiscoverySpiDataExchange}} and {{DiscoveryDataBag#isJoiningNodeClient()}}. In the ZookepeerSpi the flag is correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13451) Provide the ability to set up default performance statistics properties
Amelchev Nikita created IGNITE-13451: Summary: Provide the ability to set up default performance statistics properties Key: IGNITE-13451 URL: https://issues.apache.org/jira/browse/IGNITE-13451 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability to set up default performance statistics properties: - DFLT_FILE_MAX_SIZE - DFLT_BUFFER_SIZE - DFLT_FLUSH_SIZE - DFLT_MAX_CACHED_STRINGS_COUNT -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13452) Create a new performance statistics file instead of deleting the existing
Amelchev Nikita created IGNITE-13452: Summary: Create a new performance statistics file instead of deleting the existing Key: IGNITE-13452 URL: https://issues.apache.org/jira/browse/IGNITE-13452 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Create a new performance statistics file instead of deleting the existing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13427) The local metastorage system view fails if unmarshallable values present
Amelchev Nikita created IGNITE-13427: Summary: The local metastorage system view fails if unmarshallable values present Key: IGNITE-13427 URL: https://issues.apache.org/jira/browse/IGNITE-13427 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita The local metastorage allow to write raw data. For example, distributed megastore writes it: {noformat} metastorage.writeRaw(cleanupGuardKey(), DUMMY_VALUE); {noformat} System view iterator fails on such entries: {noformat} [2020-09-10 14:34:37,556][WARN ][test-runner-#1%metric.SystemViewSelfTest%][GridCacheDatabaseSharedManager] Metastore iteration error class org.apache.ignite.IgniteCheckedException: Failed to deserialize object with given class loader: sun.misc.Launcher$AppClassLoader@18b4aac2 at org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:132) at org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:139) at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:80) at org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.applyCallback(MetaStorage.java:387) at org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.iterate(MetaStorage.java:359) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$registerSystemView$1(GridCacheDatabaseSharedManager.java:415) at org.apache.ignite.internal.managers.systemview.SystemViewAdapter.iterator(SystemViewAdapter.java:82) at org.apache.ignite.internal.util.lang.GridFunc.find(GridFunc.java:2068) at org.apache.ignite.internal.metric.SystemViewSelfTest.testMetastorage(SystemViewSelfTest.java:1155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2373) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13380) Output IgniteSystemProperties via ignite.sh
Amelchev Nikita created IGNITE-13380: Summary: Output IgniteSystemProperties via ignite.sh Key: IGNITE-13380 URL: https://issues.apache.org/jira/browse/IGNITE-13380 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability output of all available Ignite properties (`IgniteSystemProperties`) with its descriptions in the `ignite.sh` command. For example, `ignite.sh -systemProps`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13252) Provide the ability to cache strings
Amelchev Nikita created IGNITE-13252: Summary: Provide the ability to cache strings Key: IGNITE-13252 URL: https://issues.apache.org/jira/browse/IGNITE-13252 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Strings that performance statistics writes can be cached with id. It will reduce affect on performance. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13227) AssertionError on getting cache size from the mbean on the inactive cluster
Amelchev Nikita created IGNITE-13227: Summary: AssertionError on getting cache size from the mbean on the inactive cluster Key: IGNITE-13227 URL: https://issues.apache.org/jira/browse/IGNITE-13227 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The reproducer for {{CacheMetricsManageTest}}: {noformat} /** @throws Exception If failed. */ @Test public void testCacheSize() throws Exception { persistence = true; startGrid(0); CacheMetricsMXBean mxBean = mxBean(0, CACHE1, CacheClusterMetricsMXBeanImpl.class); long size = mxBean.getCacheSize(); assertEquals(0, size); } {noformat} AssertionError: {noformat} java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0] at org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:794) at org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:771) at org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:697) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheData(IgniteCacheOffheapManagerImpl.java:431) at org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:398) at org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.localSizeLong(GridDistributedCacheAdapter.java:284) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.localSize(GridCacheAdapter.java:4151) at org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getEntriesStat(CacheMetricsImpl.java:1272) at org.apache.ignite.internal.processors.cache.CacheMetricsSnapshotV2.(CacheMetricsSnapshotV2.java:375) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3546) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.clusterMetrics(GridCacheAdapter.java:3540) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.clusterMetrics(GridCacheAdapter.java:3522) at org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl.getCacheSize(CacheClusterMetricsMXBeanImpl.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.getAttribute(PerInterface.java:83) at com.sun.jmx.mbeanserver.MBeanSupport.getAttribute(MBeanSupport.java:206) at javax.management.StandardMBean.getAttribute(StandardMBean.java:372) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647) at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273) at com.sun.proxy.$Proxy30.getCacheSize(Unknown Source) at org.apache.ignite.internal.processors.cache.CacheMetricsManageTest.testCacheSize(CacheMetricsManageTest.java:833) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosiv
[jira] [Created] (IGNITE-13218) System view walker generator wrong sorts imports
Amelchev Nikita created IGNITE-13218: Summary: System view walker generator wrong sorts imports Key: IGNITE-13218 URL: https://issues.apache.org/jira/browse/IGNITE-13218 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita {{SystemViewRowAttributeWalkerGenerator}} wrong sorts imports. 1. Run SystemViewRowAttributeWalkerGenerator 2. Run check codestyle to occurs error: {noformat} ComputeJobViewWalker.java:23: Wrong lexicographical order for 'org.apache.ignite.spi.systemview.view.ComputeJobView' import. Should be before 'org.apache.ignite.spi.systemview.view.ComputeJobView.ComputeJobState'. [CustomImportOrder] Audit done. {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13150) Provide the ability to profile only specific operations
Amelchev Nikita created IGNITE-13150: Summary: Provide the ability to profile only specific operations Key: IGNITE-13150 URL: https://issues.apache.org/jira/browse/IGNITE-13150 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability to profile only specific operations. For example: {noformat} startProfiling(CACHE_OPERATION, TRANSACTION) {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13115) Master key name can't be changed if Unicode symbols present
Amelchev Nikita created IGNITE-13115: Summary: Master key name can't be changed if Unicode symbols present Key: IGNITE-13115 URL: https://issues.apache.org/jira/browse/IGNITE-13115 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The master key name can't be changed if Unicode symbols present. The reason is the wrong key name length calculation. {noformat} [2020-06-03 18:43:35,289][ERROR][disco-notifier-worker-#84%grid-1%][IgniteTestResources] Critical system error detected. Will be handled accordingly to configured handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext [type=CRITICAL_ERROR, err=class o.a.i.i.processors.cache.persistence.StorageException: Unable to write]] class org.apache.ignite.internal.processors.cache.persistence.StorageException: Unable to write at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.flush(FsyncFileWriteHandle.java:476) at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.flush(FsyncFileWriteHandle.java:404) at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.flushOrWait(FsyncFileWriteHandle.java:344) at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.fsync(FsyncFileWriteHandle.java:586) at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileHandleManagerImpl.flush(FsyncFileHandleManagerImpl.java:167) at org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.flush(FileWriteAheadLogManager.java:903) at org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.writeRaw(MetaStorage.java:438) at org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.write(MetaStorage.java:401) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.writeKeysToMetaStore(GridEncryptionManager.java:822) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.doChangeMasterKey(GridEncryptionManager.java:956) at org.apache.ignite.internal.managers.encryption.GridEncryptionManager.performMasterKeyChange(GridEncryptionManager.java:1086) at org.apache.ignite.internal.util.distributed.DistributedProcess.lambda$new$2(DistributedProcess.java:148) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:732) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:533) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2641) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2679) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: java.lang.IllegalStateException: Failed to write record: WALRecord [size=418, chainSize=418, pos=FileWALPointer [idx=0, fileOff=402386, len=418], type=MASTER_KEY_CHANGE_RECORD] ... 18 more Caused by: java.lang.IllegalStateException: Failed to write record: WALRecord [size=418, chainSize=418, pos=FileWALPointer [idx=0, fileOff=402386, len=418], type=MASTER_KEY_CHANGE_RECORD] at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.fillBuffer(FsyncFileWriteHandle.java:512) at org.apache.ignite.internal.processors.cache.persistence.wal.filehandle.FsyncFileWriteHandle.flush(FsyncFileWriteHandle.java:464) ... 17 more Caused by: java.nio.BufferOverflowException at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:363) at java.nio.ByteBuffer.put(ByteBuffer.java:859) at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.writePlainRecord(RecordDataV1Serializer.java:1821) at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.writePlainRecord(RecordDataV2Serializer.java:332) at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.writeRecord(RecordDataV1Serializer.java:238) at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer$2.writeWithHeaders(RecordV2Serializer.java:189) at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.R
[jira] [Created] (IGNITE-13109) Skip metastorage entries that can not be unmarshalled
Amelchev Nikita created IGNITE-13109: Summary: Skip metastorage entries that can not be unmarshalled Key: IGNITE-13109 URL: https://issues.apache.org/jira/browse/IGNITE-13109 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Need to skip metastorage entries that can not be unmarshalled (created by the old cluster). It leads that nodes can't join to the first started node: {noformat} [SEVERE][main][PersistenceBasicCompatibilityTest1] Got exception while starting (will rollback startup routine). class org.apache.ignite.IgniteCheckedException: Failed to start manager: GridManagerAdapter [enabled=true, name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager] at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:2035) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1314) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2063) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1116) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:636) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:562) at org.apache.ignite.Ignition.start(Ignition.java:328) at org.apache.ignite.testframework.junits.multijvm.IgniteNodeRunner.main(IgniteNodeRunner.java:74) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller [clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@77b14724], reconCnt=10, reconDelay=2000, maxAckTimeout=60, soLinger=5, forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null, skipAddrsRandomization=false] at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:302) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:948) at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:2030) ... 8 more Caused by: class org.apache.ignite.spi.IgniteSpiException: Unable to unmarshal key=ignite.testOldClusterTag at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:2009) at org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:1116) at org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:427) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2111) at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:299) ... 10 more {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12959) Add support for GenericWhitespace to checkstyle rules
Amelchev Nikita created IGNITE-12959: Summary: Add support for GenericWhitespace to checkstyle rules Key: IGNITE-12959 URL: https://issues.apache.org/jira/browse/IGNITE-12959 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add a new rule to checkstyle according to Apache Ignite Whitespaces and empty lines conventions. https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12958) Add licenses check to Travis configuration
Amelchev Nikita created IGNITE-12958: Summary: Add licenses check to Travis configuration Key: IGNITE-12958 URL: https://issues.apache.org/jira/browse/IGNITE-12958 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita 1. Add licenses check to Travis configuration 2. Make checks on the compile lifecycle -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12953) Add support for SingleSpaceSeparator to checkstyle rules
Amelchev Nikita created IGNITE-12953: Summary: Add support for SingleSpaceSeparator to checkstyle rules Key: IGNITE-12953 URL: https://issues.apache.org/jira/browse/IGNITE-12953 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add a new rule to checkstyle according to Apache Ignite Whitespaces and empty lines conventions. https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12949) Add support for NoWhitespaceAfter to checkstyle rules
Amelchev Nikita created IGNITE-12949: Summary: Add support for NoWhitespaceAfter to checkstyle rules Key: IGNITE-12949 URL: https://issues.apache.org/jira/browse/IGNITE-12949 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add a new rule to checkstyle according to Apache Ignite Whitespaces and empty lines conventions. https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12948) Add support for NoWhitespaceBefore to checkstyle rules
Amelchev Nikita created IGNITE-12948: Summary: Add support for NoWhitespaceBefore to checkstyle rules Key: IGNITE-12948 URL: https://issues.apache.org/jira/browse/IGNITE-12948 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add a new rule to checkstyle according to Apache Ignite Whitespaces and empty lines conventions. https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12947) Add support for MethodParamPad to checkstyle rules
Amelchev Nikita created IGNITE-12947: Summary: Add support for MethodParamPad to checkstyle rules Key: IGNITE-12947 URL: https://issues.apache.org/jira/browse/IGNITE-12947 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add a new rule to checkstyle according to Apache Ignite Whitespaces and empty lines conventions. [https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines|https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-Whitespacesandemptylines] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
Amelchev Nikita created IGNITE-12927: Summary: The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky Key: IGNITE-12927 URL: https://issues.apache.org/jira/browse/IGNITE-12927 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is flacky. [TC history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-448222889376376497&branch=%3Cdefault%3E&tab=testDetails] {noformat} java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging values 1472820775 and 1472820775) at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133) at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180) at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) at java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180) at java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044) at java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578) at org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315) {noformat} The reason is that random generated keys can be duplicated and cant be collected from stream . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12919) Not all GridUuid renamed to IgniteUuid
Amelchev Nikita created IGNITE-12919: Summary: Not all GridUuid renamed to IgniteUuid Key: IGNITE-12919 URL: https://issues.apache.org/jira/browse/IGNITE-12919 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.9 There are several places in javadocs and serialization mechanisms where GridUuid is not renamed. For example: {noformat} /** * Constructs {@code GridUuid} from a global and local identifiers. ... */ public IgniteUuid(UUID gid, long locId) { ... } /** * Reads {@link org.apache.ignite.lang.IgniteUuid} from input stream. ... */ @Nullable public static IgniteUuid readGridUuid(DataInput in) throws IOException {...} {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12728) The cache#putAllAsync method does not collect statistics
Amelchev Nikita created IGNITE-12728: Summary: The cache#putAllAsync method does not collect statistics Key: IGNITE-12728 URL: https://issues.apache.org/jira/browse/IGNITE-12728 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The cache#putAllAsync method does not collect statistics. The reproducer for {{GridCacheAbstractMetricsSelfTest}}: {noformat} @Test public void testPutAllAsyncAvgTime() throws Exception { IgniteCache cache = grid(0).cache(DEFAULT_CACHE_NAME); assertEquals(0.0, cache.localMetrics().getAveragePutTime(), 0.0); assertEquals(0, cache.localMetrics().getCachePuts()); Map values = new HashMap<>(); values.put(1, 1); values.put(2, 2); values.put(3, 3); IgniteFuture fut = cache.putAllAsync(values); fut.get(); assertTrue(waitForCondition(() -> cache.localMetrics().getAveragePutTime() > 0, 30_000)); assertEquals(values.size(), cache.localMetrics().getCachePuts()); } {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12724) Command parser: do not skip commands with its own specific arguments
Amelchev Nikita created IGNITE-12724: Summary: Command parser: do not skip commands with its own specific arguments Key: IGNITE-12724 URL: https://issues.apache.org/jira/browse/IGNITE-12724 Project: Ignite Issue Type: Test Reporter: Amelchev Nikita {{CommandList.CACHE}}, {{CommandList.WAL}}, {{CommandList.SET_STATE}}, {{CommandList.ENCRYPTION}} commands have their own specific arguments. They are skipped in tests: * testParseAndValidateSSLArguments * testParseAndValidateUserAndPassword * testConnectionSettings Need to refactor tests and avoid skips: {noformat} if (skipCommand(cmd)) continue; {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12666) Provide cluster performance profiling tool
Amelchev Nikita created IGNITE-12666: Summary: Provide cluster performance profiling tool Key: IGNITE-12666 URL: https://issues.apache.org/jira/browse/IGNITE-12666 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita For now, Ignite has not build-in profiling tool for user's operations and internal processes. Such a tool will be able to collect performance statistics and create a human-readable report. It will help to analyze workload and to tune configuration and applications. Example of similar tools in other products: AWR [[1]|https://docs.oracle.com/cd/E11882_01/server.112/e41573/autostat.htm#PFGRF94176] [[2]|http://www.dba-oracle.com/t_sample_awr_report.htm] [[3]|http://expertoracle.com/2018/02/06/performance-tuning-basics-15-awr-report-analysis/] (Oracle) ; pgbadger [[4]|https://github.com/darold/pgbadger], pgmetrics [[5]|https://pgmetrics.io/docs/index.html#example], powa [[6]|https://powa.readthedocs.io/en/latest/] (PostgresSQL). Example of html report: [powa|https://powa.readthedocs.io/en/latest/]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12501) The AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky.
Amelchev Nikita created IGNITE-12501: Summary: The AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize test is flacky. Key: IGNITE-12501 URL: https://issues.apache.org/jira/browse/IGNITE-12501 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.9 The test is flacky. [TC history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7463074180495175640&tab=testDetails]. (Success rate 76%) The reason is that there is not enough check for a message about the node exit: Now: {noformat} private boolean serverDownMessage(String text) { return text.contains("Failed to send message (node may have left the grid or " + "TCP connection cannot be established due to firewall issues)") || text.contains("Failed to send message, node left"); } {noformat} But message send can be failed by follow message introduced in IGNITE-7648: {noformat} java.lang.AssertionError: Unexpected exception: Failed to send message (node left topology): {noformat} It seems we should to add this message to the check. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12492) TDE - Phase-2. Documentation.
Amelchev Nikita created IGNITE-12492: Summary: TDE - Phase-2. Documentation. Key: IGNITE-12492 URL: https://issues.apache.org/jira/browse/IGNITE-12492 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12475) TDE - Phase-2. CLI process management
Amelchev Nikita created IGNITE-12475: Summary: TDE - Phase-2. CLI process management Key: IGNITE-12475 URL: https://issues.apache.org/jira/browse/IGNITE-12475 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Provide the ability to manage the process from CLI: {noformat} # Starts master key rotation. control.sh --encryption change_master_key newMasterKeyName # Displays cluster's current master key name. control.sh --encryption get_master_key {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12453) Transaction operations metrics on affinity nodes
Amelchev Nikita created IGNITE-12453: Summary: Transaction operations metrics on affinity nodes Key: IGNITE-12453 URL: https://issues.apache.org/jira/browse/IGNITE-12453 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita We should add histogram metrics that measure cache operations times on affinity nodes: - get - put - remove - commit - rollback -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12423) PME duration histogram updates only if log info enabled
Amelchev Nikita created IGNITE-12423: Summary: PME duration histogram updates only if log info enabled Key: IGNITE-12423 URL: https://issues.apache.org/jira/browse/IGNITE-12423 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 The updates histogram method is placed at the log info block: {noformat} if (log.isInfoEnabled()) { ... updateDurationHistogram(System.currentTimeMillis() - initTime); ... } {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12420) Fix broken the Check Code Style suite
Amelchev Nikita created IGNITE-12420: Summary: Fix broken the Check Code Style suite Key: IGNITE-12420 URL: https://issues.apache.org/jira/browse/IGNITE-12420 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita The Check Code Style suite fails with error: {noformat} [ERROR] /opt/buildagent/work/7bc1c54bc719b67c/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/index/AbstractIndexingCommonTest.java:28:8: Unused import - org.apache.ignite.IgniteException. [UnusedImports] {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12416) Avoid use deprecated the Ignite.active(boolean) methods in project
Amelchev Nikita created IGNITE-12416: Summary: Avoid use deprecated the Ignite.active(boolean) methods in project Key: IGNITE-12416 URL: https://issues.apache.org/jira/browse/IGNITE-12416 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita IgniteCluster#active(boolean) should be used instead of Ignite#active(boolean) IgniteCluster#active() should be used instead of Ignite#active() Since IEP-4 was merged and deprecates cluster activation methods Deprecated methods usages provide many warnings on the build project stage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12410) Too long muted tests should be ignored with annotation
Amelchev Nikita created IGNITE-12410: Summary: Too long muted tests should be ignored with annotation Key: IGNITE-12410 URL: https://issues.apache.org/jira/browse/IGNITE-12410 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita There are some tests that muted and having long execution time: Test: CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime Duration: 2m:37s,377ms (x2, 2 suite) Muted by: https://issues.apache.org/jira/browse/IGNITE-9391 Fail rate: 97% Test: IgniteOsgiServiceTest.testServiceExposedAndCallbacksInvoked Duration: 3m:04s,307ms Muted by: https://issues.apache.org/jira/browse/IGNITE-8300 Fail rate: 93% Test: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled Duration: 3m:01s,369ms Muted by: https://issues.apache.org/jira/browse/IGNITE-8254 Fail rate: 100% Test: JoinInActiveNodeToActiveClusterWithPersistence.testJoinClientStaticCacheConfigurationInCluster Duration: 9s,194ms Muted by: https://issues.apache.org/jira/browse/IGNITE-5518 Fail rate: 100% Total time: 11+ minutes They should be ignored with the ignored annotation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12400) Remove the stopProcess method from the DiscoveryCustomMessage interface
Amelchev Nikita created IGNITE-12400: Summary: Remove the stopProcess method from the DiscoveryCustomMessage interface Key: IGNITE-12400 URL: https://issues.apache.org/jira/browse/IGNITE-12400 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Currently, the {{stopProcess}} method works only if the {{zookeeper discovery}} configured. It doesn't work in {{TcpDiscoverySpi}}. There are no any usages of this method except tests. I suggest to remove it from the discovery custom message interface. [Dev-list discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/Unclear-to-use-methods-in-the-DiscoverySpiCustomMessage-interface-td44144.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12388) The testReconnectServersRestart_3 test is flacky
Amelchev Nikita created IGNITE-12388: Summary: The testReconnectServersRestart_3 test is flacky Key: IGNITE-12388 URL: https://issues.apache.org/jira/browse/IGNITE-12388 Project: Ignite Issue Type: Test Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 The testReconnectServersRestart_3 test is flacky. [TC history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=534893108987486091&tab=testDetails] Sometimes it fails by timeout. The reason is the incorrect client mode condition during nodes starts: {noformat} helper.clientModeThreadLocal(threadIdx == srvIdx || ThreadLocalRandom.current().nextBoolean()) {noformat} There is no server node to connect when all started nodes are clients: {noformat} [2019-11-22 15:42:24,998][WARN ][start-node-5][ZookeeperDiscoveryImpl] Waiting for local join event [nodeId=74a33ea3-6d7c-4ab4-b86c-3d9305c4, name=internal.ZookeeperDiscoveryClientReconnectTest4] [2019-11-22 15:42:25,010][WARN ][start-node-1][ZookeeperDiscoveryImpl] Waiting for local join event [nodeId=b113bb09-5d6a-48b8-a656-d22cb920, name=internal.ZookeeperDiscoveryClientReconnectTest0] [2019-11-22 15:42:25,015][WARN ][start-node-4][ZookeeperDiscoveryImpl] Waiting for local join event [nodeId=121ca03d-31de-4de4-a81c-20bd1373, name=internal.ZookeeperDiscoveryClientReconnectTest3] [2019-11-22 15:42:25,017][WARN ][start-node-2][ZookeeperDiscoveryImpl] Waiting for local join event [nodeId=4a6b5c7f-fc06-4251-b78f-c49277f1, name=internal.ZookeeperDiscoveryClientReconnectTest1] [2019-11-22 15:42:25,020][WARN ][start-node-3][ZookeeperDiscoveryImpl] Waiting for local join event [nodeId=b0468b08-7d57-4b29-b2fb-6d142592, name=internal.ZookeeperDiscoveryClientReconnectTest2] {noformat} Then the test fails by timeout (5min). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12386) The InvalidServerTest.testInvalidServer test is flacky
Amelchev Nikita created IGNITE-12386: Summary: The InvalidServerTest.testInvalidServer test is flacky Key: IGNITE-12386 URL: https://issues.apache.org/jira/browse/IGNITE-12386 Project: Ignite Issue Type: Test Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 The InvalidServerTest.testInvalidServer test is flacky. The reason is that in the test two clusters are started, instead of one. Because TcpDiscoveryMulticastIpFinder is used by default. {noformat} 03:41:32] Topology snapshot [ver=1, locNode=10ecdb9c, servers=1, clients=0, state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB] [03:41:36] Topology snapshot [ver=1, locNode=20f59b4f, servers=1, clients=0, state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB] [03:41:40] Topology snapshot [ver=2, locNode=cecf2df6, servers=2, clients=0, state=INACTIVE, CPUs=5, offheap=19.0GB, heap=2.0GB] {noformat} [Fail example.|https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=4771562&_focus=233870] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12323) Test GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode is flaky
Amelchev Nikita created IGNITE-12323: Summary: Test GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode is flaky Key: IGNITE-12323 URL: https://issues.apache.org/jira/browse/IGNITE-12323 Project: Ignite Issue Type: Test Reporter: Amelchev Nikita Assignee: Amelchev Nikita Test {{GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode}} is flaky. The reason is that node stopping may be more than the auto adjust timeout. This cause assertion error on topology size check: {code:java} assertEquals(EXIT_CODE_OK, execute("--baseline", "auto_adjust", "enable", "timeout", "2000")); assertEquals(3, ignite.cluster().currentBaselineTopology().size()); stopGrid(2); // May be more than 2 seconds assertEquals(3, ignite.cluster().currentBaselineTopology().size()); // Fails. {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12302) Test ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId is broken.
Amelchev Nikita created IGNITE-12302: Summary: Test ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId is broken. Key: IGNITE-12302 URL: https://issues.apache.org/jira/browse/IGNITE-12302 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 Test checks that a new node will not be started with the same node id. Newly added SystemView creates table on node startup and fails with error: {noformat} java.lang.AssertionError: Unexpected exception at org.apache.ignite.testframework.GridTestUtils.fail(GridTestUtils.java:622) at org.apache.ignite.testframework.GridTestUtils.assertThrowsAnyCause(GridTestUtils.java:465) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryTopologyChangeAndReconnectTest.testDuplicatedNodeId(ZookeeperDiscoveryTopologyChangeAndReconnectTest.java:582) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2090) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to register system view. at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1401) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1703) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1117) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:615) at org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:983) at org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:924) at org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:912) at org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:878) at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryTopologyChangeAndReconnectTest.lambda$testDuplicatedNodeId$0(ZookeeperDiscoveryTopologyChangeAndReconnectTest.java:583) at org.apache.ignite.testframework.GridTestUtils.assertThrowsAnyCause(GridTestUtils.java:449) ... 11 more Caused by: class org.apache.ignite.IgniteException: Failed to register system view. at org.apache.ignite.internal.processors.query.h2.SchemaManager.createSystemView(SchemaManager.java:238) at org.apache.ignite.internal.processors.query.h2.SchemaManager.createSystemViews(SchemaManager.java:247) at org.apache.ignite.internal.processors.query.h2.SchemaManager.start(SchemaManager.java:195) at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.start(IgniteH2Indexing.java:2083) [2019-10-17 21:50:42,017][INFO ][main][root] >>> Stopping test: ZookeeperDiscoveryTopologyChangeAndReconnectTest#testDuplicatedNodeId in 261 ms <<< at org.apache.ignite.internal.processors.query.GridQueryProcessor.start(GridQueryProcessor.java:250) at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1977) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1213) ... 21 more Caused by: org.h2.jdbc.JdbcSQLException: Таблица "NODE_ATTRIBUTES" уже существует Table "NODE_ATTRIBUTES" already exists; SQL statement: CREATE TABLE NODE_ATTRIBUTES(NODE_ID UUID, NAME VARCHAR, VALUE VARCHAR) ENGINE "org.apache.ignite.internal.processors.query.h2.sys.SqlSystemTableEngine" [42101-197] at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at org.h2.message.DbException.get(DbException.java:179) at org.h2.message.DbException.get(DbException.java:155) at org.h2.command.ddl.CreateTable.update(CreateTable.java:86) at org.h2.command.CommandContainer.update(CommandContainer.java:102) at org.h2.command.Command.executeUpdate(Command.java:261) at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement
[jira] [Created] (IGNITE-12186) TDE - Phase-2. Master key rotation.
Amelchev Nikita created IGNITE-12186: Summary: TDE - Phase-2. Master key rotation. Key: IGNITE-12186 URL: https://issues.apache.org/jira/browse/IGNITE-12186 Project: Ignite Issue Type: Sub-task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 Need to implement master key rotation process. Master key(MK) rotation required in case of it compromising or at the end of crypto period(key validity period). [Design (cwiki).|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12171) Remove the MetricRegistry.remove(String name) method.
Amelchev Nikita created IGNITE-12171: Summary: Remove the MetricRegistry.remove(String name) method. Key: IGNITE-12171 URL: https://issues.apache.org/jira/browse/IGNITE-12171 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 I suggest removing the unused {{MetricRegistry.remove(String name)}} method due to we can remove a subset of metrics using the {{GridMetricManager.remove(String regName)}} method with notifying mechanism. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12027) NPE on try to read the MinimumNumberOfPartitionCopies metric.
Amelchev Nikita created IGNITE-12027: Summary: NPE on try to read the MinimumNumberOfPartitionCopies metric. Key: IGNITE-12027 URL: https://issues.apache.org/jira/browse/IGNITE-12027 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita NPE on try to read the MinimumNumberOfPartitionCopies metric before node starts. Details: {noformat} java.lang.NullPointerException at org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.numberOfPartitionCopies(CacheGroupMetricsImpl.java:218) at org.apache.ignite.internal.processors.cache.CacheGroupMetricsImpl.getMinimumNumberOfPartitionCopies(CacheGroupMetricsImpl.java:232) at org.apache.ignite.internal.util.lang.GridFunc.lambda$nonThrowableSupplier$2(GridFunc.java:3302) at org.apache.ignite.internal.processors.metric.impl.IntGauge.value(IntGauge.java:45) at org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$null$5(OpenCensusMetricExporterSpi.java:152) at java.lang.Iterable.forEach(Iterable.java:75) at org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.lambda$export$6(OpenCensusMetricExporterSpi.java:141) at java.lang.Iterable.forEach(Iterable.java:75) at org.apache.ignite.spi.metric.opencensus.OpenCensusMetricExporterSpi.export(OpenCensusMetricExporterSpi.java:137) at org.apache.ignite.internal.processors.metric.PushMetricsExporterAdapter.lambda$spiStart$0(PushMetricsExporterAdapter.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} Reason: {{GridDhtPartitionFullMap partFullMap = ctx.topology().partitionMap(false);}} is null. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12017) Avoid calling GridDhtPartitionsExchangeFuture#onEvent more than once.
Amelchev Nikita created IGNITE-12017: Summary: Avoid calling GridDhtPartitionsExchangeFuture#onEvent more than once. Key: IGNITE-12017 URL: https://issues.apache.org/jira/browse/IGNITE-12017 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita When the GridDhtPartitionsExchangeFuture#onEvent method called it releases init latch. It means that we can't change the initial event (firstDiscoEvt). Otherwise, it breaks the exchange logic. I have checked on TC and this method may be called twice with one event (identical references). The following assert is correct: {noformat} assert exchId.equals(this.exchId) && (firstDiscoEvt == null || firstDiscoEvt == discoEvt); {noformat} Need to refactor the method usages and avoid confusing developers that the first event may be changed. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11961) Provide JMX metrics for PME timings
Amelchev Nikita created IGNITE-11961: Summary: Provide JMX metrics for PME timings Key: IGNITE-11961 URL: https://issues.apache.org/jira/browse/IGNITE-11961 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Currently, partition map exchange timings printed to log(IGNITE-10493). It will be useful if we allow external tools to collect and aggregate partition map exchange metrics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11936) Avoid changing AffinityTopologyVersion on a server node join/left event from not baseline topology.
Amelchev Nikita created IGNITE-11936: Summary: Avoid changing AffinityTopologyVersion on a server node join/left event from not baseline topology. Key: IGNITE-11936 URL: https://issues.apache.org/jira/browse/IGNITE-11936 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Assignee: Amelchev Nikita Currently, a client join/left event does not change AffinityTopologyVersion (see IGNITE-9558). It shouldn't be changed on a server node join/left event from not baseline topology too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11624) Discovery SPI: The client can handle events from the previous cluster after reconnect.
Amelchev Nikita created IGNITE-11624: Summary: 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 Fix For: 2.8 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] [Created] (IGNITE-11623) MVCC: testRebalancingDuringLoad_N tests is flacky in master
Amelchev Nikita created IGNITE-11623: Summary: MVCC: testRebalancingDuringLoad_N tests is flacky in master Key: IGNITE-11623 URL: https://issues.apache.org/jira/browse/IGNITE-11623 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita The following tests are flacky in master: IgnitePdsMvccTestSuite3: IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_10_1_1 ( [Test history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5373044394008664141&branch=%3Cdefault%3E&tab=testDetails] ) testRebalancingDuringLoad_1000_2_8_16 ( [Test history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=8776582252343254845&order=TEST_STATUS_DESC&branch_IgniteTests24Java8=%3Cdefault%3E&itemsCount=50]) testRebalancingDuringLoad_1000_500_8_1 ([Test history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4172157337542230771&branch=%3Cdefault%3E&tab=testDetails]) IgniteClusterActivateDeactivateTestWithPersistence.testDeactivateDuringEvictionAndRebalance ([Test history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=4619901385813836807&branch=%3Cdefault%3E&tab=testDetails]) According to the logs, the cause of the fall: *IgniteTxUnexpectedStateCheckedException: Unexpected state* {noformat} java.lang.AssertionError: Unexpected exception: javax.cache.CacheException: class org.apache.ignite.transactions.TransactionRollbackException: Transaction has been rolled back: be9b08fa961--09d4-4a7d--0001 at org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1318) at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:2064) at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1371) at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:866) at org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest$1.call(IgnitePdsContinuousRestartTest.java:280) at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84) Caused by: class org.apache.ignite.transactions.TransactionRollbackException: Transaction has been rolled back: be9b08fa961--09d4-4a7d--0001 at org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:935) at org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:933) ... 6 more Caused by: class org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException: Transaction has been rolled back: be9b08fa961--09d4-4a7d--0001 at org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4297) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll0(GridCacheAdapter.java:3000) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll(GridCacheAdapter.java:2989) at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1368) ... 3 more Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update backup node: [localNodeId=44bb5db4-5317-4ab1-8379-16f3b923, remoteNodeId=08a44c02-ebe8-46e8-a7ca-890c6251] at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:999) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2350) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257) at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1126) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318) at org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109) at org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308) at org.apache.ignite.internal.man
[jira] [Created] (IGNITE-11460) MVCC: Possible race on coordinator changing on client reconnection.
Amelchev Nikita created IGNITE-11460: Summary: MVCC: Possible race on coordinator changing on client reconnection. Key: IGNITE-11460 URL: https://issues.apache.org/jira/browse/IGNITE-11460 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 I found that the wrong coordinator can be set in case of client reconnect: {noformat} assert newCrd.topologyVersion().compareTo(curCrd.topologyVersion()) > 0; java.lang.AssertionError at org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onCoordinatorChanged(MvccProcessorImpl.java:541) at org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onLocalJoin(MvccProcessorImpl.java:416) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:851) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:601) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2681) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2719) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748) {noformat} I have attached reproducer in PR. The main reason is that coordinator can be changed from discovery event thread when the client already disconnect (disconnection processed in notifier thread and change coordinator on onDisconnected method). Coordinator can be changed in cases: 1. notifier disco thread: onDisconnected method 2. event disco thread: onDiscovery listener. and events can be processed with some delay and override coordinator that set in notifier thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts
Amelchev Nikita created IGNITE-10926: Summary: ZookeeperDiscoverySpi: client does not survive after several cluster restarts Key: IGNITE-10926 URL: https://issues.apache.org/jira/browse/IGNITE-10926 Project: Ignite Issue Type: Bug Components: zookeeper Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 {{ZookeeperDiscoveryImpl#cleanupPreviousClusterData}} can delete alive node of a client in case of low internal order. Steps to reproduce: 1. Start server and client. 2. Stop the server and wait for the client disconnected. 3. Start and stop the server. The server hasn't time to process client join request. 4. Start server. It will delete alive client node because the client has low internal order. The client will never connect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10579) IgniteCacheContinuousQueryReconnectTest.testReconnectServer is flaky in master.
Amelchev Nikita created IGNITE-10579: Summary: IgniteCacheContinuousQueryReconnectTest.testReconnectServer is flaky in master. Key: IGNITE-10579 URL: https://issues.apache.org/jira/browse/IGNITE-10579 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Next tests are flaky in master: IgniteCacheContinuousQueryReconnectTest.testReconnectServer IgniteCacheContinuousQueryReconnectTest.testReconnectClient Test exception: {noformat} junit.framework.AssertionFailedError: expected:<2> but was:<1> at org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.putAndCheck(IgniteCacheContinuousQueryReconnectTest.java:111) at org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnect(IgniteCacheContinuousQueryReconnectTest.java:179) at org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnectServer(IgniteCacheContinuousQueryReconnectTest.java:93) {noformat} [Test history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-4837559557126450615&branch=%3Cdefault%3E&tab=testDetails] By logs I found that possible reason is that started node doesn't see cluster: {noformat} startGrid(0); Topology snapshot [ver=1, locNode=0b292f90, servers=1, clients=0 startGrid(1); //client Topology snapshot [ver=2, locNode=0b292f90, servers=1, clients=1 Topology snapshot [ver=2, locNode=693848f6, servers=1, clients=1 startGrid(2); Topology snapshot [ver=3, locNode=0b292f90, servers=2, clients=1 Topology snapshot [ver=3, locNode=693848f6, servers=2, clients=1 Topology snapshot [ver=3, locNode=99a406a5, servers=2, clients=1 stopGrid(0); Topology snapshot [ver=4, locNode=99a406a5, servers=1, clients=1 Topology snapshot [ver=4, locNode=693848f6, servers=1, clients=1 startGrid(3); Topology snapshot [ver=1, locNode=8d9ef192, servers=1, clients=0 {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10087) IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master
Amelchev Nikita created IGNITE-10087: Summary: IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master Key: IGNITE-10087 URL: https://issues.apache.org/jira/browse/IGNITE-10087 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 The IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 test is flaky in master. Sometimes the test fails on test timeout (5 min). [Test history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-6728945354254258306&branch=&tab=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10023) Improve ListeningTestLogger for wait conditions.
Amelchev Nikita created IGNITE-10023: Summary: Improve ListeningTestLogger for wait conditions. Key: IGNITE-10023 URL: https://issues.apache.org/jira/browse/IGNITE-10023 Project: Ignite Issue Type: Improvement Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 [Dev-list discussion.|http://apache-ignite-developers.2346864.n4.nabble.com/Unreliable-checks-in-tests-for-string-presence-in-GridStringLogger-contents-td30802.html] Method LogListener.check() should be boolean type. It'll be useful for wait for conditions and code readability: For now: {code:java} waitForCondition(() -> { try { lsnr.check(); return true; } catch (AssertionError ignored) { return false; } }, timeout); {code} After improvement: {code:java} waitForCondition(lsnr::check, timeout); {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9997) IgniteDiagnosticMessagesTest.testLongRunningTx fails on TC
Amelchev Nikita created IGNITE-9997: --- Summary: IgniteDiagnosticMessagesTest.testLongRunningTx fails on TC Key: IGNITE-9997 URL: https://issues.apache.org/jira/browse/IGNITE-9997 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 It fails with the assertion error. [Example of fail.|https://ci.ignite.apache.org/viewLog.html?buildId=2157923&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_BinaryObjectsSimpleMapperBasic#testNameId808105671819833392] Log: {noformat} junit.framework.AssertionFailedError at org.apache.ignite.internal.managers.IgniteDiagnosticMessagesTest.testLongRunningTx(IgniteDiagnosticMessagesTest.java:378){noformat} {code:java} assertTrue(log.contains("Cache entries [cacheId=" + CU.cacheId(DEFAULT_CACHE_NAME) + ", cacheName=" + DEFAULT_CACHE_NAME + "]:")); {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9948) JettyRestProcessorAuthenticationWithTokenSelfTest.testGetOrCreateCache fails on TC
Amelchev Nikita created IGNITE-9948: --- Summary: JettyRestProcessorAuthenticationWithTokenSelfTest.testGetOrCreateCache fails on TC Key: IGNITE-9948 URL: https://issues.apache.org/jira/browse/IGNITE-9948 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 [Example of fail.|https://ci.ignite.apache.org/viewLog.html?buildId=2118632&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient#testNameId-4416495803371140089] Log details: {noformat} [2018-10-19 06:59:53,063][ERROR][main][root] Test failed. java.lang.NullPointerException at org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.checkGetOrCreateAndDestroy(JettyRestProcessorAbstractSelfTest.java:593) at org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testGetOrCreateCache(JettyRestProcessorAbstractSelfTest.java:619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at junit.framework.TestCase.runTest(TestCase.java:176) at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176) at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:142) at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2091) at java.lang.Thread.run(Thread.java:748){noformat} The possible reason is the race between getting cache instance on different nodes: # Jetty query create cache successfully on one node. # PME doesn't have completed. # The test fails with NPE while getting the instance of cache on another node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9837) Test BinaryMetadataUpdatesFlowTest.testConcurrentMetadataUpdates is flaky in master.
Amelchev Nikita created IGNITE-9837: --- Summary: Test BinaryMetadataUpdatesFlowTest.testConcurrentMetadataUpdates is flaky in master. Key: IGNITE-9837 URL: https://issues.apache.org/jira/browse/IGNITE-9837 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test _BinaryMetadataUpdatesFlowTest.testConcurrentMetadataUpdates_ is flaky in master. Sometimes it fails by timeout (5min). [Example of fail.|https://ci.ignite.apache.org/viewLog.html?buildId=2042133&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_BinaryObjects#testNameId4314129944736732856] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9802) Test TcpCommunicationSpiFaultyClientTest.testNotAcceptedConnection is flaky in master
Amelchev Nikita created IGNITE-9802: --- Summary: Test TcpCommunicationSpiFaultyClientTest.testNotAcceptedConnection is flaky in master Key: IGNITE-9802 URL: https://issues.apache.org/jira/browse/IGNITE-9802 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test is flaky in master. Example of fail: [TC build. |https://ci.ignite.apache.org/viewLog.html?buildTypeId=IgniteTests24Java8_Spi&buildId=1976776] Log details: {noformat} junit.framework.AssertionFailedError at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiFaultyClientTest.testFailClient(TcpCommunicationSpiFaultyClientTest.java:178) at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiFaultyClientTest.testNotAcceptedConnection(TcpCommunicationSpiFaultyClientTest.java:130){noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9673) Timeout in Java Client suite.
Amelchev Nikita created IGNITE-9673: --- Summary: Timeout in Java Client suite. Key: IGNITE-9673 URL: https://issues.apache.org/jira/browse/IGNITE-9673 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Example of timeout: [TC build|[https://ci.ignite.apache.org/viewLog.html?buildId=1919405&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient].] The possible reason is non-interruptable future: {noformat} "test-runner-#2440%redis.RedisProtocolStringSelfTest%" #3843 prio=5 os_prio=0 tid=0x7f8f053fb000 nid=0x7b19 waiting on condition [0x7f8d74f8f000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304) at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177) at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140) at org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2465) at org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2463) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4228) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2463) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2444) at org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2421) at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1089) at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820) at org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testStrlen(RedisProtocolStringSelfTest.java:310) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at junit.framework.TestCase.runTest(TestCase.java:176) at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2177) at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143) at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2092) at java.lang.Thread.run(Thread.java:748) {noformat} The main thread is waiting for runner thread interrupt: {noformat} "main" #1 prio=5 os_prio=0 tid=0x7f8f0400e000 nid=0x6c18 in Object.wait() [0x7f8f0db58000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Thread.join(Thread.java:1252) - locked <0x00078bfaf668> (a org.apache.ignite.thread.IgniteThread) at org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4662) at org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4647) at org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:2124) at junit.framework.TestCase.runBare(TestCase.java:141) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.framework.TestSuite.run(TestSuite.java:250) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.maven.surefire.util.Reflec
[jira] [Created] (IGNITE-9654) Test testJoinQueryUnstableTopology is flaky in master
Amelchev Nikita created IGNITE-9654: --- Summary: Test testJoinQueryUnstableTopology is flaky in master Key: IGNITE-9654 URL: https://issues.apache.org/jira/browse/IGNITE-9654 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test IgniteCacheDistributedPartitionQueryNodeRestartsSelfTest.testJoinQueryUnstableTopology is flaky in master. [Example of fail|https://ci.ignite.apache.org/viewLog.html?buildId=1910548&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Queries1#testNameId-9054712716754027821]. Log: {noformat} java.lang.RuntimeException: Not all Ignite instances has been stopped. Please, see log for details. {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9627) TcpCommunicationSpiSkipMessageSendTest.testClientSegmented is flaky in master
Amelchev Nikita created IGNITE-9627: --- Summary: TcpCommunicationSpiSkipMessageSendTest.testClientSegmented is flaky in master Key: IGNITE-9627 URL: https://issues.apache.org/jira/browse/IGNITE-9627 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test is flaky in master. Also, it uses the default failure handler and can halt JVM. Example of fail: [TC build|https://ci.ignite.apache.org/viewLog.html?buildId=1895268&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Spi#testNameId-3225493048753223945]. Log: {noformat} [2018-09-18 06:12:42,466][ERROR][main][root] Test failed. junit.framework.AssertionFailedError: Client wasn't segmented. at junit.framework.Assert.fail(Assert.java:57) at junit.framework.TestCase.fail(TestCase.java:227) at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiSkipMessageSendTest.testClientSegmented(TcpCommunicationSpiSkipMessageSendTest.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at junit.framework.TestCase.runTest(TestCase.java:176) at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2177) at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143) at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2092) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9589) GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange is flaky in master
Amelchev Nikita created IGNITE-9589: --- Summary: GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange is flaky in master Key: IGNITE-9589 URL: https://issues.apache.org/jira/browse/IGNITE-9589 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita The test GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange fails periodicaly. >From the logs, I see that the failure is caused by BindException. It causes >node start fails because the test port range is 0. {noformat} [2018-09-13 04:06:20,060][ERROR][test-runner-#225862%tcp.GridTcpCommunicationSpiConfigSelfTest%][GridTcpCommunicationSpiConfigSelfTest] Failed to start manager: GridManagerAdapter [enabled=true, name=o.a.i.i.managers.communication.GridIoManager] class org.apache.ignite.IgniteCheckedException: Failed to get SPI attributes. at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278) at org.apache.ignite.internal.managers.communication.GridIoManager.start(GridIoManager.java:262) at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1755) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:975) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2020) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1725) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1153) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:673) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:598) at org.apache.ignite.Ignition.start(Ignition.java:323) at org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:1370) at org.apache.ignite.spi.communication.tcp.GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange(GridTcpCommunicationSpiConfigSelfTest.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at junit.framework.TestCase.runTest(TestCase.java:176) at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2177) at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143) at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2092) at java.lang.Thread.run(Thread.java:748) Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to initialize TCP server: 0.0.0.0/0.0.0.0 at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.getNodeAttributes(TcpCommunicationSpi.java:2137) at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:261) ... 20 more Caused by: class org.apache.ignite.IgniteCheckedException: Failed to bind to any port within range [startPort=47100, portRange=0, locHost=0.0.0.0/0.0.0.0] at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.resetNioServer(TcpCommunicationSpi.java:2450) at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.getNodeAttributes(TcpCommunicationSpi.java:2134) ... 21 more Caused by: class org.apache.ignite.IgniteCheckedException: Failed to initialize NIO selector. at org.apache.ignite.internal.util.nio.GridNioServer.createSelector(GridNioServer.java:988) at org.apache.ignite.internal.util.nio.GridNioServer.(GridNioServer.java:342) at org.apache.ignite.internal.util.nio.GridNioServer.(GridNioServer.java:97) at org.apache.ignite.internal.util.nio.GridNioServer$Builder.build(GridNioServer.java:3669) at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.resetNioServer(TcpCommunicationSpi.java:2415) ... 22 more Caused by: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:433) at sun.nio.ch.Net.bind(Net.java:425) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) at org.apache.ignite.internal.util.nio.GridNioServer.createSelector(GridNioServer.java:972) ... 26 more {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9020) .NET: Creating CacheEntry events regardless of values.
Amelchev Nikita created IGNITE-9020: --- Summary: .NET: Creating CacheEntry events regardless of values. Key: IGNITE-9020 URL: https://issues.apache.org/jira/browse/IGNITE-9020 Project: Ignite Issue Type: Task Components: platforms Reporter: Amelchev Nikita At Java, cache entry events serialize in _PlatformUtils.writeCacheEntryEvent()_ method. It writes only _key_, _val_, and _oldVal_. *EventType doesn't write*. At .Net _ContinuousQueryUtils.ReadEvent0()_ method create events after check on exist _val_ and _oldVal_ fields. TCK 1.1 says that _getValue()_ not _null_ for REMOVE/EXPIRED events if old value required and it breaks logic. The possible solution is to check event type in this methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7024) Introduce some kind of network compression
Amelchev Nikita created IGNITE-7024: --- Summary: Introduce some kind of network compression Key: IGNITE-7024 URL: https://issues.apache.org/jira/browse/IGNITE-7024 Project: Ignite Issue Type: New Feature Reporter: Amelchev Nikita Assignee: Amelchev Nikita Introduce some kind of pluggable compression at network level The main idea is using in-line compression and writes encoded bytes in network channel by bytes array buffer. It allows us avoiding expensive memory allocation. A solution may be implemented at TcpCommunicationSpi level. For example, introduce Compressor interface which will allow us to describe our compression strategy, for example, exclude some small messages, choose compression algorithm and other… -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6692) Select query on a client with unused field throws an exception.
Amelchev Nikita created IGNITE-6692: --- Summary: Select query on a client with unused field throws an exception. Key: IGNITE-6692 URL: https://issues.apache.org/jira/browse/IGNITE-6692 Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Reporter: Amelchev Nikita Steps to reproduce: 1. Run one server, one client. 2. Execute next queries on a client: 3. Run select that throws an exception: Test is in attachment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6666) BinaryObjectImpl.writeFieldByOrder method does not support TIME
Amelchev Nikita created IGNITE-: --- Summary: BinaryObjectImpl.writeFieldByOrder method does not support TIME Key: IGNITE- URL: https://issues.apache.org/jira/browse/IGNITE- Project: Ignite Issue Type: Bug Security Level: Public (Viewable by anyone) Components: binary Reporter: Amelchev Nikita Assignee: Amelchev Nikita The variable totalLen is not define for TIME in method BinaryObjectImpl.writeFieldByOrder. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6172) Binary marshaller should support Serializable
Amelchev Nikita created IGNITE-6172: --- Summary: Binary marshaller should support Serializable Key: IGNITE-6172 URL: https://issues.apache.org/jira/browse/IGNITE-6172 Project: Ignite Issue Type: Task Components: general Reporter: Amelchev Nikita When binary marshaller meets a Serializable object, it switches to optimized marshaller. Ignite should just have a single marshaller, which drives the whole serialization process. It doesn't delegate to OptimizedMarshaller as it does today. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5104) Refactor javadocs and annotations to single style
Amelchev Nikita created IGNITE-5104: --- Summary: Refactor javadocs and annotations to single style Key: IGNITE-5104 URL: https://issues.apache.org/jira/browse/IGNITE-5104 Project: Ignite Issue Type: Task Reporter: Amelchev Nikita Assignee: Amelchev Nikita Priority: Trivial According to Ignite codestyle: We should use a shorter version of {@inheritDoc} when it possible. Annotations @Nullable and @Override should be placed on one line with declare of method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)