[jira] [Created] (IGNITE-9072) Memory Configuration for client nodes

Roman Guseinov created IGNITE-9072: -- Summary: Memory Configuration for client nodes Key: IGNITE-9072 URL: https://issues.apache.org/jira/browse/IGNITE-9072 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-9071) Failed to reinitialize local partitions on client node

Roman Guseinov created IGNITE-9071: -- Summary: Failed to reinitialize local partitions on client node Key: IGNITE-9071 URL: https://issues.apache.org/jira/browse/IGNITE-9071 Project: Ignite I

Re: Thin Client lib: Python

Hello, Dmitriy, Igor! Dmitriy, as you have noted, most cache API functions are parameterized with the hash codes, and the function for creating the hash codes is documented. I personally see no harm in using hash codes as it is defined by low-level client operations. But it may be better to en

Re: Does Ignite Txs Protect against Phantom Reads?

Hi John, Looks like pictures can't be attached directly. Try uploading it somewhere and providing a link. However, since you're talking about ranges, my guess would be that you're using SQL which is currently NOT transactional. This support currently in development though, probably other members

Does Ignite Txs Protect against Phantom Reads?

Hi, Do Ignite transactions with serializable isolation level protect against phantom reads? For example, in the below example, does Ignite, in pessimistic mode, lock all entries in the range 10 to 30? Thanks.

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Great, thanks! I hope all TC failures would be fixed as fast as this one. вт, 24 июл. 2018 г. в 17:41, Alexey Goncharuk : > Thanks, merged to master. > > вт, 24 июл. 2018 г. в 16:28, Anton Vinogradov : > >> Seems, it works. >> Cancelled hanged suites, they hangs because of problems fixed at maste

Re: Service grid redesign

Igniters, please help me to clarify the following questions: 1). According to the issue [1] we should propagate services deployment results to an initiator, that means we should wait for wor Service#init method completion. How should we handle Service#init method hangup? I propose to introduce som

[jira] [Created] (IGNITE-9070) Web Console: 404 on notification from Admin panel

Alexey Kuznetsov created IGNITE-9070: Summary: Web Console: 404 on notification from Admin panel Key: IGNITE-9070 URL: https://issues.apache.org/jira/browse/IGNITE-9070 Project: Ignite Is

[GitHub] ignite pull request #4423: IGNITE-9069 Hadoop and IGFS TC configurations fai...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4423 IGNITE-9069 Hadoop and IGFS TC configurations fail with exit code = 130 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignit

[jira] [Created] (IGNITE-9069) Hadoop and IGFS TC configurations fail with exit code = 130

Eduard Shangareev created IGNITE-9069: - Summary: Hadoop and IGFS TC configurations fail with exit code = 130 Key: IGNITE-9069 URL: https://issues.apache.org/jira/browse/IGNITE-9069 Project: Ignite

[GitHub] ignite pull request #4417: IGNITE-9057 Update JCraft dependency version in A...

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

[jira] [Created] (IGNITE-9068) Node fails to stop when CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()

Ilya Kasnacheev created IGNITE-9068: --- Summary: Node fails to stop when CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard() Key: IGNITE-9068 URL: https://issues.apache.org/jira/browse/IGNITE

[GitHub] ignite pull request #4422: IGNITE-9046 Actualize dependency versions for Cas...

GitHub user zzzadruga opened a pull request: https://github.com/apache/ignite/pull/4422 IGNITE-9046 Actualize dependency versions for Cassandra Cache Store You can merge this pull request into a Git repository by running: $ git pull https://github.com/zzzadruga/ignite IGNITE-9

[GitHub] ignite pull request #4412: IGNITE-9055 Update Cache Based Dataset so that it...

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

[GitHub] ignite pull request #4264: IGNITE-8791 Fix WAL rebalancing from backup for T...

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

[GitHub] ignite pull request #4415: IGNITE-8892: Fix CacheQueryFuture usage.

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

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Thanks, merged to master. вт, 24 июл. 2018 г. в 16:28, Anton Vinogradov : > Seems, it works. > Cancelled hanged suites, they hangs because of problems fixed at master. > > вт, 24 июл. 2018 г. в 15:20, Anton Vinogradov : > > > Started more [1] Data Structures tasks to make sure fix works. > > > >

[GitHub] ignite pull request #4236: IGNITE-8188

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

[GitHub] ignite pull request #4421: IGNITE-9044 Update scala dependency version in Ap...

GitHub user zzzadruga opened a pull request: https://github.com/apache/ignite/pull/4421 IGNITE-9044 Update scala dependency version in Apache Ignite You can merge this pull request into a Git repository by running: $ git pull https://github.com/zzzadruga/ignite IGNITE-9044 Al

Re: Documenting Ignite

I've noticed now INFRA asks for feedback from us. Artem, will you provide feedback on done change in https://issues.apache.org/jira/browse/INFRA-16803 вт, 24 июл. 2018 г. в 11:01, Dmitry Pavlov : > Hi Artem, > > This is page in Ignite space, so you could do updates. Of course, if you > have acce

[jira] [Created] (IGNITE-9067) Clients to do a random delay when reconnecting to the cluster

Sergey Chugunov created IGNITE-9067: --- Summary: Clients to do a random delay when reconnecting to the cluster Key: IGNITE-9067 URL: https://issues.apache.org/jira/browse/IGNITE-9067 Project: Ignite

RE: ConcurrentLinkedHashMap works incorrectly after clear()

It seems that we currently use the CLHM primarily as a FIFO cache. I see two ways around that. First, we could implement such LRU/FIFO cache based on another, properly supported data structure from j.u.c. ConcurrentSkipListMap seems OK. I have a draft implementation of LruEvictionPolicy based on

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Seems, it works. Cancelled hanged suites, they hangs because of problems fixed at master. вт, 24 июл. 2018 г. в 15:20, Anton Vinogradov : > Started more [1] Data Structures tasks to make sure fix works. > > [1] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStruct

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Hello, Ilya. May be we need to proceed with ticket [1] "Get rid of org.jsr166.ConcurrentLinkedHashMap"? Especially, if this class is broken and buggy. [1] https://issues.apache.org/jira/browse/IGNITE-7516 В Вт, 24/07/2018 в 16:20 +0300, Ilya Lantukh пишет: > Thanks for revealing this issue! >

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Thanks for revealing this issue! I don't understand why should we disallow calling clear(). One way how it can be re-implemented is: 1. acquire write locks on all segments; 2. clear them; 3. reset size to 0; 4. release locks. Another approach is to calculate inside ConcurrentLinkedHashMap.Segmen

ConcurrentLinkedHashMap works incorrectly after clear()

Hello igniters! So I was working on a fix for https://issues.apache.org/jira/browse/IGNITE-9056 The reason for test flakiness turned out our ConcurrentLinkedHashMap (and its tautological cousin GridBoundedConcurrentLinkedHashMap) is broken :( When you do clear(). its size counter is not updated.

[jira] [Created] (IGNITE-9066) Web Console: Table rows highlight on mouse over is broken

Alexey Kuznetsov created IGNITE-9066: Summary: Web Console: Table rows highlight on mouse over is broken Key: IGNITE-9066 URL: https://issues.apache.org/jira/browse/IGNITE-9066 Project: Ignite

[GitHub] ignite pull request #4350: IGNITE-8981: Parallel optimizations for BaggingTr...

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

[GitHub] ignite pull request #4420: IGNITE-9056 Disallow calling clear() on Concurren...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4420 IGNITE-9056 Disallow calling clear() on ConcurrentLinkedHashMap. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9

Re: Thin Client lib: Python

Yes, looks strange? Why is the hash code part of API? On Tue, Jul 24, 2018, 13:38 Igor Sapego wrote: > Ok, I've quickly looked through API and I have a questions. Here > is the code from the example: > > cache_name = 'my cache' > hash_code = hashcode(cache_name) > cache_create(conn, cache_name)

Re: Thin Client lib: Python

Ok, I've quickly looked through API and I have a questions. Here is the code from the example: cache_name = 'my cache' hash_code = hashcode(cache_name) cache_create(conn, cache_name) result = cache_put(conn, hash_code, 'my key', 42) I'm not familiar with python, so here is the question. Why there

[jira] [Created] (IGNITE-9065) Gradient boosting optimization

Yury Babak created IGNITE-9065: -- Summary: Gradient boosting optimization Key: IGNITE-9065 URL: https://issues.apache.org/jira/browse/IGNITE-9065 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-9064) Decision tree optimization

Yury Babak created IGNITE-9064: -- Summary: Decision tree optimization Key: IGNITE-9064 URL: https://issues.apache.org/jira/browse/IGNITE-9064 Project: Ignite Issue Type: Improvement Com

[GitHub] ignite pull request #4307: IGNITE-8361 Use discovery messages for service de...

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

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Started more [1] Data Structures tasks to make sure fix works. [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures&branch_IgniteTests24Java8=pull%2F4415%2Fhead&tab=buildTypeStatusDiv вт, 24 июл. 2018 г. в 14:59, Alexey Goncharuk : > I will merge the fix o

[GitHub] ignite pull request #4419: IGNITE-9063 Correct DataFrame Partition Ordering

GitHub user stuartmacd opened a pull request: https://github.com/apache/ignite/pull/4419 IGNITE-9063 Correct DataFrame Partition Ordering You can merge this pull request into a Git repository by running: $ git pull https://github.com/stuartmacd/ignite fixSparkDfSequencing Alt

Re: Service grid redesign

Got it. Yes, we will preserve this behavior. Thanks! On Tue, Jul 24, 2018 at 2:20 PM Dmitriy Setrakyan wrote: > > By default the client nodes should be excluded form service deployment. The > only way to include clients is to explicitly specify them through node > filter. This is how services ar

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

I will merge the fix once the TC passes for the new PR. вт, 24 июл. 2018 г. в 13:13, Andrey Mashenkov : > Hi Dmitry, > > Looks like DataStructure sute timeouts is caused by IGNITE-8892 fix [1]. > The issue here is IgniteSetImpl uses internal CacheQueryFuture in wrong > way. > > I've already run P

Re: Service grid redesign

By default the client nodes should be excluded form service deployment. The only way to include clients is to explicitly specify them through node filter. This is how services are deployed today and we should preserve this behavior. D. On Tue, Jul 24, 2018 at 11:20 AM, Denis Mekhanikov wrote: >

[GitHub] ignite pull request #4418: IGNITE-9058 'Update Apache Tomcat dependency vers...

GitHub user 1vanan opened a pull request: https://github.com/apache/ignite/pull/4418 IGNITE-9058 'Update Apache Tomcat dependency version' You can merge this pull request into a Git repository by running: $ git pull https://github.com/1vanan/ignite IGNITE-9058 Alternatively y

Re: Service grid redesign

Maybe let's keep the functionality the way it is, since it doesn't interfere with the IEP? But I think, it's worth mentioning as a warning in log, that a service is deployed on a client node. Denis вт, 24 июл. 2018 г. в 12:44, Vyacheslav Daradur : > No, it's doesn't complicate implementation on

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Hi Dmitry, Looks like DataStructure sute timeouts is caused by IGNITE-8892 fix [1]. The issue here is IgniteSetImpl uses internal CacheQueryFuture in wrong way. I've already run PR branch with a fix on TC and it looks fine [2]. [1] issues.apache.org/jira/browse/IGNITE-8892 [2] https://ci.ignite.

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Hi, one of a possible cause: https://issues.apache.org/jira/browse/IGNITE-8892 Iterating over large dataset via ScanQuery can fails with OOME. Related PR tests: https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures&branch=%3Cdefault%3E&tab=buildTypeStatusDiv&bran

[GitHub] ignite pull request #4417: IGNITE-9057 Update JCraft dependency version in A...

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4417 IGNITE-9057 Update JCraft dependency version in Apache Ignite You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite ignite-9057 Alt

Re: Hello

Hi Nikolai, I've added you to the list of contributors, so you could assign issues to yourself. Looking forward to your contributions! Sincerely, Dmitriy Pavlov P.S. Additional references for you that should boost your onboarding. Please subscribe to both dev and user lists: https://ignite.apa

Re: Hello

Sure, I'd be happy to help. вт, 24 июл. 2018 г. в 12:47, Vyacheslav Daradur : > Welcome to the community, Nikolai! > > Dmitry, could you help with contributor permissions in Jira? > > On Tue, Jul 24, 2018 at 12:44 PM Nikolai Kulagin > wrote: > > > > I'm new to Ignite and I would like to join apa

Re: [MTCGA]: new failures in builds [1532044] needs to be handled

Hi Igniters, Test caused suite timeout 3 times in a row ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started) ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started) ⚠ IgniteDataStructureWithJobTest.testJobWithRestart (last started) History - https://ci.ignite.apache.org/vi

Re: Hello

Welcome to the community, Nikolai! Dmitry, could you help with contributor permissions in Jira? On Tue, Jul 24, 2018 at 12:44 PM Nikolai Kulagin wrote: > > I'm new to Ignite and I would like to join apache ignite development. > > My JIRA's login is zzzadruga. > > Going to start from IGNITE-9044

Re: Service grid redesign

No, it's doesn't complicate implementation on the current stage. But we will have to change assignment function to forbid client nodes even if configuration's node filter resolves them it can be not transparent for the end user. I think the only use case to have such behavior is: hosting of not c

Hello

I'm new to Ignite and I would like to join apache ignite development.  My JIRA's login is zzzadruga. Going to start from IGNITE-9044 and IGNITE-9046

[GitHub] ignite pull request #4416: IGNITE-8179 test unmuted to verify behavior on TC

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4416 IGNITE-8179 test unmuted to verify behavior on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-81

Re: Spark DataFrame Partition Ordering Issue

Thanks Nikolay, yes I’ll provide a fix. Stuart. > On 24 Jul 2018, at 10:18, Nikolay Izhikov wrote: > > Hello, Stuart. > > I'm able to reproduce your issue > > So I've created the ticket for it - > https://issues.apache.org/jira/browse/IGNITE-9063 > > Do you want to provide a fix? > > В Пт, 20/0

Re: Spark DataFrame Partition Ordering Issue

Hello, Stuart. I'm able to reproduce your issue So I've created the ticket for it - https://issues.apache.org/jira/browse/IGNITE-9063 Do you want to provide a fix? В Пт, 20/07/2018 в 19:37 +0300, Nikolay Izhikov пишет: > Hello, Stuart. > > I will investigate this issue and return to you in a

[jira] [Created] (IGNITE-9063) Wrong Data Frame parition order

Nikolay Izhikov created IGNITE-9063: --- Summary: Wrong Data Frame parition order Key: IGNITE-9063 URL: https://issues.apache.org/jira/browse/IGNITE-9063 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #4415: IGNITE-8892: Fix CacheQueryFuture usage.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4415 IGNITE-8892: Fix CacheQueryFuture usage. CacheQueryFuture does not collect results anymore. So, we have to iterate on future instead of using get(). You can merge this pull request into a Gi

Re: Service grid redesign

I don't think, that client nodes, that host services make much sense. May we forbid it? Does anybody know, when it may be useful? Vyacheslav, does it complicate the implementation somehow? Denis вт, 24 июл. 2018 г. в 11:57, Vyacheslav Daradur : > Hi, Igniters! > > I am close to completing the m

[jira] [Created] (IGNITE-9062) MVCC SQL: H2 connection and statement cache reafactoring

Ivan Pavlukhin created IGNITE-9062: -- Summary: MVCC SQL: H2 connection and statement cache reafactoring Key: IGNITE-9062 URL: https://issues.apache.org/jira/browse/IGNITE-9062 Project: Ignite

Re: Service grid redesign

Hi, Igniters! I am close to completing the main tasks and I'm going to request a review in a couple weeks. I have a question about the new design: The current implementation of Service Grid doesn't' take into account Ignition#client(true). It means that *clients* nodes are able to host services.

Re: Ignite guide for community developes

May be this discussion is answer: http://apache-ignite-developers.2346864.n4.nabble.com/Re-Documenting-Ignite-td32746.html -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Apache Ignite 2.7: scope, time and release manager

Hi, Igniters! The end of September for Ignite 2.7 release sounds good to me. I'm working on Service Grid and going to deliver the following tasks: - Use discovery messages for service deployment [[1] - Collect service deployment results asynchronously on coordinator [2] - Propagate service deploy

[jira] [Created] (IGNITE-9061) Add ability to specify a set of partitions for ScanQuery

Andrey Kalinin created IGNITE-9061: -- Summary: Add ability to specify a set of partitions for ScanQuery Key: IGNITE-9061 URL: https://issues.apache.org/jira/browse/IGNITE-9061 Project: Ignite

Re: Documenting Ignite

Hi Artem, This is page in Ignite space, so you could do updates. Of course, if you have access to Ignite space in wiki. If not, please sign up and share your wiki login (id). Sincerely, Dmitriy Pavlov вт, 24 июл. 2018 г. в 10:25, Artem Budnikov : > Hi everyone, > > Despite what I've been told a

[GitHub] ignite pull request #4414: IGNITE-8915: Check moved to GridQueryProcessor. C...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/4414 IGNITE-8915: Check moved to GridQueryProcessor. Check for SqlFieldsQuery added. You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/igni

Re: Documenting Ignite

Hi everyone, Despite what I've been told about INFRA, it responded exceptionally quickly and added the field :-) I think the page describing the process of creating IGNITE issues needs to be

Re: Ignite guide for community developes

Hi! How about continuation of this activity? We were planning to discuss this proposal, and make it possibly IEP. Can you help make this proposal active to make some decision ? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-9060) Web Console: Fix minor typos.

Alexey Kuznetsov created IGNITE-9060: Summary: Web Console: Fix minor typos. Key: IGNITE-9060 URL: https://issues.apache.org/jira/browse/IGNITE-9060 Project: Ignite Issue Type: Task