Dmitriy Pavlov created IGNITE-11962:
---
Summary: [TC Bot] Test threated as recently contributed even if
there were runs outside 21 days
Key: IGNITE-11962
URL: https://issues.apache.org/jira/browse/IGNITE-11962
Ivan Bessonov created IGNITE-11963:
--
Summary: Remove ContinuousQueryDeserializationErrorOnNodeJoinTest
Key: IGNITE-11963
URL: https://issues.apache.org/jira/browse/IGNITE-11963
Project: Ignite
Folks,
Just a minor update.
RunAll [1] with enabled ReadRepair proxy is almost green now (~10 tests
left, started with 6k :)).
During the analisys, I've found some tests with
- unexpected repairs at tx caches
- inconsistent state after the test finished (different entries across the
topology)
For
Fix merged to master.
Guys, thanks for the help!
В Вт, 02/07/2019 в 18:25 +0300, Alexey Goncharuk пишет:
> Hello Nikolay,
>
> I will take a look shortly.
>
> вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov :
>
> > Guys.
> >
> > I've prepared PR to fix this issue.
> > Who want to review it?
> >
>
Vladimir Malinovskiy created IGNITE-11964:
-
Summary: Code style failed
Key: IGNITE-11964
URL: https://issues.apache.org/jira/browse/IGNITE-11964
Project: Ignite
Issue Type: Bug
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
I've just added this suite to list of trusted. This means that exit code
(and any other build problem) in this suite is a reason to notify.
For all other suites, only some specific build problems (OOME, Timeout,
Crash) causes notification.
Thanks to N. Izikov, this issue is already solved.
чт, 4
I discussed this issue with Denis and we decided to remove this test
completely as it is invalid after my changes. Corresponding issue: [1]
[1] https://issues.apache.org/jira/browse/IGNITE-11963
чт, 4 июл. 2019 г. в 08:25, Павлухин Иван :
> Seems to be an interference of two commits related to c
Dmitry,
I'm aware of failing tests, will check in nearest time.
пн, 1 июл. 2019 г. в 22:04, Dmitriy Pavlov :
> I've checked Pavel's change and it is .NET only
> https://issues.apache.org/jira/browse/IGNITE-11867
> I guess this change may have an effect on other tests
>
> пн, 1 июл. 2019 г. в 21:
Igniters,
I rethought the issue and I see some problems:
1. It seems that in most cases bucket boundaries configuration will be
problem for user. Absolute values for latency boundaries it is very
odd choice.
2. Also seems that latency for most caches (if we configure cache
metrics fro example) wi
Andrey Aleksandrov created IGNITE-11965:
---
Summary: Pyton client: Expiration policies are missed
Key: IGNITE-11965
URL: https://issues.apache.org/jira/browse/IGNITE-11965
Project: Ignite
Andrey Aleksandrov created IGNITE-11966:
---
Summary: Using AdaptiveLoadBalancingSpi without
IgniteConfiguration.setIncludeEventTypes(EventType.EVT_TASK_FINISHED,
EventType.EVT_TASK_FAILED) leads to memory leak
Key: IGNITE-11
Hi Igniters,
As you know, Ignite SQL engine is tightly coupled with the H2 database that
provides basic parsing and query execution capabilities. This synergy has
worked well for a while until Ignite SQL engine got a much broader adoption
for all sort of use cases.
Presently, there is a list of
Hi Denis,
As you know, some time ago I've started a discussion about removing
dependence from gridgain:shmem. Ignite community seems to be not so much
interested in this removal, for now. So once added it could stay here
forever. Reverse dependency direction seems to be more natural. It is like
th
Hello, Denis.
Who can contribute to gridgain/h2?
Who are commiters of gridgain/h2?
В Чт, 04/07/2019 в 19:26 +0300, Dmitriy Pavlov пишет:
> Hi Denis,
>
> As you know, some time ago I've started a discussion about removing
> dependence from gridgain:shmem. Ignite community seems to be not so muc
Hello, Andrey.
> 3. I can't imagine that adequate values will be chosen on project
> setup stage.
Configuration file required in the case we adds new node or replace existing to
the cluster.
Use can have parameters similar to Ignite configuration, log configuration
files.
> My proposal is addi
16 matches
Mail list logo
