Ivan Pavlukhin created IGNITE-12001:
---
Summary: SchemaExchangeSelfTest.testServerRestartWithNewTypes is
flaky
Key: IGNITE-12001
URL: https://issues.apache.org/jira/browse/IGNITE-12001
Project:
Ivan Pavlukhin created IGNITE-12000:
---
Summary: IgniteSqlQueryMinMaxTest is flaky
Key: IGNITE-12000
URL: https://issues.apache.org/jira/browse/IGNITE-12000
Project: Ignite
Issue Type: Bug
Nikita,
Yes, I mean duration not timestamp. For the metric name, I suggest
"cacheOperationsBlockingDuration", I think it cleaner represents what is
blocked during PME.
We can also combine both timestamp "cacheOperationsBlockingStartTs" and
duration to have better correlation when cache operations
+1
пт, 19 июля 2019 г., 19:17 Denis Magda :
> Thanks Dmitry, this looks good to me.
>
> -
> Denis
>
>
> On Fri, Jul 19, 2019 at 9:08 AM Dmitriy Pavlov wrote:
>
> > Hi Igniters,
> > Please review following announce email for 2.7.5. I would like to send an
> > email during the weekend.
> > {{{
>
Thanks Dmitry, this looks good to me.
-
Denis
On Fri, Jul 19, 2019 at 9:08 AM Dmitriy Pavlov wrote:
> Hi Igniters,
> Please review following announce email for 2.7.5. I would like to send an
> email during the weekend.
> {{{
> The Apache Ignite Community is pleased to announce the release of
Pavel,
The main purpose of this metric is
>> how much time we wait for resuming cache operations
Seems I misunderstood you. Do you mean timestamp or duration here?
>> What do you think if we change the boolean value of metric to a long value
>> that represents time in milliseconds when
Hi Igniters,
Please review following announce email for 2.7.5. I would like to send an
email during the weekend.
{{{
The Apache Ignite Community is pleased to announce the release of Apache
Ignite 2.7.5.
Apache Ignite [1] is a memory-centric distributed database, caching,
and processing platform
Alexandr Shapkin created IGNITE-11999:
-
Summary: .NET unable to specify JvmDllPath for standalone node
Key: IGNITE-11999
URL: https://issues.apache.org/jira/browse/IGNITE-11999
Project: Ignite
Nikita,
I think getCurrentPmeDuration doesn't show useful information. The main PME
side effect for end-users is blocking cache operations. Not all PME time
blocks it.
What information gives to an end-user timestamp of
"timeSinceOperationsBlocked"? For what analysis it can be used and how?
пт,
Hi Pavel,
This time already can be obtained from the getCurrentPmeDuration and
new isOperationsBlockedByPme metrics.
As an alternative solution, I can rework recently added
getCurrentPmeDuration metric (not released yet). Seems for users it
useless in case of non-blocking PME.
Lets name it
Maxim,
Go ahead. I don't see any real usages of this functionality and seems it
obsolete and should be removed.
пт, 19 июл. 2019 г. в 08:36, Anton Vinogradov :
> Folks,
>
> To be clear, I'm going to merge the PR next Monday in case of interest lack
> (which means the feature is obsolete and can
Hi Nikita,
Thank you for working on this. What do you think if we change the boolean
value of metric to a long value that represents time in milliseconds when
operations were blocked?
Since we have not only JMX and now metrics are periodically exported to
some backend it can give a more clear
Anton, Nikolay,
Thanks for the support.
For now, we have the getCurrentPmeDuration() metric that does not show
influence on the cluster correctly. PME can be without blocking
operations. For example, client node join/leave events.
I suggest add new metric - isOperationsBlockedByPme(). Together,
Ivan Bessonov created IGNITE-11998:
--
Summary: Fix DataPageScan for fragmented pages.
Key: IGNITE-11998
URL: https://issues.apache.org/jira/browse/IGNITE-11998
Project: Ignite
Issue Type:
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 PDS (Direct IO) 2
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PdsDirectIo2=%3Cdefault%3E=buildTypeStatusDiv
No
Pavel Kuznetsov created IGNITE-11997:
Summary: TESTS: investigate long running tests in
IgniteCacheQueriesLoadTest1
Key: IGNITE-11997
URL: https://issues.apache.org/jira/browse/IGNITE-11997
Anton,
No doubts, just a lack of attention from my side. Thank you for clarifying.
Regarding MVCC, it's Beta state is mentioned in documentation [1] (a
warning badge in the beginning).
And I think it is a really good idea to employ some means of
delivering some experimental stuff. It can be
17 matches
Mail list logo
