[GitHub] ignite pull request #3772: Ignite 1.9.12

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3772 Ignite 1.9.12 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.9.12 Alternatively you can review and apply

Re: Thin clients release cycle

Regardless of the path taken, the sources have to be located in ASF repositories since we agreed to contribute the clients to the Foundation. Presently, I'm leaning towards the monolithic approach (1) because that's just simpler for an ASF project. The hybrid way (3.) can work out only if ASF

Re: Thin clients release cycle

Vladimir, can you clarify your ideas from Apache projects standpoint? Do you propose (1) to create new apache projects for every client (or for all of them) Or (2) move thin clients OUT of Apache ecosystem and simply host them on Github? I think none of these will fly with ASF. I am strongly for

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Thanks, Ivan, It will be good if we fix usability issues like that as soon as possible because usually, they don't involve much effort. Igniters, is anyone interested to implement the improvement for 2.5 release? -- Denis On Fri, Apr 6, 2018 at 4:12 AM, Ivan Rakov

Re: IEP-18: Transparent Data Encryption

Nikolay, Dmitriy R., Thanks for the research and for writing down a summary in the IEP form. Please answer several high-level questions: - Is it necessary to have CEP keys for every cache? Not sure how all the keys will be managed if the user wants to encrypt 10-100 caches. Is it

Re: Memory usage per cache

Alex, Why not return cache group metrics from this method by default and properly > document it? What do you think about Dmitry's suggestion? It sounds reasonable to me. -- Denis On Wed, Apr 4, 2018 at 12:22 PM, Dmitriy Setrakyan wrote: > On Wed, Apr 4, 2018 at 5:27

Re: Service grid redesign

Yes, the class deployment itself has to be explicit. I.e., there has to be a manual step where user updates the class, and the exact step required would depend on DeploymentSpi implementation. But then Ignite takes care of everything else - service redeployment and restart is automatic. Dmitriy

[GitHub] ignite pull request #3774: Ignite 7791

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3774 Ignite 7791 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite ignite-7791 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #3773: IGNITE-8153 Nodes fail to connect each other when...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/3773 IGNITE-8153 Nodes fail to connect each other when SSL is enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8171) Document how to rollback transactions to let PME complete

Denis Magda created IGNITE-8171: --- Summary: Document how to rollback transactions to let PME complete Key: IGNITE-8171 URL: https://issues.apache.org/jira/browse/IGNITE-8171 Project: Ignite

Re: Thin clients release cycle

>From our point of view option (3) makes the most sense (if it works for the ASF, as Denis pointed out). Option (2) implies too much overhead, which may not be worth it. (1) is the least convenient approach for such independent projects as Client libs, however it's clear where it comes from. So it

Re: IGNITE-8167

Pavel, added you to JIRA contributors list. -- Denis On Fri, Apr 6, 2018 at 8:12 AM, Pavel Sapezhko wrote: > My JIRA ID: pavel.sapezhko > As I mentioned above, first we will have only archiver thread crashed and > absolute wal started from 0, but we will have alive

Re: Atomic caches

I would say absolutely YES - we need to have configuration validation. Igniters, why was the validation skipped in atomic caches? D. On Fri, Apr 6, 2018 at 1:43 PM, akurbanov wrote: > Hello Igniters, > > I want to address a question on AtomicConfiguration validation. I've

Re: Upsource update required

Dmitry, I confirm that a problem existed. Upsource can't handle situations of merging master to PR branch, in this case, Upsorce shows changes which are not related to a pull request. I know only one workaround solution: rebasing branch on master and never merge it, but in this case, we lost

Re: Upsource update required

Hi Igniters, Anton, According to my experience upsource works well, except 1 suspicious case with my PR. So I'm not sure if there are Upsource problems, probably there are problems with some of our PRs? My example is https://github.com/apache/ignite/pull/3243 PR and

[GitHub] ignite pull request #3770: IGNITE-8017 (2)

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3770 IGNITE-8017 (2) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8017-8122 Alternatively you can review and

[GitHub] ignite pull request #3767: IGNITE-8085

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/3767 IGNITE-8085 You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-8085 Alternatively you can review and apply these changes as

[GitHub] ignite pull request #3766: fix to avoid race between auto-activation and exp...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3766 ---

Re: Upsource update required

Defenetely, it may be reason of my PR / CR problem because I've merged master into my branch. Thank you. пт, 6 апр. 2018 г. в 15:14, Vyacheslav Daradur : > Dmitry, I confirm that a problem existed. > > Upsource can't handle situations of merging master to PR branch, in >

[GitHub] ignite pull request #3769: Ignite 8049

GitHub user SpiderRus opened a pull request: https://github.com/apache/ignite/pull/3769 Ignite 8049 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8049 Alternatively you can review and apply these

Re: Upsource update required

Anyway, We have to find the reason why merge from master breaks upsource review when PR is ok. 2018-04-06 15:28 GMT+03:00 Dmitry Pavlov : > Defenetely, it may be reason of my PR / CR problem because I've merged > master into my branch. Thank you. > > пт, 6 апр. 2018 г. в

Re: IGNITE-6879

Hi all! As i see everything is awesome and there is no objections, so when my PR would be merged? чт, 5 апр. 2018 г. в 18:58, Вячеслав Коптилин : > Thank you, Roman! > > 2018-04-05 17:49 GMT+03:00 Роман Меерсон : > > > Hi Slava, > > > > Fixed > >

Thin clients release cycle

Igniters, Over the last year we saw dramatic increase in demand for lightweight thin clients. We already have four: JDBC, ODBC, .NET, Java. In future we are going to have even more: NodeJS, PHP, Python, Go, whatever. I'd like to start a discussion on how are we going to host them. There are

Re: IGNITE-6879

OK [image: 1486924635147168240.jpg] пт, 6 апр. 2018 г. в 17:08, Igor Sapego : > Hi, > Well, Dmitry has said he's going to merge it in 3-4 days 2 days ago, > so I guess, the merge is going to happen in 1-2 days or so. > > > Best Regards, > Igor > > On Fri, Apr 6, 2018 at

[GitHub] ignite pull request #3768: IGNITE-8111 Add extra validation for WAL segment ...

GitHub user dgarus opened a pull request: https://github.com/apache/ignite/pull/3768 IGNITE-8111 Add extra validation for WAL segment size You can merge this pull request into a Git repository by running: $ git pull https://github.com/dgarus/ignite ignite-8111 Alternatively

Re: Breaking change in JDBC connection string format

ODBC uses semicolon and this semantics are defined by ODBC specification. Best Regards, Igor On Thu, Apr 5, 2018 at 10:35 PM, Denis Magda wrote: > Vladimir, Igor, > > Shouldn't we do the same for ODBC? > > -- > Denis > > On Thu, Apr 5, 2018 at 5:53 AM, Vladimir Ozerov

Re: IGNITE-6879

Hi, Well, Dmitry has said he's going to merge it in 3-4 days 2 days ago, so I guess, the merge is going to happen in 1-2 days or so. Best Regards, Igor On Fri, Apr 6, 2018 at 3:48 PM, Роман Меерсон wrote: > Hi all! > > As i see everything is awesome and there is no

[jira] [Created] (IGNITE-8158) Missed cleanups if afterTestsStop throws exception

Maxim Muzafarov created IGNITE-8158: --- Summary: Missed cleanups if afterTestsStop throws exception Key: IGNITE-8158 URL: https://issues.apache.org/jira/browse/IGNITE-8158 Project: Ignite

[jira] [Created] (IGNITE-8160) GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization flaky-fails on TC

Alexey Goncharuk created IGNITE-8160: Summary: GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization flaky-fails on TC Key: IGNITE-8160 URL:

[jira] [Created] (IGNITE-8159) control.sh Failed with NPE in case of adding not online node in base line

Alexey Kuznetsov created IGNITE-8159: Summary: control.sh Failed with NPE in case of adding not online node in base line Key: IGNITE-8159 URL: https://issues.apache.org/jira/browse/IGNITE-8159

[GitHub] ignite pull request #3686: IGNITE-8018 : Optimized initialValue(...)

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3686 ---

[jira] [Created] (IGNITE-8162) Handle ClassNotFoundException during deserialization of persisted cache configuration

Ivan Rakov created IGNITE-8162: -- Summary: Handle ClassNotFoundException during deserialization of persisted cache configuration Key: IGNITE-8162 URL: https://issues.apache.org/jira/browse/IGNITE-8162

[GitHub] ignite pull request #3765: Ignite 8049

GitHub user SpiderRus opened a pull request: https://github.com/apache/ignite/pull/3765 Ignite 8049 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8049 Alternatively you can review and apply these

[jira] [Created] (IGNITE-8164) SQL TX: JDBC driver meta data update.

Roman Kondakov created IGNITE-8164: -- Summary: SQL TX: JDBC driver meta data update. Key: IGNITE-8164 URL: https://issues.apache.org/jira/browse/IGNITE-8164 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-8161) Suspend-resume TX test is flaky on TC (~5% fail rate)

Dmitriy Pavlov created IGNITE-8161: -- Summary: Suspend-resume TX test is flaky on TC (~5% fail rate) Key: IGNITE-8161 URL: https://issues.apache.org/jira/browse/IGNITE-8161 Project: Ignite

[GitHub] ignite pull request #3764: GG-13379 Extended security for Huawei

GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/3764 GG-13379 Extended security for Huawei You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-13379 Alternatively

Re: Ability to check and completely fill transactions on creation

>> But I have concern >> about performance. How can you estimate impact to performance ? We have to benchmark result. >> How about to set label name with some useful info if user does not provide >> custom name? You can set custom listener which will do that >> For example thread name + global

[jira] [Created] (IGNITE-8163) PDS Indexing suite is hanging on TC in different branches including master

Sergey Chugunov created IGNITE-8163: --- Summary: PDS Indexing suite is hanging on TC in different branches including master Key: IGNITE-8163 URL: https://issues.apache.org/jira/browse/IGNITE-8163

[GitHub] ignite pull request #3766: fix to avoid race between auto-activation and exp...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3766 fix to avoid race between auto-activation and explicit activation You can merge this pull request into a Git repository by running: $ git pull

Re: Apache Ignite 2.5 release

Added corresponding triggers for ignite-2.5 in Ignite Tests 2.4+ project in TC. > On 5 Apr 2018, at 21:55, Denis Magda wrote: > > Thanks Andrey! > > Folks, if you'd like to add anything to 2.5 please make sure it gets merged > into 2.5 branch. > > -- > Denis > > On Thu,

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Denis, I'm sure we can: https://issues.apache.org/jira/browse/IGNITE-8162 Best Regards, Ivan Rakov On 05.04.2018 22:39, Denis Magda wrote: Ivan, How can we facilitate the user here? Can we generate a meaningful exception that explains how to tackle the issue? -- Denis On Thu, Apr 5, 2018

Upsource update required

Igniters. Who is responsible for Upsource [1]? I see some strange things at reviews, a lot of fake changes inside reviews. I don't see such changes at PRs. Could you please check we're using stable version and update if necessary? [1] https://reviews.ignite.apache.org

[GitHub] ignite pull request #3765: Ignite 8049

Github user SpiderRus closed the pull request at: https://github.com/apache/ignite/pull/3765 ---

[jira] [Created] (IGNITE-8156) Ignite Compatibility: common improvements

Vyacheslav Daradur created IGNITE-8156: -- Summary: Ignite Compatibility: common improvements Key: IGNITE-8156 URL: https://issues.apache.org/jira/browse/IGNITE-8156 Project: Ignite Issue

[jira] [Created] (IGNITE-8157) Remove boilerplate and unused code due to grids stopping by default

Maxim Muzafarov created IGNITE-8157: --- Summary: Remove boilerplate and unused code due to grids stopping by default Key: IGNITE-8157 URL: https://issues.apache.org/jira/browse/IGNITE-8157 Project:

[GitHub] ignite pull request #3633: IGNITE-7933 Checkpoint markers writing issues

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3633 ---

[jira] [Created] (IGNITE-8168) [ML] Add KMeans version for Partitioned Datasets

Aleksey Zinoviev created IGNITE-8168: Summary: [ML] Add KMeans version for Partitioned Datasets Key: IGNITE-8168 URL: https://issues.apache.org/jira/browse/IGNITE-8168 Project: Ignite

Re: Service grid redesign

Val, I don't really like the idea of automatic redeployment of services when classes change. Different nodes may detect these changes at different moments in time, so there won't be any guarantee, that all nodes have the same version. And if redeployment fails, then there won't be a way to notify

[GitHub] ignite pull request #3769: Ignite 8049

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3769 ---

[jira] [Created] (IGNITE-8167) Recovery after crash sometimes leads to starting from beginning absolute wal segment index

Pavel Sapezhko created IGNITE-8167: -- Summary: Recovery after crash sometimes leads to starting from beginning absolute wal segment index Key: IGNITE-8167 URL: https://issues.apache.org/jira/browse/IGNITE-8167

Re: IGNITE-8167

My JIRA ID: pavel.sapezhko As I mentioned above, first we will have only archiver thread crashed and absolute wal started from 0, but we will have alive ignite instance. Logs can be found in attach. On Fri, Apr 6, 2018 at 5:42 PM Dmitry Pavlov wrote: > Hi Pavel, > > Thank

[jira] [Created] (IGNITE-8170) [ML] Adopt KMeans example to the Partitioned Dataset

Aleksey Zinoviev created IGNITE-8170: Summary: [ML] Adopt KMeans example to the Partitioned Dataset Key: IGNITE-8170 URL: https://issues.apache.org/jira/browse/IGNITE-8170 Project: Ignite

[jira] [Created] (IGNITE-8169) [ML] Implement Model-Trainer pair for KMeans based on Partitioned Dataset

Aleksey Zinoviev created IGNITE-8169: Summary: [ML] Implement Model-Trainer pair for KMeans based on Partitioned Dataset Key: IGNITE-8169 URL: https://issues.apache.org/jira/browse/IGNITE-8169

[GitHub] ignite pull request #3740: ignite-8049 Limit the number of operation cycles ...

Github user SpiderRus closed the pull request at: https://github.com/apache/ignite/pull/3740 ---

[jira] [Created] (IGNITE-8166) stopGrid() hangs in some cases when node is invalidated and PDS is enabled

Aleksey Plekhanov created IGNITE-8166: - Summary: stopGrid() hangs in some cases when node is invalidated and PDS is enabled Key: IGNITE-8166 URL: https://issues.apache.org/jira/browse/IGNITE-8166

[jira] [Created] (IGNITE-8165) Spark Dataset Write intermittent "Failed to map key to node" error

mark pettovello created IGNITE-8165: --- Summary: Spark Dataset Write intermittent "Failed to map key to node" error Key: IGNITE-8165 URL: https://issues.apache.org/jira/browse/IGNITE-8165 Project:

IGNITE-8167

Working on it. -- С уважением, Cапежко Павел Александрович Инженер-программист ООО "Synesis" Skype: p.sapezhko

[GitHub] ignite pull request #3771: IGNITE-8167: Fix inconsistent last record pointer...

GitHub user amelius0712 opened a pull request: https://github.com/apache/ignite/pull/3771 IGNITE-8167: Fix inconsistent last record pointer in case of recovery from corrupted WAL Let's look at this peace of code from GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory

Re: Thin clients release cycle

I would vote for single repository and the following release scheme: we build and release everything, but deliver only that modules, which have actual features / bugfixes, skipping other from release iteration until new changes come into them. Also, I’d propose versioning scheme, that will

Re: IGNITE-6879

Excellend picture. I remember about this change. If Denis M. would be able to look througt the changes faster than me, I can merge without detailed review. пт, 6 апр. 2018 г. в 16:15, Роман Меерсон : > OK > > [image: 1486924635147168240.jpg] > > > пт, 6 апр. 2018 г. в

Re: IGNITE-8167

Hi Pavel, Thank you. Could you please attach logs/stacktraces. Now it is not quite clear where Ignite has failed? Could you please share your JIRA ID? Hi PMCs, could you please add Pavel to contributor list so https://issues.apache.org/jira/browse/IGNITE-8167 issue can be assigned? Sincerely,

[GitHub] ignite pull request #3700: IGNITE-6839 Ignite Compatibility: flaky test test...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3700 ---

Re: Service grid redesign

Hi Igniters, I like automatic redeploy which can be disabled by config if user wants to control this process. What do you think? Sincerely, Dmitriy Pavlov пт, 6 апр. 2018 г. в 18:29, Denis Mekhanikov : > Val, > > I don't really like the idea of automatic redeployment of

[GitHub] ignite pull request #3734: IGNITE-8114 Add fail recovery mechanism to tracki...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3734 ---

Re: Service grid redesign

On Fri, Apr 6, 2018 at 9:13 AM, Dmitry Pavlov wrote: > Hi Igniters, > > I like automatic redeploy which can be disabled by config if user wants to > control this process. What do you think? > I do not think we should have anything automatic when it comes to deployment,