Nikolay, both commits fixed a regression compared to ignite-2.6. First one
was mentioned by Anton Kalashnikov before (java-level deadlock during WAL
flush), another - by Andrey Kuznetsov (NPE during a concurrent WAL flush).
--AG
ср, 3 окт. 2018 г. в 13:38, Nikolay Izhikov :
> Hello, Igniters.
>
Andrew Medvedev created IGNITE-9782:
---
Summary: Webconsole: Form too large
Key: IGNITE-9782
URL: https://issues.apache.org/jira/browse/IGNITE-9782
Project: Ignite
Issue Type: Bug
Hello, Igniters.
Release scope is frozen.
Please, if you include some new issues in release - discuss it in this thread.
Alexey, can you, please, comment on including fix for IGNITE-9760, IGNITE-9761
in 2.7 branch.
GitHub user luchnikovbsk opened a pull request:
https://github.com/apache/ignite/pull/4905
IGNITE-9719 Extra rebalanceThreadPoolSize check on client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/luchnikovbsk/ignite
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4906
IGNITE-9606: JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME
You can merge this pull request into a Git repository by running:
$ git pull
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4881
---
Ivan Rakov created IGNITE-9785:
--
Summary: Introduce read-only state in local node context
Key: IGNITE-9785
URL: https://issues.apache.org/jira/browse/IGNITE-9785
Project: Ignite
Issue Type: New
SomeFire commented on a change in 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#discussion_r222308185
##
File path:
SomeFire commented on a change in 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#discussion_r68058
##
File path:
SomeFire commented on a change in 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#discussion_r85591
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in 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#discussion_r89864
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in 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#discussion_r78498
##
File path:
SomeFire commented on a change in 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#discussion_r222307517
##
File path:
SomeFire commented on a change in 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#discussion_r63950
##
File path:
SomeFire commented on a change in 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#discussion_r72279
##
File path:
SomeFire commented on a change in 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#discussion_r71593
##
File path:
SomeFire commented on a change in 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#discussion_r89732
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
SomeFire commented on a change in 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#discussion_r63852
##
File path:
SomeFire commented on a change in 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#discussion_r222307974
##
File path:
Hi Igniters,
I see that https://issues.apache.org/jira/browse/IGNITE-9390 was resolved, but
.Net metrics tests are failing.
*New test failure in master DataRegionMetricsTest.TestMemoryMetrics
Taras Ledkov created IGNITE-9781:
Summary: JDK11: SSL handshake is failed
Key: IGNITE-9781
URL: https://issues.apache.org/jira/browse/IGNITE-9781
Project: Ignite
Issue Type: Bug
Affects
Hi Igniters,
After a short chat with Vladimir I understood the concern, it should be a
regression, but not just a bug, which existed for years. It is the case of
all fixes related to WAL nowadays.
I can research a bit which ticket caused regression, but I see no reason to
do if we already have
Ivan Pavlukhin created IGNITE-9783:
--
Summary: MVCC: Track all nodes participating in transaction
Key: IGNITE-9783
URL: https://issues.apache.org/jira/browse/IGNITE-9783
Project: Ignite
Github user pavlukhin closed the pull request at:
https://github.com/apache/ignite/pull/4873
---
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4903
IGNITE-9722
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9722-1
Alternatively you can review and apply
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4902
IGNTIE-9722
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9722-1
Alternatively you can review and apply
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4902
---
Aleksey Plekhanov created IGNITE-9780:
-
Summary: SQL system view for cache groups
Key: IGNITE-9780
URL: https://issues.apache.org/jira/browse/IGNITE-9780
Project: Ignite
Issue Type: Task
Alexey, thank you for the answer. I'd ask your advice about the
following question:
New Service Grid implementation listens to messages:
* ChangeGlobalStateMessage - to perform activation/deactivation actions;
* DynamicCacheChangeBatch - to handle caches stopping to undeploy
related affinity
SomeFire commented on a change in 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#discussion_r79867
##
File path:
SomeFire commented on a change in 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#discussion_r90983
##
File path: ignite-tc-helper-web/src/main/webapp/comparison.html
Hi Ignite Enthusiasts,
I would like to decrease pressure to dev list by removing GitBox comments
from being forwarded to dev@
I suggest we will create new list notificati...@ignite.apache.org and setup
GitBox comments to be sent to it instead of dev list.
Dmitrii Ryabov contacted Infra about
Alexey.
Sorry, I lost link to IGNITE-9760 in this thread :)
Thanks, for a clarification.
В Ср, 03/10/2018 в 13:58 +0300, Alexey Goncharuk пишет:
> Nikolay, both commits fixed a regression compared to ignite-2.6. First one
> was mentioned by Anton Kalashnikov before (java-level deadlock during
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4891
---
Hi Alexey,
Could you please assist with fixing test?
Sincerely,
Dmitriy Pavlov
сб, 29 сент. 2018 г. в 12:23, Dmitriy Pavlov :
> Folks,
>
> both tests are failed in ignite-2.7 IgniteStandByClusterTest.testSimple
>
Hi Nikolay, Igniters,
I've added the link to notes, and (as follow up related to the blockers/
non-blockers discussion) added several attributes of blockers. Please
review if you have a minute.
Sincerely,
Dmitriy Pavlov
вт, 2 окт. 2018 г. в 14:49, Nikolay Izhikov :
> Dmitriy, thank you.
>
> I
asfgit closed pull request #23: IGNITE-9541 Add row highlight for 'failed', add
title for columns, re…
URL: https://github.com/apache/ignite-teamcity-bot/pull/23
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4909
IGNITE-9126 Update Apache Kafka dependency
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9126
Alternatively
asfgit closed pull request #24: IGNITE-9697 Autocomplete branch for TC field
URL: https://github.com/apache/ignite-teamcity-bot/pull/24
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
Ilya Kasnacheev created IGNITE-9787:
---
Summary: Local Continuous Query skips rows during initial
rebalance of REPLICATED cache
Key: IGNITE-9787
URL: https://issues.apache.org/jira/browse/IGNITE-9787
Sorry, the previous email was not clear and not finished: Main repository
related emails from g...@git.apache.org (GitHub) will remain as is, so
regular PRs create and close will be forwarded as is.
If someone wants to redirect main repo-related PR notifications (as it was
suggested in Remove
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/4910
IGNITE-9390: Fixed memory metrics tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9390
Alternatively
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4907
IGNITE-9785 Introduce read-only state in local node context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9785
Yes, by Igniters, who will subscribe to it using
notifications-subscr...@ignite.apache.org . I'm going to subscribe.
I've heard complains about the volume of emails here, so it could be useful
to remove this one chunk from the dev.
For the record:
I suggest forwarding only emails from
Vladimir Ozerov created IGNITE-9786:
---
Summary: MVCC: simplify TX wait list management
Key: IGNITE-9786
URL: https://issues.apache.org/jira/browse/IGNITE-9786
Project: Ignite
Issue Type:
Github user Max-Pudov closed the pull request at:
https://github.com/apache/ignite/pull/4880
---
Will that list be read at all?
> On 3 Oct 2018, at 17:24, Dmitriy Pavlov wrote:
>
> Hi Ignite Enthusiasts,
>
> I would like to decrease pressure to dev list by removing GitBox comments
> from being forwarded to dev@
>
> I suggest we will create new list notificati...@ignite.apache.org and
Igniters,
We observe serious drop in SQL performance. Corresponding ticket with
"blocker" priority has been added to AI 2.7 scope [1].
[1] https://issues.apache.org/jira/browse/IGNITE-9784
On Wed, Oct 3, 2018 at 2:02 PM Nikolay Izhikov wrote:
> Alexey.
>
> Sorry, I lost link to IGNITE-9760 in
>
> It will be great if you can share your presentation/video after this summit
> in dev-list.
The video should be posted on this page in a couple of weeks:
https://www.imcsummit.org/2018/us/session/scalable-machine-and-deep-learning-apache-ignite
Did you use a TensorFlow integration stand in
Dmitriy, Vladimir,
We added an extra memory region for TxLog and this change wasn't
reflected in .Net tests.
I've made a trivial fix for these issues:
https://github.com/apache/ignite/pull/4910
Tests are OK:
https://ci.ignite.apache.org/viewLog.html?buildId=1999429=queuedBuildOverviewTab
Hi Roman,
thank you for stepping in and fixing tests.
The fix was merged into all branches.
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 22:30, Roman Kondakov :
> Dmitriy, Vladimir,
>
> We added an extra memory region for TxLog and this change wasn't
> reflected in .Net tests.
>
> I've made
Yury Gerzhedovich created IGNITE-9777:
-
Summary: Gathering local node statistics with cache and index
dimensions
Key: IGNITE-9777
URL: https://issues.apache.org/jira/browse/IGNITE-9777
Project:
Vladimir, Nikolay,
For sure, I'm not an experienced Ignite contributor, so I'm sorry for
intervening. I've just run the reproducer from [1] against ignite-2.6
branch and it has passed. So, it's not an legacy bug, we've brought it with
some change of 2.7 scope. Is it still ok to ignore the bug?
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4889
---
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 asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4832
---
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4904
IGNITE-9783: MVCC: Track all nodes participating in transaction
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4903
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4910
---
GitHub user luchnikovbsk opened a pull request:
https://github.com/apache/ignite/pull/4911
IGNITE-9719 Extra rebalanceThreadPoolSize check on client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/luchnikovbsk/ignite
Github user luchnikovbsk closed the pull request at:
https://github.com/apache/ignite/pull/4905
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4871
---
Nobody vetos anything, let's stop use this term unless some really
important problem is discussed.
At this point we are in situation when new tickets are still included into
the scope. All want to ask is to stop including new tickets without
explaining on why they should be in AI 2.7. Regression
Nobody vetos anything, let's stop use this term unless some really
important problem is discussed.
At this point we are in situation when new tickets are still included into
the scope. All I want to ask is to stop including new tickets without
explaining why they should be in AI 2.7. Regression
Ilya Kasnacheev created IGNITE-9779:
---
Summary: Support Java 9/10/11 in C++ tests
Key: IGNITE-9779
URL: https://issues.apache.org/jira/browse/IGNITE-9779
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4828
---
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/4901
IGNITE-9728: fix setup IGNITE_HOME for tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9728
It will be great if you can share your presentation/video after this summit
in dev-list.
Did you use a TensorFlow integration stand in your presentation?
Good news about potential users, it will be great to contact with somebody
who are going to use ML in production to discuss possible cases
ср,
I will try, Dmitriy, of course, to encourage contributors to other modules.
But from my side the main problem is not enough
screencasts/tutorials/examples to run something interesting about other
modules.
Great to see something tasty in examples folder in 2.7 release.
If you need my help with
ololo3000 opened a new 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 an automated message from the
Yury Gerzhedovich created IGNITE-9778:
-
Summary: Gathering local node statistics on query level
Key: IGNITE-9778
URL: https://issues.apache.org/jira/browse/IGNITE-9778
Project: Ignite
Nikolay,
this has nothing about scaring someone. Let me explain about Apache Way.
Voting -1 to release does not mean blocking it, release can't be vetoed.
Approving release is done by policy: majority approval. 3+1 binding and
more +1 than -1. Consensus approval is better but not mandatory.
The fix for MarshallerContext in IGNITE-7794 has resolved part of the
problem with unknown pair, however, we can still trigger a further unknown
pair issue with the following sequence:
1) Connect a client node to a server node
2) send a couple of service call so that there are some objects is
Vyacheslav,
Thanks for investigating this. User code should never listen to system
custom events because this is an internal API and it's a subject to change.
If there is anything a user interested in, the corresponding public event
should be added.
Nullifying the event in this case looks ok for
Denis, Alexey,
thank you for work you do to make Ignite more recognizable.
Don't forget to encourage contributors to come not only to ML but to core
and to other modules as well :)
Sincerely,
Dmitriy Pavlov
ср, 3 окт. 2018 г. в 6:29, Denis Magda :
> Alexey,
>
> Thanks for spreading the word
75 matches
Mail list logo
