Question about extra backward connection in Discovery.

Hi, Igniters. Does anyone know or remember the reason of the additional 'backward ping' when some node loses the connection to its next in the ring? The ticket is [1]. Consider: 1) There is a cluster with nodes 'A', 'B, 'C' 2) 'A' fails to negotiate with B by the discovery, tries to establish a

Re: Hostname Dns Check on Connection Ignite server

    Hi, Yunus!     There is a fix for similar case: https://issues.apache.org/jira/browse/IGNITE-21630 If the hostname is a clear IP, it shouldn't be resolved any more. On 28.03.2024 16:48, Yunus Emre Tekin wrote: Hello, We are using apache ignite in our projects. We realized that while a c

[DISCUSSION] IEP-114: Custom Metrics

Hi, Igniters! I'd like to propose a new feature - Custom Metrics. This would allow a user to register his own measurement and monitoring values. Short IEP description: 1. Custom metrics are convenient to gather different application metrics using the same client/platform/API. Or when the existin

Re: New Apache Ignite PMC member: Nikita Amelchev

    Wow! Congrats! On 22.11.2023 13:17, Pavel Pereslegin wrote: Congratulations, Nikita! ср, 22 нояб. 2023 г. в 13:11, Aleksandr Pakhomov : Congratulations! On 21 Nov 2023, at 18:18, Dmitriy Pavlov wrote: Hello Igniters, The Project Management Committee (PMC) for Apache Ignite has invite

Re: [DISCUSSION] Service awareness for thin client.

ticket? On Thu, Oct 26, 2023 at 1:30 PM Vladimir Steshin wrote: Roman, hi. Done. Thanks! On 26.10.2023 13:25, Roman Puchkovskiy wrote: Hi Vladimir. Sorry to intervene, but we have a clash with IEP numbers, there is already IEP-110 in Ignite 3, it was created on August, 1: https

Re: [DISCUSSION] Service awareness for thin client.

+synchronization%3A+basic+schema+changes Is it possible to pick another number, while your IEP is fresh? чт, 26 окт. 2023 г. в 14:05, Vladimir Steshin : All right. Pavel, thank you. IEP: https://cwiki.apache.org/confluence/display/IGNITE/IEP-110+Thin+Client+Service+Awareness Ticket: https

Re: [DISCUSSION] Service awareness for thin client.

pt by client while it exists even if is not in use any more. If the suggestion looks reasonable, I'm ready to implement, create IEP. On 17.10.2023 18:28, Vladimir Steshin wrote: They barely can guarantee. If client miss service instance node, the request is just redirected. But I talk

Re: [DISCUSSION] Service awareness for thin client.

while it exists even if is not in use any more. If the suggestion looks reasonable, I'm ready to implement, create IEP. On 17.10.2023 18:28, Vladimir Steshin wrote:     They barely can guarantee. If client miss service instance node, the request is just redirected. But I talk abou

Re: [DISCUSSION] Service awareness for thin client.

16, 2023 at 8:17 PM Vladimir Steshin wrote: Hi Igniters! I propose to add the /service awareness feature to the thin client/. I remember a couple of users asked of it. Looks nice to have and simple to implement. Similar to the partition awareness. Reason: A service can be deployed only on one or few n

[DISCUSSION] Service awareness for thin client.

Hi Igniters! I propose to add the /service awareness feature to the thin client/. I remember a couple of users asked of it. Looks nice to have and simple to implement. Similar to the partition awareness. Reason: A service can be deployed only on one or few nodes. Currently, the thin client choo

Re: [VOTE] Release Apache Ignite 2.15.0 RC0

+ 1 26.04.2023 22:51, Alex Plehanov пишет: Dear Community, The release candidate is ready. I have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/ https://dist.apache.org/repos/dist/dev/ignite/packages_2.15.0-rc0/ The following staging can be used for te

Re: Deprecated GridSslContextFactory removal

+1 24.04.2023 15:49, Николай Ижиков пишет: +1 24 апр. 2023 г., в 14:56, Taras Ledkov написал(а): +1 for remove

Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]

+1 29.03.2023 21:56, Alex Plehanov пишет: Dear Ignite Community! I suggest starting Apache Ignite 2.15 release activities. We've accumulated more than two hundred resolved issues [1] with new features and bug fixes which are waiting for release. The major changes related to the proposed releas

Re: [VOTE] Release bug fix release pyignite-0.6.1-rc0

+ 1 15.02.2023 11:21, Ivan Daschinsky пишет: Dear Igniters! This is a patch release that contains an important fix for users of pyignite https://issues.apache.org/jira/browse/IGNITE-18788 Release candidate binaries for subj are uploaded and ready for vote You can find them here: https://dist

Re: [VOTE] Release pyignite 0.6.0.rc0

    Good job. +1 11.11.2022 16:40, Ivan Daschinsky пишет: Dear Igniters! Release candidate binaries for subj are uploaded and ready for vote You can find them here: https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.0.rc0 If you follow the link above, you will find source packages (*.z

Re: [ANNOUNCE] Welcome Mikhail Petrov as a new Committer

Mikhail, congratulations! 11.11.2022 11:20, Maxim Muzafarov пишет: The Project Management Committee (PMC) for Apache Ignite has invited Mikhail Petrov to become a committer and we are pleased to announce that they have accepted. Mikhail Petrov is an active contributor and community member, he m

Re: [DISCUSSION] Add DataStreamer's default per-node-batch-setting for PDS.

NodeParallelOperations), which for 1 kb entries and 16 threads gives (1kb * 512 * 16 * 8) = 64mb which is usually peanuts for server Java. Can you check the heap dump in your tests to see what actually occupies most of the heap? Thanks, Stan On 28 Oct 2022, at 11:54, Vladimir Steshin wrote:

[DISCUSSION] Add DataStreamer's default per-node-batch-setting for PDS.

    Hi Folks,     I found that Datastreamer may consume heap or use increased heap amount when loading into a persistent cache. This may happen with streamer's 'allowOverwite'==true and the cache is in PRIMARY_SYNC mode.     What I don't like here is that the case looks simple. Not the defau

Unmarshalable result from the MX beans

    Hi, Igniters.     We've found that invocation results from some MX beans might not be properly represented on clients like jconsole [1]. In the exception cases. We pass Ignite exceptions or JMException with Ignite exception causes to the client. And the client fails to unmarshal unknown e

Re: Proxy (GridServiceProxy) for local services if required

ll as relevant documentation updates. I don't think we need a vote. I will also change mine to +1 in the existing thread. -Val On Mon, Jan 24, 2022 at 11:23 AM Vladimir Steshin wrote: Sure. This is a simple change. These 2 fixes could go together. And the doc already has notes

Re: Proxy (GridServiceProxy) for local services if required

hould do both fixes together and also clearly document that using service() can lead to incorrect metrics. -Val On Fri, Jan 21, 2022 at 1:13 AM Vladimir Steshin wrote: Valentin, there are 2 notable issues: 1) Variate behavior of `/serviceProxy()/` depending on user setting. It can return both

Re: Proxy (GridServiceProxy) for local services if required

x27;m ok with the change. But I think we should do both fixes together and also clearly document that using service() can lead to incorrect metrics. -Val On Fri, Jan 21, 2022 at 1:13 AM Vladimir Steshin wrote: Valentin, there are 2 notable issues: 1) Variate behavior of `/serviceProxy()/` d

Re: Proxy (GridServiceProxy) for local services if required

o interact with a service. In that case, we need to do something with the service() method (deprecate it?). Or probably there are other ways to fix metrics? -Val On Thu, Jan 20, 2022 at 3:32 AM Vladimir Steshin wrote: Yes. Invocations from direct reference are not measured. This method

Re: Proxy (GridServiceProxy) for local services if required

actual problem. If the *only* way to have metrics is to have a proxy, then this should be the only way to interact with a service. In that case, we need to do something with the service() method (deprecate it?). Or probably there are other ways to fix metrics? -Val On Thu, Jan 20, 2022 at

Re: Proxy (GridServiceProxy) for local services if required

y will get a runtime exception. But I believe that it is an obvious failure, and it should be fixed on the user side. On Mon, Dec 27, 2021 at 10:26 PM Vladimir Steshin < vlads...@gmail.com> wrote: Hi, Igniters. I'd like to suggest modifying `/IgniteServices.serviceProxy(S

[VOTE] Service proxy for local service by 'IgniteServices#serviceProxy()'

    Hi, Igniters.     Should we return a proxy even for local services by 'IgniteServices#serviceProxy()'? *I vote +1*, let's return proxy.     This question has recently raised again. Before the service metrics, we returned direct instance for local services. With service metrics enabled

Re: Proxy (GridServiceProxy) for local services if required

then they will get a runtime exception. But I believe that it is an obvious failure, and it should be fixed on the user side. On Mon, Dec 27, 2021 at 10:26 PM Vladimir Steshin < vlads...@gmail.com> wrote: Hi, Igniters. I'd like to suggest modifying `/IgniteServices.servic

Re: Proxy (GridServiceProxy) for local services if required

    Valentin, hi. "Could you elaborate on why we count metrics incorrectly when theserviceProxy() returns an instance of a local service instead of an actual proxy?" Local instance executes direct calls without any wrapping and doesn't measure itself. That's why we bring proxy by 'serviceProxy(

Re: Proxy (GridServiceProxy) for local services if required

will enable metrics (even with such docs!) and will be using casting proxy(!) to an implementation, then they will get a runtime exception. But I believe that it is an obvious failure, and it should be fixed on the user side. On Mon, Dec 27, 2021 at 10:26 PM Vladimir Steshin wrote: Hi, Ignite

Re: [VOTE] @Nullable/@NotNull annotation usage in Ignite 3

+1 for option 2 13.01.2022 13:25, Alexander Polovtcev пишет: Dear Igniters, In this thread we've discussed possible approaches to using null-related annotations. As the result, the following approaches were proposed: 1. Use

Re: [VOTE] Release Apache Ignite 2.12.0 RC2

+1 10.01.2022 15:52, Nikita Amelchev пишет: Dear Community, The release candidate (2.12.0-rc2) is ready. I have uploaded a release candidate to: https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/ https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/ The following staging c

Proxy (GridServiceProxy) for local services if required

Hi, Igniters. I'd like to suggest modifying `/IgniteServices.serviceProxy(String name, Class svcItf, boolean sticky)/` so that it may return proxy even for local service. Motivation: service metrics [1]. To measure method call we need to wrap service somehow. Also, the method name says `prox

Re: Defrag?

            Hi, Ryan. Current implementation doesn’t share free pages among cache partitions when persistence is enabled. This happens because page is bound to certain partition file and cannot be ‘moved’ and reused in another partition. And there is no share of free pages among caches. Each h

[jira] [Created] (IGNITE-14452) Add cehcking of the iptables settings applied.

Vladimir Steshin created IGNITE-14452: - Summary: Add cehcking of the iptables settings applied. Key: IGNITE-14452 URL: https://issues.apache.org/jira/browse/IGNITE-14452 Project: Ignite

[jira] [Created] (IGNITE-14437) Adjust test params: exclude input net failures with disabled connRecovery

Vladimir Steshin created IGNITE-14437: - Summary: Adjust test params: exclude input net failures with disabled connRecovery Key: IGNITE-14437 URL: https://issues.apache.org/jira/browse/IGNITE-14437

[jira] [Created] (IGNITE-14378) Remove delay from node ping.

Vladimir Steshin created IGNITE-14378: - Summary: Remove delay from node ping. Key: IGNITE-14378 URL: https://issues.apache.org/jira/browse/IGNITE-14378 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-14377) Enchance log of node ping failure.

Vladimir Steshin created IGNITE-14377: - Summary: Enchance log of node ping failure. Key: IGNITE-14377 URL: https://issues.apache.org/jira/browse/IGNITE-14377 Project: Ignite Issue Type

[jira] [Created] (IGNITE-14096) Try to bring randomization in node waiting with TcpDiscoverySpi.reconnectDelay.

Vladimir Steshin created IGNITE-14096: - Summary: Try to bring randomization in node waiting with TcpDiscoverySpi.reconnectDelay. Key: IGNITE-14096 URL: https://issues.apache.org/jira/browse/IGNITE-14096

[jira] [Created] (IGNITE-14095) Try fasten cluster start in the ducktests with decreasing 'spi.reconnectDelay'

Vladimir Steshin created IGNITE-14095: - Summary: Try fasten cluster start in the ducktests with decreasing 'spi.reconnectDelay' Key: IGNITE-14095 URL: https://issues.apache.org/jira/browse/IG

[jira] [Created] (IGNITE-14068) Infinite node persistance in the ring while outcoming connections are lost

Vladimir Steshin created IGNITE-14068: - Summary: Infinite node persistance in the ring while outcoming connections are lost Key: IGNITE-14068 URL: https://issues.apache.org/jira/browse/IGNITE-14068

[jira] [Created] (IGNITE-14054) Improve discovery ducktest: add partial network drop.

Vladimir Steshin created IGNITE-14054: - Summary: Improve discovery ducktest: add partial network drop. Key: IGNITE-14054 URL: https://issues.apache.org/jira/browse/IGNITE-14054 Project: Ignite

[jira] [Created] (IGNITE-14053) Remove status check message at all.

Vladimir Steshin created IGNITE-14053: - Summary: Remove status check message at all. Key: IGNITE-14053 URL: https://issues.apache.org/jira/browse/IGNITE-14053 Project: Ignite Issue Type

[jira] [Created] (IGNITE-14038) Separate JVM settings in the ducktests.

Vladimir Steshin created IGNITE-14038: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14038 URL: https://issues.apache.org/jira/browse/IGNITE-14038 Project: Ignite Issue

[jira] [Created] (IGNITE-14037) Separate JVM settings in the ducktests.

Vladimir Steshin created IGNITE-14037: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14037 URL: https://issues.apache.org/jira/browse/IGNITE-14037 Project: Ignite Issue

[jira] [Created] (IGNITE-13980) Remove duplicated ping: status check message.

Vladimir Steshin created IGNITE-13980: - Summary: Remove duplicated ping: status check message. Key: IGNITE-13980 URL: https://issues.apache.org/jira/browse/IGNITE-13980 Project: Ignite

Re: [DISCUSSION] Java 11 for Ignite 3.0 development

My + for java 11 On 08.12.2020 15:00, Nikolay Izhikov wrote: +1 for using java 11. 8 дек. 2020 г., в 13:18, ткаленко кирилл написал(а): +1 08.12.2020, 12:48, "Philipp Masharov" : Hello! Andrey's arguments are solid. On Tue, Dec 8, 2020 at 12:23 PM Pavel Tupitsyn wrote: +1, Java 11 s

[jira] [Created] (IGNITE-13835) Improve discovery ducktape test to research small timeouts and behavior on large cluster.

Vladimir Steshin created IGNITE-13835: - Summary: Improve discovery ducktape test to research small timeouts and behavior on large cluster. Key: IGNITE-13835 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-13705) Fix middle node failed when failed next node and previous.

Vladimir Steshin created IGNITE-13705: - Summary: Fix middle node failed when failed next node and previous. Key: IGNITE-13705 URL: https://issues.apache.org/jira/browse/IGNITE-13705 Project

[jira] [Created] (IGNITE-13704) Try failuredetectionTimeout==500 in ducktape integration test.

Vladimir Steshin created IGNITE-13704: - Summary: Try failuredetectionTimeout==500 in ducktape integration test. Key: IGNITE-13704 URL: https://issues.apache.org/jira/browse/IGNITE-13704 Project

[jira] [Created] (IGNITE-13702) Fix description of soLibger for DiscoveryTcpSpi.

Vladimir Steshin created IGNITE-13702: - Summary: Fix description of soLibger for DiscoveryTcpSpi. Key: IGNITE-13702 URL: https://issues.apache.org/jira/browse/IGNITE-13702 Project: Ignite

[jira] [Created] (IGNITE-13695) Move javadoc of affection of several addresses on failure detection.

Vladimir Steshin created IGNITE-13695: - Summary: Move javadoc of affection of several addresses on failure detection. Key: IGNITE-13695 URL: https://issues.apache.org/jira/browse/IGNITE-13695

[jira] [Created] (IGNITE-13666) Disable socket linger in discovery ducktape test.

Vladimir Steshin created IGNITE-13666: - Summary: Disable socket linger in discovery ducktape test. Key: IGNITE-13666 URL: https://issues.apache.org/jira/browse/IGNITE-13666 Project: Ignite

[jira] [Created] (IGNITE-13663) Represent in the documenttion affection of several node addresses on failure detection v2.

Vladimir Steshin created IGNITE-13663: - Summary: Represent in the documenttion affection of several node addresses on failure detection v2. Key: IGNITE-13663 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-13662) Discribe soLinger setting in TCP Discovery and SSL issues.

Vladimir Steshin created IGNITE-13662: - Summary: Discribe soLinger setting in TCP Discovery and SSL issues. Key: IGNITE-13662 URL: https://issues.apache.org/jira/browse/IGNITE-13662 Project

[jira] [Created] (IGNITE-13646) Discovery ducktape test might have setting for socket linger.

Vladimir Steshin created IGNITE-13646: - Summary: Discovery ducktape test might have setting for socket linger. Key: IGNITE-13646 URL: https://issues.apache.org/jira/browse/IGNITE-13646 Project

[jira] [Created] (IGNITE-13645) Discovery ducktape test should detect failed nodes by asking the cluster.

Vladimir Steshin created IGNITE-13645: - Summary: Discovery ducktape test should detect failed nodes by asking the cluster. Key: IGNITE-13645 URL: https://issues.apache.org/jira/browse/IGNITE-13645

[jira] [Created] (IGNITE-13644) Close socket bravely.

Vladimir Steshin created IGNITE-13644: - Summary: Close socket bravely. Key: IGNITE-13644 URL: https://issues.apache.org/jira/browse/IGNITE-13644 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-13643) Fix long closing of the socker in ServerImpl (TcpDiscoverySpi)

Vladimir Steshin created IGNITE-13643: - Summary: Fix long closing of the socker in ServerImpl (TcpDiscoverySpi) Key: IGNITE-13643 URL: https://issues.apache.org/jira/browse/IGNITE-13643 Project

[jira] [Created] (IGNITE-13641) More logs for debugging DiscoveryTcpSpi

Vladimir Steshin created IGNITE-13641: - Summary: More logs for debugging DiscoveryTcpSpi Key: IGNITE-13641 URL: https://issues.apache.org/jira/browse/IGNITE-13641 Project: Ignite Issue

[jira] [Created] (IGNITE-13638) Bring log config to ducktape tests

Vladimir Steshin created IGNITE-13638: - Summary: Bring log config to ducktape tests Key: IGNITE-13638 URL: https://issues.apache.org/jira/browse/IGNITE-13638 Project: Ignite Issue Type

[jira] [Created] (IGNITE-13625) Make network timeout rely on failureDetectionTimeout in TcpDiscovery

Vladimir Steshin created IGNITE-13625: - Summary: Make network timeout rely on failureDetectionTimeout in TcpDiscovery Key: IGNITE-13625 URL: https://issues.apache.org/jira/browse/IGNITE-13625

[jira] [Created] (IGNITE-13620) Bind ignite node to 1 address in the ducktests

Vladimir Steshin created IGNITE-13620: - Summary: Bind ignite node to 1 address in the ducktests Key: IGNITE-13620 URL: https://issues.apache.org/jira/browse/IGNITE-13620 Project: Ignite

[jira] [Created] (IGNITE-13603) TcpDiscoverySpi seems do not drop network recovery state and it's timer.

Vladimir Steshin created IGNITE-13603: - Summary: TcpDiscoverySpi seems do not drop network recovery state and it's timer. Key: IGNITE-13603 URL: https://issues.apache.org/jira/browse/IGNITE-

[jira] [Created] (IGNITE-13602) Create discovery node failure test based on network malfunction emulation.

Vladimir Steshin created IGNITE-13602: - Summary: Create discovery node failure test based on network malfunction emulation. Key: IGNITE-13602 URL: https://issues.apache.org/jira/browse/IGNITE-13602

[jira] [Created] (IGNITE-13282) Fix TcpDiscoveryCoordinatorFailureTest.testClusterFailedNewCoordinatorInitialized()

Vladimir Steshin created IGNITE-13282: - Summary: Fix TcpDiscoveryCoordinatorFailureTest.testClusterFailedNewCoordinatorInitialized() Key: IGNITE-13282 URL: https://issues.apache.org/jira/browse/IGNITE-13282

[jira] [Created] (IGNITE-13208) Refactoring of IgniteSpiOperationTimeoutHelper

Vladimir Steshin created IGNITE-13208: - Summary: Refactoring of IgniteSpiOperationTimeoutHelper Key: IGNITE-13208 URL: https://issues.apache.org/jira/browse/IGNITE-13208 Project: Ignite

[jira] [Created] (IGNITE-13206) Represent in the doc affection of several node addresses on failure detection.

Vladimir Steshin created IGNITE-13206: - Summary: Represent in the doc affection of several node addresses on failure detection. Key: IGNITE-13206 URL: https://issues.apache.org/jira/browse/IGNITE-13206

[jira] [Created] (IGNITE-13205) Represent in logs, javadoc affection of several node addresses on failure detection.

Vladimir Steshin created IGNITE-13205: - Summary: Represent in logs, javadoc affection of several node addresses on failure detection. Key: IGNITE-13205 URL: https://issues.apache.org/jira/browse/IGNITE-13205

[jira] [Created] (IGNITE-13194) Fix testNodeWithIncompatibleMetadataIsProhibitedToJoinTheCluster()

Vladimir Steshin created IGNITE-13194: - Summary: Fix testNodeWithIncompatibleMetadataIsProhibitedToJoinTheCluster() Key: IGNITE-13194 URL: https://issues.apache.org/jira/browse/IGNITE-13194

[jira] [Created] (IGNITE-13134) Fix connection recovery timout.

Vladimir Steshin created IGNITE-13134: - Summary: Fix connection recovery timout. Key: IGNITE-13134 URL: https://issues.apache.org/jira/browse/IGNITE-13134 Project: Ignite Issue Type

Re: Question: network issues of single node.

tart a two-nodes cluster with the nodes that fail to discover each other and attach the logs from those. - Denis On Thu, Jun 4, 2020 at 1:57 PM Vladimir Steshin wrote: Denis, hi. Sorry, I didn’t catch your idea. Are you saying this can happen and suggest experiment? I’m not descripting

Re: Question: network issues of single node.

. Start a 2-nodes cluster booting node 3 and, for instance, node 5. Those won't be able to interconnect according to your description. Attach the log files from both nodes for analysis. This should be a networking issue. - Denis On Thu, Jun 4, 2020 at 1:24 PM Vladimir Steshin wrote:

Question: network issues of single node.

    Hi, Igniters.     I wanted to ask how one node may not be able to connect to another whereas rest of the cluster can. This got covered in [1]. In short: node 3 can't connect to nodes 4 and 5 but can to 1. At the same time, node 2 can connect to 4. Questions: 1) Is it real case? Where th

[jira] [Created] (IGNITE-13111) Simplify backward checking of node connection.

Vladimir Steshin created IGNITE-13111: - Summary: Simplify backward checking of node connection. Key: IGNITE-13111 URL: https://issues.apache.org/jira/browse/IGNITE-13111 Project: Ignite

Review request: IEP-45, Improvements of node failure detection.

    Hi, Igniters. Everyone is welcome to review several suggestions of reducing time of node failure detection - part of IEP-45: 1.IGNITE-13017 : Hardcoded timeout in re-marking node as alive. It can prolong detection of node failure. Solution: The hardcode simply removed. * 2.IGNITE-1301

[jira] [Created] (IGNITE-13090) Add parameter of connection check period to TcpDiscoverySpi

Vladimir Steshin created IGNITE-13090: - Summary: Add parameter of connection check period to TcpDiscoverySpi Key: IGNITE-13090 URL: https://issues.apache.org/jira/browse/IGNITE-13090 Project

[jira] [Created] (IGNITE-13040) Remove unused parameter from TcpDiscoverySpi.writeToSocket()

Vladimir Steshin created IGNITE-13040: - Summary: Remove unused parameter from TcpDiscoverySpi.writeToSocket() Key: IGNITE-13040 URL: https://issues.apache.org/jira/browse/IGNITE-13040 Project

[jira] [Created] (IGNITE-13018) Get rid of duplicated checking of failed node.

Vladimir Steshin created IGNITE-13018: - Summary: Get rid of duplicated checking of failed node. Key: IGNITE-13018 URL: https://issues.apache.org/jira/browse/IGNITE-13018 Project: Ignite

[jira] [Created] (IGNITE-13017) Remove delay of 200ms from re-marking failed node as alive.

Vladimir Steshin created IGNITE-13017: - Summary: Remove delay of 200ms from re-marking failed node as alive. Key: IGNITE-13017 URL: https://issues.apache.org/jira/browse/IGNITE-13017 Project

[jira] [Created] (IGNITE-13016) Remove hardcoded values/timeouts from backward checking of failed node.

Vladimir Steshin created IGNITE-13016: - Summary: Remove hardcoded values/timeouts from backward checking of failed node. Key: IGNITE-13016 URL: https://issues.apache.org/jira/browse/IGNITE-13016

[jira] [Created] (IGNITE-13015) Use nono time instead of currentMills() in node failure ddetection.

Vladimir Steshin created IGNITE-13015: - Summary: Use nono time instead of currentMills() in node failure ddetection. Key: IGNITE-13015 URL: https://issues.apache.org/jira/browse/IGNITE-13015

[jira] [Created] (IGNITE-13014) Remove long, double checking of node availability. Fix hardcoded values.

Vladimir Steshin created IGNITE-13014: - Summary: Remove long, double checking of node availability. Fix hardcoded values. Key: IGNITE-13014 URL: https://issues.apache.org/jira/browse/IGNITE-13014

[jira] [Created] (IGNITE-13012) Make node connection checking rely on the configuration. Simplify node ping routine.

Vladimir Steshin created IGNITE-13012: - Summary: Make node connection checking rely on the configuration. Simplify node ping routine. Key: IGNITE-13012 URL: https://issues.apache.org/jira/browse/IGNITE-13012

Re: Active nodes aliveness WatchDog

Hi everyone. I think we should check behavior of failure detection with tests or find them if already written. I’ll research this question and rise a ticket if a reproducer appears. 08.04.2020 12:19, Stephen Darlington пишет: Yes. Nodes are always chatting to each another even if there are

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

do you think? Thanks, Slava. чт, 2 апр. 2020 г. в 18:47, Vladimir Steshin : Ivan, hello. Thanks. I vote for keeping the comments as they are now :) Igniters, it seems we are agreed to merge [1]. And the ticked s to be reverted in future with new designed solution of keeping in-memory data after

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

-12779 01.04.2020 20:20, Ivan Rakov пишет: I don't think that making javadocs more descriptive can be considered as harmful code base enlargement. I'd recommend to extend the docs, but the last word is yours ;) On Tue, Mar 31, 2020 at 2:44 PM Vladimir Steshin wrote: Ivan, hi. I

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

ll data in the corresponding caches will be vanished as a result. Does this make sense? On Fri, Mar 27, 2020 at 12:00 PM Vladimir Steshin wrote: Ivan, hi. 1) >>> Is it correct? If we are on the same page, let's proceed this way It is correct. 2) - In many places in the code

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

es.apache.org/jira/browse/IGNITE-12701 [2]: https://issues.apache.org/jira/browse/IGNITE-12779 [3]: https://issues.apache.org/jira/browse/IGNITE-12614 -- Ivan On Tue, Mar 24, 2020 at 7:18 PM Vladimir Steshin wrote: Hi, Igniters. I'd like to remind you that cluster can be deactivated by user with 3 uti

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

Hi, Igniters. I'd like to remind you that cluster can be deactivated by user with 3 utilities: control.sh, *JMX and the REST*. Proposed in [1] solution is not about control.sh. It suggests same approach regardless of the utility user executes. The task touches *only* *API of the user calls*,

Re: Reference of local service.

ecate IgniteService.service(). WDYT? 17.03.2020 19:56, Vladimir Steshin пишет: Andrey, >>> Is it possible to return actual class instance instead of interface from serviceProxy() method? No, it is not possible. IgniteServiceImpl doesn't allow that: public T serviceProxy(final

Re: Reference of local service.

ce too and keep backward compatibility at the same time. Is it possible to return actual class instance instead of interface from serviceProxy() method? E.g. could I get ServiceImpl as result of method call instead of ServiceItf? On Tue, Mar 17, 2020 at 9:50 AM Vladimir Steshin wrote: Andrey, IgniteS

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

Nikolay, I think we should reconsider clearing at least system caches when deactivating. 17.03.2020 14:18, Nikolay Izhikov пишет: Hello, Vladimir. I don’t get it. What is your proposal? What we should do? 17 марта 2020 г., в 14:11, Vladimir Steshin написал(а): Nikolay, hi. And should

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

there is at lease one persistent data region then system data region also becomes persistent. Your example applies only to pure in-memory clusters. And should be covered with the —force parameter we added. What do you think? 17 марта 2020 г., в 13:45, Vladimir Steshin написал(а): Hi, all

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

    Hi, all. Fixes for control.sh and the REST have been merged. Could anyone take a look to the previous email with an issue? Isn't this conductvery wierd?

Re: Reference of local service.

LocalProxy(). It will not break backward compatibility and will always return proxy. On Thu, Mar 12, 2020 at 2:25 PM Vladimir Steshin wrote: Andrey, hi. We won’t affect existing services How exactly will we affect services without special interface? Please see the benchmarks in previous email.

Re: Reference of local service.

hods like nodeSingletonConfiguration(String name, Service > service) and clusterSingletonConfiguration(String name, Service > service). This methods will return configuration which has parameters > for given type of deployment and could be modified, e.g. metrics could > be enabled.

[jira] [Created] (IGNITE-12779) Split Ignite and IgniteMXBean, make different behavior of the active(boolean)

Vladimir Steshin created IGNITE-12779: - Summary: Split Ignite and IgniteMXBean, make different behavior of the active(boolean) Key: IGNITE-12779 URL: https://issues.apache.org/jira/browse/IGNITE-12779

[jira] [Created] (IGNITE-12773) Reduce number of cluster deactivation methods in internal API.

Vladimir Steshin created IGNITE-12773: - Summary: Reduce number of cluster deactivation methods in internal API. Key: IGNITE-12773 URL: https://issues.apache.org/jira/browse/IGNITE-12773 Project

Re: Reference of local service.

> service). This methods will return configuration which has parameters > for given type of deployment and could be modified, e.g. metrics could > be enabled. > > WDYT? > > On Wed, Mar 4, 2020 at 8:42 PM Vladimir Steshin > wrote: > > > > Vyacheslav, Denis, hi

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

Hi, Igniters. I've found other deactivation issue. Should we consider this behavior as a bug? IgniteEx ignite = startGrids(3);     IgniteAtomicLong atomicLong = ignite.atomicLong("atomic", 10L, true);     IgniteLock lock = ignite.reentrantLock("lock", true, false, true);    

  1   2   >