Hello, Valentin.
I’m -1 to make Tracing API GA
> the API is stabilized, and there are no known performance issues associated
> with it.
For now, API works with strings only and this leads to huge performance
degradation when tracing enabled.
Our measurement shows about 50% drop.
Moreover,
Hello, Kirill.
> It is not possible for us to estimate how much space a user will need in the
> archive so as not to overflow it under its load
It still not clear for me why do we need those metrics.
Can you please, write down specific scenario - how user will use these metrics
to estimate
Cool drawing idea created IGNITE-14172:
--
Summary: Cool drawing ideas with pencil sketching
Key: IGNITE-14172
URL: https://issues.apache.org/jira/browse/IGNITE-14172
Project: Ignite
Igniters,
As far as I know, the tracing feature [1] is still marked as experimental.
However, It seems that we've had it for a while, it's being used, the API
is stabilized, and there are no known performance issues associated with it.
That said, should we remove the "experimental" mark and move
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-nightly MVCC Cache 7
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E
No changes in the build
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testConcurrentStart
Folks,
I'm going to cherry-pick these issues to the release branch, any objections?
Checkpointer thread holds write lock too long
https://issues.apache.org/jira/browse/IGNITE-14140
Incorrect initialize checkpoint-runner-cpu thread pool
https://issues.apache.org/jira/browse/IGNITE-14139
On
Hi, Nikolay!
It is not possible for us to estimate how much space a user will need in the
archive so as not to overflow it under its load. And the proposed metrics will
allow you to make a rough estimate.
12.02.2021, 17:23, "Nikolay Izhikov" :
> Hello, Kirill.
>
> Can you, please, clarify -
Hello, Igniters.
Currently, BasicBinaryNameMapper[isSimpleName=false] assumes that type names
equals both in Java and .Net.
• Java type - ru.company.Model
• .Net type - ‘ru.company.Model`
However, .net naming conventions [1] differs from java [2]
So, if a user follows both
Aleksey Plekhanov created IGNITE-14171:
--
Summary: Flaky
IgniteSpringBeanSpringResourceInjectionTest.testSpringResourceInjectedInService
Key: IGNITE-14171
URL:
Hello, Kirill.
Can you, please, clarify - What question about WAL user have in mind?
And what answers he(or she) gets with these new metrics?
> 12 февр. 2021 г., в 14:26, ткаленко кирилл написал(а):
>
> Hi everyone!
> At the moment, I have not found an opportunity to estimate how many WAL
>
Hi everyone!
At the moment, I have not found an opportunity to estimate how many WAL
segments fall into the archive, say per day.
So I created a ticket https://issues.apache.org/jira/browse/IGNITE-14170 to add
a couple of new metrics.
Kirill Tkalenko created IGNITE-14170:
Summary: Adding metrics of using WAL archive
Key: IGNITE-14170
URL: https://issues.apache.org/jira/browse/IGNITE-14170
Project: Ignite
Issue Type:
Nikolay Izhikov created IGNITE-14169:
Summary: .NET support standart java, .net naming conventions
Key: IGNITE-14169
URL: https://issues.apache.org/jira/browse/IGNITE-14169
Project: Ignite
14 matches
Mail list logo
