[jira] [Commented] (IGNITE-18434) Сustom histogram buckets not applied after restart
[ https://issues.apache.org/jira/browse/IGNITE-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680333#comment-17680333 ] Stepanov Ilya commented on IGNITE-18434: Checked in persistent mode. Problem still reproducible. My config: {code:java} {code} Steps: 1) Start node with persistent=true 2) Activate cluster 3) change buckets for TaskExecutionTime in StripedExecutor (register name threadPools.StripedExecutor.TaskExecutionTime) 4) deactivate and stop cluster 5) Start node with persistent=true 6) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" After restart, custom histogram buckets are not aplied. Additionally: Bucket settings are displayed in metastorge (in system views) > Сustom histogram buckets not applied after restart > -- > > Key: IGNITE-18434 > URL: https://issues.apache.org/jira/browse/IGNITE-18434 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.14 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > Setting custom buckets for "TaskExecutionTime" metric in > "threadPools.\{thread_pool_name}" register is not applied after node restart. > > Steps to reproduce: > 1) Start node > 2) change buckets for TaskExecutionTime in StripedExecutor (via > configureHistogramMetric > [https://javadoc.io/static/org.apache.ignite/ignite-core/2.14.0/org/apache/ignite/mxbean/MetricsMxBean.html#configureHistogramMetric-java.lang.String-long:A-]) > 3) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" > 4) Restart node > 5) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IGNITE-18434) Сustom histogram buckets not applied after restart
[ https://issues.apache.org/jira/browse/IGNITE-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya reopened IGNITE-18434: Ignite Flags: (was: Docs Required,Release Notes Required) > Сustom histogram buckets not applied after restart > -- > > Key: IGNITE-18434 > URL: https://issues.apache.org/jira/browse/IGNITE-18434 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.14 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > Setting custom buckets for "TaskExecutionTime" metric in > "threadPools.\{thread_pool_name}" register is not applied after node restart. > > Steps to reproduce: > 1) Start node > 2) change buckets for TaskExecutionTime in StripedExecutor (via > configureHistogramMetric > [https://javadoc.io/static/org.apache.ignite/ignite-core/2.14.0/org/apache/ignite/mxbean/MetricsMxBean.html#configureHistogramMetric-java.lang.String-long:A-]) > 3) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" > 4) Restart node > 5) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18434) Сustom histogram buckets not applied after restart
Stepanov Ilya created IGNITE-18434: -- Summary: Сustom histogram buckets not applied after restart Key: IGNITE-18434 URL: https://issues.apache.org/jira/browse/IGNITE-18434 Project: Ignite Issue Type: Bug Affects Versions: 2.14 Reporter: Stepanov Ilya Setting custom buckets for "TaskExecutionTime" metric in "threadPools.\{thread_pool_name}" register is not applied after node restart. Steps to reproduce: 1) Start node 2) change buckets for TaskExecutionTime in StripedExecutor (via configureHistogramMetric [https://javadoc.io/static/org.apache.ignite/ignite-core/2.14.0/org/apache/ignite/mxbean/MetricsMxBean.html#configureHistogramMetric-java.lang.String-long:A-]) 3) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" 4) Restart node 5) Check metrics in JMX "org.apache:group=threadPools,name=StripedExecutor" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics are no updated in case of connection problems/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: Metrics "\{clientType}.ActiveSessions" are not updated correctly in case of connection problems. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) Block port 10800 on the server host {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], writeBuf=java.nio.DirectByteBuffer[po s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, outboundMessagesQueueSizeMetric=o.a.i.i. processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, createTime=1661776500783, closeTime=0, bytesSent=28, bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, filterChain=FilterChain[filters=[GridNio AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, directMode=true]], accepted=true, markedForClose=false]]] java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) ~[?:1.8.0_302] at org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with proxy server connection {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: Metrics "\{clientType}.ActiveSessions" are not updated correctly in case of connection problems. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) Block port 10800 on the server host {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354, h
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics are no updated in case of connection problems/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: Metrics "\{clientType}.ActiveSessions" are not updated correctly in case of connection problems. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) Block port 10800 on the server host {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], writeBuf=java.nio.DirectByteBuffer[po s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, outboundMessagesQueueSizeMetric=o.a.i.i. processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, createTime=1661776500783, closeTime=0, bytesSent=28, bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, filterChain=FilterChain[filters=[GridNio AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, directMode=true]], accepted=true, markedForClose=false]]] java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) ~[?:1.8.0_302] at org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: Metrics "\{clientType}.ActiveSessions" are not updated correctly in case of connection problems. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics are no updated in case of connection problems/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: Metrics "\{clientType}.ActiveSessions" are not updated correctly in case of connection problems. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], writeBuf=java.nio.DirectByteBuffer[po s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, outboundMessagesQueueSizeMetric=o.a.i.i. processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, createTime=1661776500783, closeTime=0, bytesSent=28, bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, filterChain=FilterChain[filters=[GridNio AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, directMode=true]], accepted=true, markedForClose=false]]] java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) ~[?:1.8.0_302] at org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: "\{clientType}.ActiveSessions" metrics no correctly updated in case when we have a problems with connection. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics are no updated in case of connection problems/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Summary: {clientType}.ActiveSessions metrics are no updated in case of connection problems/lost (was: {clientType}.ActiveSessions metrics are no updated in case of connection problem/lost) > {clientType}.ActiveSessions metrics are no updated in case of connection > problems/lost > -- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no correctly updated in case when we > have a problems with connection. > > Steps to reproduce: > 1) Start server > 2) Start jdbc or thin client > 3) On the server host block 10800 port > {code:java} > iptables -A INPUT -p tcp --dport 10800 -j DROP {code} > 4) Check "\{clientType}.ActiveSessions". We will see one connection. > 5) Stop jdbc or thin client > 6) Check "\{clientType}.ActiveSessions". We will still see one connection in > "\{clientType}.ActiveSessions". > 7) After about 2 hours, the metric will have a negative value = -1 > Error in log: > {code:java} > [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] > Failed to process selector key [ses=GridSelectorNioSessionImpl > [worker=DirectNioClient > Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, > bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker > [name=grid-nio-worker-client-listener-1, igniteInst > anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, > interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], > writeBuf=java.nio.DirectByteBuffer[po > s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 > cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, > outboundMessagesQueueSizeMetric=o.a.i.i. > processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl > [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, > createTime=1661776500783, closeTime=0, bytesSent=28, > bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, > lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, > filterChain=FilterChain[filters=[GridNio > AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, > directMode=true]], accepted=true, markedForClose=false]]] > java.io.IOException: Connection timed out > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > ~[?:1.8.0_302] > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > ~[?:1.8.0_302] > at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) > ~[?:1.8.0_302] > at > org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) > ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} > > Another case with proxy: > > Steps to reproduce: > 1) Start server > 2) Start Proxy server for remote port 10800 and local port 1024 > 3) Start jdbc or thin client with connecting to proxy server > {code:java} > ClientConfiguration cfg = new > ClientConfiguration().setAddresses("127.0.0.1:1024"); > IgniteClient igniteClient = Ignition.startClient(cfg); > IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics are no updated in case of connection problem/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Summary: {clientType}.ActiveSessions metrics are no updated in case of connection problem/lost (was: {clientType}.ActiveSessions metrics no updated in case of connection problem/lost) > {clientType}.ActiveSessions metrics are no updated in case of connection > problem/lost > - > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no correctly updated in case when we > have a problems with connection. > > Steps to reproduce: > 1) Start server > 2) Start jdbc or thin client > 3) On the server host block 10800 port > {code:java} > iptables -A INPUT -p tcp --dport 10800 -j DROP {code} > 4) Check "\{clientType}.ActiveSessions". We will see one connection. > 5) Stop jdbc or thin client > 6) Check "\{clientType}.ActiveSessions". We will still see one connection in > "\{clientType}.ActiveSessions". > 7) After about 2 hours, the metric will have a negative value = -1 > Error in log: > {code:java} > [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] > Failed to process selector key [ses=GridSelectorNioSessionImpl > [worker=DirectNioClient > Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, > bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker > [name=grid-nio-worker-client-listener-1, igniteInst > anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, > interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], > writeBuf=java.nio.DirectByteBuffer[po > s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 > cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, > outboundMessagesQueueSizeMetric=o.a.i.i. > processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl > [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, > createTime=1661776500783, closeTime=0, bytesSent=28, > bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, > lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, > filterChain=FilterChain[filters=[GridNio > AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, > directMode=true]], accepted=true, markedForClose=false]]] > java.io.IOException: Connection timed out > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > ~[?:1.8.0_302] > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > ~[?:1.8.0_302] > at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) > ~[?:1.8.0_302] > at > org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) > ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) > [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} > > Another case with proxy: > > Steps to reproduce: > 1) Start server > 2) Start Proxy server for remote port 10800 and local port 1024 > 3) Start jdbc or thin client with connecting to proxy server > {code:java} > ClientConfiguration cfg = new > ClientConfiguration().setAddresses("127.0.0.1:1024"); > IgniteClient igniteClient = Ignition.startClient(cfg); > IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no updated in case of connection problem/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: "\{clientType}.ActiveSessions" metrics no correctly updated in case when we have a problems with connection. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Error in log: {code:java} [ERROR][grid-nio-worker-client-listener-1-#55][ClientListenerProcessor] Failed to process selector key [ses=GridSelectorNioSessionImpl [worker=DirectNioClient Worker [super=AbstractNioClientWorker [idx=1, bytesRcvd=19, bytesSent=28, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker [name=grid-nio-worker-client-listener-1, igniteInst anceName=null, finished=false, heartbeatTs=1661784642354, hashCode=624626958, interrupted=false, runner=grid-nio-worker-client-listener-1-#55]]], writeBuf=java.nio.DirectByteBuffer[po s=0 lim=23040 cap=23040], readBuf=java.nio.DirectByteBuffer[pos=0 lim=184640 cap=184640], inRecovery=null, outRecovery=null, closeSocket=true, outboundMessagesQueueSizeMetric=o.a.i.i. processors.metric.impl.LongAdderMetric@63a61cb2, super=GridNioSessionImpl [locAddr=/10.40.6.205:10800, rmtAddr=/10.255.12.2:4708, createTime=1661776500783, closeTime=0, bytesSent=28, bytesRcvd=19, bytesSent0=0, bytesRcvd0=0, sndSchedTime=1661776500844, lastSndTime=1661776500844, lastRcvTime=1661776500833, readsPaused=false, filterChain=FilterChain[filters=[GridNio AsyncNotifyFilter, GridNioCodecFilter [parser=ClientListenerNioMessageParser, directMode=true]], accepted=true, markedForClose=false]]] java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:1.8.0_302] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[?:1.8.0_302] at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[?:1.8.0_302] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) ~[?:1.8.0_302] at org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1351) ~[ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2508) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2273) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1910) [ignite-core-2.13.1-p0.jar:2.13.1-p0] at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) [ignite-core-2.13.1-p0.jar:2.13.1-p0] {code} Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: "\{clientType}.ActiveSessions" metrics no correctly updated in case when we have a problems with connection. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no updated in case of connection problem/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: "\{clientType}.ActiveSessions" metrics no correctly updated in case when we have a problems with connection. Steps to reproduce: 1) Start server 2) Start jdbc or thin client 3) On the server host block 10800 port {code:java} iptables -A INPUT -p tcp --dport 10800 -j DROP {code} 4) Check "\{clientType}.ActiveSessions". We will see one connection. 5) Stop jdbc or thin client 6) Check "\{clientType}.ActiveSessions". We will still see one connection in "\{clientType}.ActiveSessions". 7) After about 2 hours, the metric will have a negative value = -1 Another case with proxy: Steps to reproduce: 1) Start server 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no updated in case of connection > problem/lost > - > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no correctly updated in case when we > have a problems with connection. > > Steps to reproduce: > 1) Start server > 2) Start jdbc or thin client > 3) On the server host block 10800 port > {code:java} > iptables -A INPUT -p tcp --dport 10800 -j DROP {code} > 4) Check "\{clientType}.ActiveSessions". We will see one connection. > 5) Stop jdbc or thin client > 6) Check "\{clientType}.ActiveSessions". We will still see one connection in > "\{clientType}.ActiveSessions". > 7) After about 2 hours, the metric will have a negative value = -1 > > Another case with proxy: > > Steps to reproduce: > 1) Start server > 2) Start Proxy server for remote port 10800 and local port 1024 > 3) Start jdbc or thin client with connecting to proxy server > {code:java} > ClientConfiguration cfg = new > ClientConfiguration().setAddresses("127.0.0.1:1024"); > IgniteClient igniteClient = Ignition.startClient(cfg); > IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no updated in case of connection problem/lost
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Summary: {clientType}.ActiveSessions metrics no updated in case of connection problem/lost (was: {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn) > {clientType}.ActiveSessions metrics no updated in case of connection > problem/lost > - > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 and local port 1024 > 3) Start jdbc or thin client with connecting to proxy server > {code:java} > ClientConfiguration cfg = new > ClientConfiguration().setAddresses("127.0.0.1:1024"); > IgniteClient igniteClient = Ignition.startClient(cfg); > IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 and local port 1024 3) Start jdbc or thin client with connecting to proxy server {code:java} ClientConfiguration cfg = new ClientConfiguration().setAddresses("127.0.0.1:1024"); IgniteClient igniteClient = Ignition.startClient(cfg); IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 and local port 1024 > 3) Start jdbc or thin client with connecting to proxy server > {code:java} > ClientConfiguration cfg = new > ClientConfiguration().setAddresses("127.0.0.1:1024"); > IgniteClient igniteClient = Ignition.startClient(cfg); > IgniteClient igniteClient2 = Ignition.startClient(cfg); {code} > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\\{clientType} .ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: \\{clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType\}.ActiveSessions metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. Although the > "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics > are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy > server for remote port 10800 3) Start jdbc or thin client with connecting to > proxy server 4) Check "\\{clientType} > .ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\\{clientType} .ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: "\{clientType}.ActiveSessions" metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > "\{clientType}.ActiveSessions" metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType} .ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions > metrics no decrease in case when we use thin/jdbc client with proxy or vpn > connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType} .ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType} > .ActiveSessions metrics no decrease in case when we use thin/jdbc client with > proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: _{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster._ Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: \\{clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > \\{clientType\}.ActiveSessions metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType} .ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: _{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster._ Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > _{clientType}.ActiveSessions metrics no decrease in case when we use > thin/jdbc client with proxy or vpn connection to cluster._ > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster.Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster.Although the > "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics > are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster.Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType} .ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType} > .ActiveSessions metrics no decrease in case when we use thin/jdbc client with > proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Attachment: ProxyServer.java > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType} > .ActiveSessions metrics no decrease in case when we use thin/jdbc client with > proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". > We will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check " {clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType} .ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will still see one connection in "\{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check " {clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "\{clientType} .ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check " > {clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still > see one connection in "\{clientType} > .ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[ https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17554: --- Description: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". was: {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". > {clientType}.ActiveSessions metrics no decrease in case of connection through > proxy/vpn > --- > > Key: IGNITE-17554 > URL: https://issues.apache.org/jira/browse/IGNITE-17554 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: ProxyServer.java > > > {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc > client with proxy or vpn connection to cluster. > Although the "ClientListenerProcessor.Connections" and > "views.CLIENT_CONNECTIONS" metrics are updated correctly. > Steps to reproduce: > 1) Start Cluster > 2) Start Proxy server for remote port 10800 > 3) Start jdbc or thin client with connecting to proxy server > 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will see one connection. > 5) Stop jdbc or thin client > 6) Stop Proxy server > 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We > will still see one connection in "{clientType}.ActiveSessions" and no > connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
Stepanov Ilya created IGNITE-17554: -- Summary: {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn Key: IGNITE-17554 URL: https://issues.apache.org/jira/browse/IGNITE-17554 Project: Ignite Issue Type: Bug Affects Versions: 2.13 Reporter: Stepanov Ilya {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc client with proxy or vpn connection to cluster. Although the "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy server for remote port 10800 3) Start jdbc or thin client with connecting to proxy server 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection. 5) Stop jdbc or thin client 6) Stop Proxy server 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see one connection in "{clientType}.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node !createSnapshot_nonCrd.PNG|width=426,height=212! 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node !createSnapshot_nonCrd.PNG|width=426,height=212! 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > !createSnapshot_nonCrd.PNG|width=426,height=212! > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: createSnapshotCrd.jp2 > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: (was: createSnapshotCrd.jp2) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Attachment: error.log Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > Attachments: error.log > > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Description: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) check "LastSnapshotErrorMessage" coordinator node was: In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) execute "LastSnapshotErrorMessage" coordinator node > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) check "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
Stepanov Ilya created IGNITE-17552: -- Summary: Empty SnapshotErrorMessage on non-coordinator node Key: IGNITE-17552 URL: https://issues.apache.org/jira/browse/IGNITE-17552 Project: Ignite Issue Type: Bug Affects Versions: 2.13 Reporter: Stepanov Ilya In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated. This is misleading that the snapshot was taken successfully. Steps to reproduce: 1) Create cluster with 2+ nodes 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node 3) check "LastSnapshotErrorMessage" on non-coordinator node 4) execute "createSnapshot" with non-existent path on coordinator node 5) execute "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-17552: --- Ignite Flags: (was: Docs Required,Release Notes Required) > Empty SnapshotErrorMessage on non-coordinator node > -- > > Key: IGNITE-17552 > URL: https://issues.apache.org/jira/browse/IGNITE-17552 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.13 >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > In some cases, when we execute "createSnapshot" on non-coordinator node, the > snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but > the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are > updated. > This is misleading that the snapshot was taken successfully. > Steps to reproduce: > 1) Create cluster with 2+ nodes > 2) execute "createSnapshot" with non-existent path(example: /bad/path) on > non-coordinator node > 3) check "LastSnapshotErrorMessage" on non-coordinator node > 4) execute "createSnapshot" with non-existent path on coordinator node > 5) execute "LastSnapshotErrorMessage" coordinator node -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Labels: ise (was: ) > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > Labels: ise > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1]are not > enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount"[1] are > not enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16648) Add histogram metrics for thread pools tasks
[ https://issues.apache.org/jira/browse/IGNITE-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stepanov Ilya updated IGNITE-16648: --- Description: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are not enough Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] was: Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" are not enough [1] Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms|https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > Add histogram metrics for thread pools tasks > > > Key: IGNITE-16648 > URL: https://issues.apache.org/jira/browse/IGNITE-16648 > Project: Ignite > Issue Type: Improvement >Reporter: Stepanov Ilya >Priority: Minor > > Right now, we don't have a way to estimate the speed of task execution for a > thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" [1] are > not enough > > Suggestions: add histogram[2] metrics for thread pools tasks. Similar to > PutTime/GetTime/etc... for caches > > [1] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] > [2] - > [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16648) Add histogram metrics for thread pools tasks
Stepanov Ilya created IGNITE-16648: -- Summary: Add histogram metrics for thread pools tasks Key: IGNITE-16648 URL: https://issues.apache.org/jira/browse/IGNITE-16648 Project: Ignite Issue Type: Improvement Reporter: Stepanov Ilya Right now, we don't have a way to estimate the speed of task execution for a thread pools. Metrics such as "QueueSize" and "CompletedTaskCount" are not enough [1] Suggestions: add histogram[2] metrics for thread pools tasks. Similar to PutTime/GetTime/etc... for caches [1] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#thread-pools] [2] - [https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms|https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics-system#histograms] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16499) Сonsistency check command should support IGNITE_TO_STRING_INCLUDE_SENSITIVE option
Stepanov Ilya created IGNITE-16499: -- Summary: Сonsistency check command should support IGNITE_TO_STRING_INCLUDE_SENSITIVE option Key: IGNITE-16499 URL: https://issues.apache.org/jira/browse/IGNITE-16499 Project: Ignite Issue Type: Sub-task Reporter: Stepanov Ilya Because keys and values are sensitive data, we need to provide for disabling the possible output of these data to the log. Suggestion: add support for the "IGNITE_TO_STRING_INCLUDE_SENSITIVE" option in the consistency command(Read Repair). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-14753) Build via maven 3.8.1 fails
Ilya created IGNITE-14753: - Summary: Build via maven 3.8.1 fails Key: IGNITE-14753 URL: https://issues.apache.org/jira/browse/IGNITE-14753 Project: Ignite Issue Type: Improvement Components: general Reporter: Ilya Assignee: Ilya Building ignite with latest maven (3.8.1) fails due to http blocking policy. https://maven.apache.org/docs/3.8.1/release-notes.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14720) Remove warning about disabling explicit GC
[ https://issues.apache.org/jira/browse/IGNITE-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17345965#comment-17345965 ] Ilya commented on IGNITE-14720: --- [~ilyak] please take a look to dev list [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Proposal-to-remove-explicit-quot-GC-disable-quot-startup-suggestion-td52624.html]. I assume that we can move forward. > Remove warning about disabling explicit GC > -- > > Key: IGNITE-14720 > URL: https://issues.apache.org/jira/browse/IGNITE-14720 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Pligin >Assignee: Ilya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Right now we suggest the following > {code:java} > INFO: ^-- Disable processing of calls to System.gc() (add > '-XX:+DisableExplicitGC' to JVM options){code} > It does not make sense anymore (people don't call gc() when not needed) and > may actually prevent JVM from reclaiming heap and the failing due to running > out of direct memory buffers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14720) Remove warning about disabling explicit GC
[ https://issues.apache.org/jira/browse/IGNITE-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya reassigned IGNITE-14720: - Assignee: Ilya > Remove warning about disabling explicit GC > -- > > Key: IGNITE-14720 > URL: https://issues.apache.org/jira/browse/IGNITE-14720 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Pligin >Assignee: Ilya >Priority: Major > > Right now we suggest the following > {code:java} > INFO: ^-- Disable processing of calls to System.gc() (add > '-XX:+DisableExplicitGC' to JVM options){code} > It does not make sense anymore (people don't call gc() when not needed) and > may actually prevent JVM from reclaiming heap and the failing due to running > out of direct memory buffers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-7826) DStatProbe benchmark empty result output
Burov Ilya created IGNITE-7826: -- Summary: DStatProbe benchmark empty result output Key: IGNITE-7826 URL: https://issues.apache.org/jira/browse/IGNITE-7826 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.3 Environment: Ubuntu 17.10 apache-ignite-fabric-2.3.0-bin Dstat 0.7.3 Platform posix/linux2 Kernel 4.13.0-36-generic Python 2.7.14 (default, Sep 23 2017, 22:06:14) [GCC 7.2.0] Terminal type: xterm-256color (color support) Reporter: Burov Ilya Attachments: DStatProbe.csv, dstat.log DStatProbe creates empty result csv report due to dstat command output parsing error. Sample csv file and part of driver log included. -- This message was sent by Atlassian JIRA (v7.6.3#76005)