Ilya, good points, then support the idea of the API removal in 3.0.
Ivan, downloaded the screenshot to Google Drive:
https://drive.google.com/file/d/1N21N7yqCbeZtCNs1sHvJLiJfHF_Hp0wd/view?usp=sharing
-
Denis
On Fri, Dec 20, 2019 at 7:09 AM Ilya Kasnacheev
wrote:
> Hello!
>
> This module has
Hi Denis, Ivan
Thank you, I am glad you liked the webinar.
Please let me know if there are other opportunities where I can present on
Data Streaming and I would be happy to do a talk.
Regards,
Saikat
On Fri, Dec 20, 2019 at 1:44 AM Ivan Pavlukhin wrote:
> Saikat,
>
> I watched a recording
Ignite,
I've done a major overhaul of our contribution page that promotes
involvement in Ignite development:
https://ignite.apache.org/community/contribute.html
Many sections were simplified, some legacy stuff was removed and I'll
appreciate if some of you check the page and advise further
Pavel Tupitsyn created IGNITE-12481:
---
Summary: .NET: NuGet verification script does not handle
multi-digit version parts
Key: IGNITE-12481
URL: https://issues.apache.org/jira/browse/IGNITE-12481
Denis Mekhanikov created IGNITE-12480:
-
Summary: Add BinaryFieldExtractionSelfTest to the Binary Objects
test suite
Key: IGNITE-12480
URL: https://issues.apache.org/jira/browse/IGNITE-12480
Can we use "autocrlf" safely? AFAIR there were problems (in other
project) with some Windows specific stuff if CRLF is replaced to LF
automatically.
пт, 20 дек. 2019 г. в 17:31, Maxim Muzafarov :
>
> Andrey,
>
>
> I don't know why the issue [1] has an open status, but according to
> release notes
Hello!
This module has two obvious downsides:
- It's LGPL.
- It can only schedule locally.
We could fix 1) by using other implementation, but given 2) this no longer
sounds feasible. If someone wants to use local scheduler, why not just use
it directly?
Regards,
--
Ilya Kasnacheev
пт, 20
Andrey,
I don't know why the issue [1] has an open status, but according to
release notes [2] and checkstyle-PR [3] the default behaviour for the
check `NewlineAtEndOfFile` has changed to `lf_cr_crlf` and works.
Actually, you may probably find a long interesting discussion in this
PR [3] about
> but between to have something and have nothing i choose — something
We already have "something". put, get, etc. metrics. As I told early
it relatively useless. But the same metrics with histograms doesn't
add any value.
> i found 1 grid machine with very different io usage than others, «dig
>> And if we have two metrics that are triggered for the same then one of them
>> is useless.
> I don't understand what is the two metrics you are talking about.
Please, don't loose context. In your example it was checkpoint time
and some cache operation time.
> A business transaction includes
>> Is it become slower or faster?
>
>Very correct question! User saw "cache put time" metric becomes x2
>bigger. Does it become slower or faster? Or we just put into the cache
>values that 4x bigger in size? Or all time before we put values
>locally and now we put values on remote nodes. Or our
Folks,
The issue [1] already in master, submit minor fix with performance enhancements.
i think it`s not risky to gather it too.
thanks!
[1] https://issues.apache.org/jira/browse/IGNITE-12442
>Пятница, 20 декабря 2019, 16:09 +03:00 от Maxim Muzafarov :
>
>Folks,
>
>The issue [1] has pinned
Denis Mekhanikov created IGNITE-12479:
-
Summary: All binary types are registered twice
Key: IGNITE-12479
URL: https://issues.apache.org/jira/browse/IGNITE-12479
Project: Ignite
Issue
Kirill Tkalenko created IGNITE-12478:
Summary: Add long running operation timeout to MXBean for
manipulate in run-time
Key: IGNITE-12478
URL: https://issues.apache.org/jira/browse/IGNITE-12478
> And if we have two metrics that are triggered for the same then one of them
> is useless.
I don't understand what is the two metrics you are talking about.
I wrote about a single metric for a single cache operation.
> Obviously if you want know how fast or slow your business operation you
Folks,
The issue [1] has pinned to 2.8 and raised as the release blocker.
[1] https://issues.apache.org/jira/browse/IGNITE-12470
On Fri, 20 Dec 2019 at 16:04, Alexey Goncharuk
wrote:
>
> Anton,
>
> Shouldn't we target IGNITE-12470 to 2.8? It kind of does not make sense to
> add an ability to
Anton,
Shouldn't we target IGNITE-12470 to 2.8? It kind of does not make sense to
add an ability to disable potentially dangerous change only in the next
release.
чт, 19 дек. 2019 г. в 16:18, Anton Vinogradov :
> Pavel,
> Issue created - https://issues.apache.org/jira/browse/IGNITE-12470
>
>
> For example, the user saw «checkpoint time» metric becomes x2 bigger.
I just quote your words: " this is a trigger to make a deeper
investigation". And if we have two metrics that are triggered for the
same then one of them is useless.
> How it relates to business operations?
Why it should be
Singe, no objections here -> feature merged to 2.8.
On Thu, Dec 19, 2019 at 9:10 PM Николай Ижиков wrote:
> Good news, Anton!
>
> Thanks for your work on PME feature!
>
>
> > 19 дек. 2019 г., в 21:00, Anton Vinogradov написал(а):
> >
> > Folks,
> > "2.8 + cherrypicked pme-free switch" vs "2.8"
Ivan Pavlukhin created IGNITE-12477:
---
Summary: Slow test in Queries 1 test suite
Key: IGNITE-12477
URL: https://issues.apache.org/jira/browse/IGNITE-12477
Project: Ignite
Issue Type: Task
Ivan Pavlukhin created IGNITE-12476:
---
Summary: Slow test in Continuous Query 1 test suite
Key: IGNITE-12476
URL: https://issues.apache.org/jira/browse/IGNITE-12476
Project: Ignite
Issue
> It also will be visible on other metrics
How will it be visible?
For example, the user saw «checkpoint time» metric becomes x2 bigger.
How it relates to business operations? Is it become slower or faster?
What does it mean for an application performance?
On the other hand - if `PuTime`
> If a cache has some percent of the relatively slow transaction this is a
> trigger to make a deeper investigation.
It also will be visible on other metrics. So cache operations metrics
still useless because it transitive values.
>> 1. Measure some important internals (WAL operations,
Hello, Andrey.
> Where the sense in this value? I explained why this metrics are relatively
> useless.
I don’t agree with you.
I believe they are not useless for a user.
And I try to explain why I think so.
> But user can't distinguish one transaction from another, so his knowledge
> doesn't
+1, sounds reasonable to me.
Best Regards,
Igor
On Fri, Dec 20, 2019 at 10:25 AM Pavel Tupitsyn
wrote:
> +1, let's rename while we have a chance before 2.8 is released.
>
Amelchev Nikita created IGNITE-12475:
Summary: TDE - Phase-2. CLI process management
Key: IGNITE-12475
URL: https://issues.apache.org/jira/browse/IGNITE-12475
Project: Ignite
Issue Type:
> The goal of the proposed metrics is to measure whole cache operations
> behavior.
> It provides some kind of statistics(histograms) for it.
Nikolay, reformulating doesn't make metrics more meaningful. Seriously :)
> Yes, metrics will evaluate API call performance
And what? Where the sense in
27 matches
Mail list logo
