Igniters,
Now I spot blocking / long-running code arising from
{{GridDhtPartitionsExchangeFuture#init}} calls in partition-exchanger
thread, see [1]. Ideally, all blocking operations along all possible code
paths should be guarded implicitly from critical failure detector to avoid
the thread from
Hello, Igniters.
We made some progress yesterday.
Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create TeamCity
suite for Python thin client"
This ticket doesn't sound like a blocker to me. Let's exclude it from release
scope.
Thoughts?
Here is the list of remaining
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4966
IGNITE-9862 Web Console: Add support for "date", "time" and "date-andâ¦
â¦-time" to InputDialog.
You can merge this pull request into a Git repository by running:
$ git pull
Alexey Kuznetsov created IGNITE-9862:
Summary: Web Console: Add support for "date", "time" and
"date-and-time" on InputDialog
Key: IGNITE-9862
URL: https://issues.apache.org/jira/browse/IGNITE-9862
Github user antkr closed the pull request at:
https://github.com/apache/ignite/pull/4957
---
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/4965
Ignite 2.4.12
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12
Alternatively you can review and apply these
ololo3000 opened a new pull request #36: IGNITE-9645 [TC Bot] Add comparison of
failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/36
This is an automated message from the
ololo3000 closed pull request #25: IGNITE-9645 [TC Bot] Add comparison of
failed tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/25
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below
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
GitHub user dehasi opened a pull request:
https://github.com/apache/ignite/pull/4964
IGNITE-9284 Add standard scaler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dehasi/ignite
feature/ignite-9284-add-standard-scaler
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/4963
IGNITE-9861: Authorization object names must always be non-null.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4559
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4736
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4089
---
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4962
IGNITE-9710 Ignite watchdog service handles longrunning cache creation
You can merge this pull request into a Git repository by running:
$ git pull
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4015
---
Vitaliy Biryukov created IGNITE-9861:
Summary: Authorization object names must always be non-null.
Key: IGNITE-9861
URL: https://issues.apache.org/jira/browse/IGNITE-9861
Project: Ignite
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/4961
IGNITE-9739 don't write non-baseline nodes to wal TxRecord
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4960
Ignite-2.5.1-p14-hotfix-pme
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.5.1-p14-hotfix-pme
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4959
Ignite-2.5.1-p14-hotfix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p14-hotfix
Alternatively you
Andrey Kuznetsov created IGNITE-9860:
Summary: Unreliable listener invocation order in
GridDhtPartitionsExchangeFuture#onDone
Key: IGNITE-9860
URL: https://issues.apache.org/jira/browse/IGNITE-9860
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4854
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4859
---
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4958
Added IgniteDataTransferObject and deprecated VisorDataTransferObject
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/4957
Ignite 2.4.12 test
TC pre-run to check before pushing to 2.4 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Max Shonichev created IGNITE-9859:
-
Summary: add debug logging on resendPartitions cause
Key: IGNITE-9859
URL: https://issues.apache.org/jira/browse/IGNITE-9859
Project: Ignite
Issue Type:
Pavel Pereslegin created IGNITE-9858:
Summary: [Test Failed] SystemCacheNotConfiguredTest#test flaky
fails on TC (timeout).
Key: IGNITE-9858
URL: https://issues.apache.org/jira/browse/IGNITE-9858
Alexey Goncharuk created IGNITE-9857:
Summary: .NET: IgniteConfigurationTest.TestSpringXml is flaky in
master
Key: IGNITE-9857
URL: https://issues.apache.org/jira/browse/IGNITE-9857
Project:
Sergey Antonov created IGNITE-9856:
--
Summary: Add documentation for control.sh --cache config
Key: IGNITE-9856
URL: https://issues.apache.org/jira/browse/IGNITE-9856
Project: Ignite
Issue
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/4956
IGNITE-9853 option control.sh --cache config was added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Paul Anderson created IGNITE-9855:
-
Summary: Curious deadlock on shutdown when being polled over
Jetty/REST
Key: IGNITE-9855
URL: https://issues.apache.org/jira/browse/IGNITE-9855
Project: Ignite
Ivan Daschinskiy created IGNITE-9854:
Summary: NullPointerException in
PageMemoryImpl.refreshOutdatedPages during removing from segCheckpointPages
Key: IGNITE-9854
URL:
Sergey Antonov created IGNITE-9853:
--
Summary: control.sh show more information about cache configuration
Key: IGNITE-9853
URL: https://issues.apache.org/jira/browse/IGNITE-9853
Project: Ignite
Github user antonovsergey93 closed the pull request at:
https://github.com/apache/ignite/pull/4955
---
Igor Sapego created IGNITE-9852:
---
Summary: Create TeamCity suite for Python thin client
Key: IGNITE-9852
URL: https://issues.apache.org/jira/browse/IGNITE-9852
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4940
---
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/4955
GG-14300 option control.sh --cache config was added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gg-14300
asfgit closed pull request #34: IGNITE-9833 Update Master Trends metrics
URL: https://github.com/apache/ignite-teamcity-bot/pull/34
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a
Alexey,
Since PHP thin client is now in master, can you please add it to our
"Thin clients features" wiki page, so we can track the feature parity
of our clients?
[1] -
https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features
Best Regards,
Igor
On Wed, Oct 10, 2018 at 2:56 PM
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4951
---
Yury Gerzhedovich created IGNITE-9851:
-
Summary: Share local node statistics between all nodes
Key: IGNITE-9851
URL: https://issues.apache.org/jira/browse/IGNITE-9851
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4538
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4870
---
Hi Max-Pudov,
could you please take a look? This change goes also to 2.7, so this needs
to be investigated before release.
Vyacheslav, thank you for checking this failure. I will double check why
I've missed this failure during test validation.
Sincerely,
Dmitriy Pavlov
чт, 11 окт. 2018 г. в
The test fails with an errors related to Kafka, looks like the
possible cause is the following task:
https://issues.apache.org/jira/browse/IGNITE-9126 - Update Apache
Kafka dependency
On Thu, Oct 11, 2018 at 9:11 AM wrote:
>
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be
Alexey, we all agreed to merge in 2.7 blockers only.
Is this a blocker?
Anyway, you are more experienced Igniter that I am.
If you think we should include this ticket to 2.7 - please, do it.
В Чт, 11/10/2018 в 13:08 +0300, Alexey Goncharuk пишет:
> Nikolay,
>
> I am waiting for final benchmark
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4954
IGNITE-9749 MVCC: Assertion error in
JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite
hang
You can merge this pull request into a Git repository by running:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4950
---
GitHub user SpiderRus opened a pull request:
https://github.com/apache/ignite/pull/4953
FsyncModeFileWriteAheadLogManager can block forever in log() call
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Ok, I've filed a ticket [1] for the performance investigation and targeted
it to 2.8. Feel free to assign it to yourself.
I'm going to merge the ticket to master and ignite-2.7 branches by the
end of the week, if no one have any objections.
[1] - https://issues.apache.org/jira/browse/IGNITE-9850
dspavlov opened a new pull request #35: Ignite 9848 load all builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/35
This is an automated message from the Apache Git Service.
To respond to the message, please log
Igor Sapego created IGNITE-9850:
---
Summary: Python thin: Find out the cause of the python's client
low performance
Key: IGNITE-9850
URL: https://issues.apache.org/jira/browse/IGNITE-9850
Project: Ignite
Nikolay,
I am waiting for final benchmark results for 9784, after that I will merge
the change.
On the subject of Ignite 2.7 scope, our fellow Igniter Alexey Platonov have
found another case when a failure handler is incorrectly called on node
stop:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4939
---
Nikolai Kulagin created IGNITE-9849:
---
Summary: Remove invalid builds from the selection
Key: IGNITE-9849
URL: https://issues.apache.org/jira/browse/IGNITE-9849
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4947
---
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4952
IGNITE-9620
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9620-1
Alternatively you can review and apply
Stepan,
Thank you for answering my question and for the updated results.
I have ran the profiler (cProfile) against the benchmark code you
provided and have not found any particular bottleneck. One cycle took me
434 μs, which is the same order of magnitude as your result.
I will need more
Hello, Igniters.
We made a good progress yesterday.
Here is the list of remaining tickets(17) mapped to 2.7:
Alexey Goncharuk - IGNITE-9784
Taras Ledkov - IGNITE-9171
Andrey Kuznetsov - IGNITE-9737, IGNITE-9710
Peter Ivanov - IGNITE-9583, IGNITE-9823, IGNITE-9685
Igor
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4917
---
Dmitriy Pavlov created IGNITE-9848:
--
Summary: [TC Bot] Background upload of all builds from TC to the
bot DB
Key: IGNITE-9848
URL: https://issues.apache.org/jira/browse/IGNITE-9848
Project: Ignite
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4943
---
What kind of help is needed?
On Wed, Oct 10, 2018 at 11:51 PM Dmitriy Setrakyan
wrote:
> Vladimir Ozerov,
>
> Can you help with the unassigned MVCC tickets?
>
> D.
>
> On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > I list all contributors that assigned
Stanilovsky Evgeny created IGNITE-9847:
--
Summary: IgniteSet#contains hang indefinitely.
Key: IGNITE-9847
URL: https://issues.apache.org/jira/browse/IGNITE-9847
Project: Ignite
Issue
Dmitry,
pip install -e from latest sources
On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk,
wrote:
> Stepan!
>
> Please tell me one thing about how you created the environment for your
> benchmarks, namely: how did you install the Python client. Did you just
> do `pip install pyignite`, or did you
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
66 matches
Mail list logo
