Stanilovsky Evgeny created IGNITE-10797:
---
Summary: Replace unused methods from IgniteCacheSnapshotManager.
Key: IGNITE-10797
URL: https://issues.apache.org/jira/browse/IGNITE-10797
Project: Ignit
Oleg Ignatenko created IGNITE-10796:
---
Summary: migrate from JUnit 3 to 4 suites involving IgniteTestSuite
Key: IGNITE-10796
URL: https://issues.apache.org/jira/browse/IGNITE-10796
Project: Ignite
I’ve done a quick superficial review. Didn’t look at the tests, didn’t dive
into the design, etc, just the code.
I’ve left some comments – almost all are about minor issues, grammar and code
style.
Stan
From: Vyacheslav Daradur
Sent: 21 декабря 2018 г. 14:58
To: dev@ignite.apache.org
Subject:
I thought about the same thing when using machines with Docker installed – it
seems that regex/subnet exclusion really would help.
I wonder if there are corner cases when it wouldn’t work well though.
We’d need to handle this in both TcpCommunicationSpi and TcpDiscoverySpi.
Probably even some vie
OK, even though the name “ELB” applies to both the old and the new IpFinder
in my opinion it isn’t really enough to change the name of the API classes now.
BTW in the docs the features are called Application Load Balancer and Classic
Load Balancer,
so the abbreviations would be ALB and CLB, not A
