Hello, the community!
Sometimes one needs to understand how long ago did the last checkpoint
start or end, how long was it, etc. There is lastCheckpointDuration already
- let’s add lastCheckpointStarted timestamp. From these two metrics, the
user can also figure out started + duration = ended and
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache (Restarts) 1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
No changes in the build
Hello, Yaroslav.
I support the idea.
But, we should carefully work with the release scope.
IGNITE-13477 - fix for a SQL tracing that will be available only in 2.10
IGNITE-13427 - fix for a new system view that exists in master only, we need to
include IGNITE-13409
Other tickets should be checke
Hi Ivan,
I've checked the ticket you provide. It contains subtasks to uncomment or
to remove some unused tests. It definitely describes some cases I've found.
So what do you think if I uncomment them in suites, add @Ignore annotation
for those tests while the tickets are open? This will help to fi
Nikolay Izhikov created IGNITE-13596:
Summary: Add flag to DataRecord to differentiate records on
primary and backup nodes
Key: IGNITE-13596
URL: https://issues.apache.org/jira/browse/IGNITE-13596
Hello, Igniters!
I've compiled a list of tickets that, i think, deserve to be released in a
minor Ignite release (meaning in 2.9.1) after 2.9. Here they are:
IGNITE-13569
disable archiving + walCompactionEnabled probably broke reading from wal on
server restart
IGNITE-13418
Deadlock on multiple
Ivan, as far as I understand, Max also created verification check for not
included test and found a few tests, that have never been included in any
testsuites.
Also, I suppose, that even if we cannot run some tests, these tests should
be ignored using annotation, but not commented.
пн, 19 окт. 20
Hi Max,
There is an existing effort about "abandoned" tests
https://issues.apache.org/jira/browse/IGNITE-9210
2020-10-19 16:25 GMT+03:00, Max Timonin :
> Hi Igniters!
>
> I made a research into tests that aren't included in any test suite. As
> TeamCity runs tests by suites so there could be test
Hi Veena,
As far as I know, CQ listeners should not be notified about
non-committed writes. I suppose that it is possible to reproduce a
described scenario, what does it show in practice?
Also it is important to know that all participating caches should be
TRANSACTIONAL and "update of cache b fai
Hi Igniters!
I made a research into tests that aren't included in any test suite. As
TeamCity runs tests by suites so there could be tests that never run on TC.
So I tried implementing a simple check for such tests and include it in
Ignite's travis config.
The check runs while "mvn test" command
Aleksey Plekhanov created IGNITE-13595:
--
Summary: Java thin client: Redundant CHM get/remove on each
request to server
Key: IGNITE-13595
URL: https://issues.apache.org/jira/browse/IGNITE-13595
Pr
Vladislav Pyatkov created IGNITE-13594:
--
Summary: Model classes require manual deserialization if used
inside Job loaded by p2p
Key: IGNITE-13594
URL: https://issues.apache.org/jira/browse/IGNITE-13594
Vladislav Pyatkov created IGNITE-13593:
--
Summary:
IgniteClientCacheStartFailoverTest.testRebalanceStateConcurrentStart (Cache 2)
is flaky
Key: IGNITE-13593
URL: https://issues.apache.org/jira/browse/IGNITE-1
Pavel Tupitsyn created IGNITE-13592:
---
Summary: .NET: Incorrect GetTotalPhysicalMemory result in Docker
Key: IGNITE-13592
URL: https://issues.apache.org/jira/browse/IGNITE-13592
Project: Ignite
Hello!
I think that if we move to netty, we should also move GridNioServer-using
code to netty. Let's avoid needing expertise in two socket multiplexing
frameworks.
Regards,
--
Ilya Kasnacheev
пн, 19 окт. 2020 г. в 10:52, Ivan Daschinsky :
> >> Why can't we use GridNioServer for java thin cli
Ilya Kazakov created IGNITE-13591:
-
Summary: Add getLastCheckpointStarted metric
Key: IGNITE-13591
URL: https://issues.apache.org/jira/browse/IGNITE-13591
Project: Ignite
Issue Type: Improvem
>> Why can't we use GridNioServer for java thin clients?
Yes, we can. Despite the naming, it can be used as client (set port as -1),
But doesn't have the same set of advantages as Netty. Netty has a way
better support (performance) for native transports and SSL, that
default java NIO.
But API is m
Pavel Vinokurov created IGNITE-13590:
Summary: Node fails with "Node with the same ID was found in node
IDs history" after missing TcpDiscoveryNodeAddedMessage
Key: IGNITE-13590
URL: https://issues.apache.org/
Pavel,
Why can't we use GridNioServer for java thin clients?
It has the same advantages as Netty (future based async API, SSL, etc) but
without extra dependency.
GridClient (control.sh), for example, uses GridNioServer for communication.
сб, 17 окт. 2020 г. в 11:21, Ivan Daschinsky :
> Hi.
> >>
19 matches
Mail list logo
