[jira] [Created] (IGNITE-6912) .NET: Thin client: Cache iterator

Pavel Tupitsyn created IGNITE-6912: -- Summary: .NET: Thin client: Cache iterator Key: IGNITE-6912 URL: https://issues.apache.org/jira/browse/IGNITE-6912 Project: Ignite Issue Type:

Re: request for contributors permissions

Hello Sergey and welcome aboard! Granted the required permission in JIRA. Feel free to pick a ticket you like. Some extra info that might be useful to you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Request for Contributers permission

Ignite Community, Would you please provide me with contributor permissions? JIRA account: netmille Best, Turik -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: GA Grid: Request to contribute GA library to Apache Ignite

Denis/Yury, Thank you both for your valuable feedback. I will begin reviewing software grant form and submit accordingly. Also, I have created account in JIRA and submitted request for contributor permission to dev list. In addition, I will follow steps related to creating a 'pull

[jira] [Created] (IGNITE-6911) .NET: Optionally disable Java console redirect

Pavel Tupitsyn created IGNITE-6911: -- Summary: .NET: Optionally disable Java console redirect Key: IGNITE-6911 URL: https://issues.apache.org/jira/browse/IGNITE-6911 Project: Ignite Issue

Re: Ignite Enhancement Proposal #6 (Metrics)

Anton, I do not see a section for the proposed memory metrics and this ticket [1] among the tasks. Did you forget to consider them? [1] https://issues.apache.org/jira/browse/IGNITE-5796 — Denis > On Nov 14, 2017, at 3:44 AM, Anton

Re: request for contributors permissions

Hello Denis, Done, now you can assign yourself for a ticket of an interest. Some extra info that might be useful for you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be

Losing data during restarting cluster with persistence enabled

Hi, Igniters! I’m using partitioned Ignite cache with RocksDB as 3rd party persistence store. I've got an issue: if cache rebalancing is switched on, then it’s possible to lose some data. Basic scenario: 1) Start Ignite cluster and fill a cache with RocksDB persistence; 2) Stop all nodes 3)

[jira] [Created] (IGNITE-6913) Add support for baseline manipulations to controls.sh

Alexey Kuznetsov created IGNITE-6913: Summary: Add support for baseline manipulations to controls.sh Key: IGNITE-6913 URL: https://issues.apache.org/jira/browse/IGNITE-6913 Project: Ignite

[jira] [Created] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox

Pavel Konstantinov created IGNITE-6914: -- Summary: Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox Key: IGNITE-6914 URL:

[jira] [Created] (IGNITE-6915) SQL: Failed to invoke getter method (type=class java.lang.String)

Pavel Konstantinov created IGNITE-6915: -- Summary: SQL: Failed to invoke getter method (type=class java.lang.String) Key: IGNITE-6915 URL: https://issues.apache.org/jira/browse/IGNITE-6915

Re: Add emergency node closing handler to public Ignite API

This information should be available through local metrics, so that it is accessible from Ignite instance. вт, 14 нояб. 2017 г. в 22:37, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Andrey, > > Then let's add API to get this information. There is no need to add another > callback as

collocated compute and off-heap cache

Igniters, I am noticing that some users struggle with performance when using collocated compute and off-heap cache. The main reason is that collocated computations access data locally, directly on the server, and with off-heap cache all binary objects need to be deserialized for every access. A

[GitHub] ignite pull request #2972: Ignite 8266 test failing GridTcpCommunicationSpiC...

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

[GitHub] ignite pull request #2904: IGNITE-6071 White list of exceptions to suppress ...

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

[GitHub] ignite pull request #3027: IGNITE-6901

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

[GitHub] ignite pull request #3031: IGNITE-6896 .NET: support Multidimensional Arrays...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3031 IGNITE-6896 .NET: support Multidimensional Arrays in binary serializer You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3028: Support enforceJoinOrder flag for Thick JDBC Driv...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3028 Support enforceJoinOrder flag for Thick JDBC Driver for 1.8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: GA Grid: Request to contribute GA library to Apache Ignite

Also please check the coding guideline - https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines Code in PR should fits to this guideline. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #2906: IGNITE-6071 White list of exceptions to suppress ...

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

[GitHub] ignite pull request #2905: IGNITE-6071 White list of exceptions to suppress ...

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

[GitHub] ignite pull request #2903: IGNITE-6071 White list of exceptions to suppress ...

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

[GitHub] ignite pull request #2997: IGNITE-6835 ODBC driver should handle ungraceful ...

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

[GitHub] ignite pull request #3030: IGNITE-5846: Add support of distributed matrices ...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3030 IGNITE-5846: Add support of distributed matrices for OLS regression You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2841: GG-12821 IGNITE-4642: Added "enforceJoinOrder" fl...

GitHub user alamar reopened a pull request: https://github.com/apache/ignite/pull/2841 GG-12821 IGNITE-4642: Added "enforceJoinOrder" flag to thick JDBC driver. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2841: GG-12821 IGNITE-4642: Added "enforceJoinOrder" fl...

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

[GitHub] ignite pull request #2610: Fix Licenses & Javadoc tests.

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

[GitHub] ignite pull request #2841: GG-12821 IGNITE-4642: Added "enforceJoinOrder" fl...

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

[GitHub] ignite pull request #3029: enforceJoinOrder flag for Thick JDBC Driver to 1....

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3029 enforceJoinOrder flag for Thick JDBC Driver to 1.9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13053

[jira] [Created] (IGNITE-6898) Datastreamers can lead to OOM on server side

Alexander Belyak created IGNITE-6898: Summary: Datastreamers can lead to OOM on server side Key: IGNITE-6898 URL: https://issues.apache.org/jira/browse/IGNITE-6898 Project: Ignite Issue

[jira] [Created] (IGNITE-6900) .NET: QuerySqlEntity attribute

Pavel Tupitsyn created IGNITE-6900: -- Summary: .NET: QuerySqlEntity attribute Key: IGNITE-6900 URL: https://issues.apache.org/jira/browse/IGNITE-6900 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6901) IgniteH2Indexing#rebuildIndexesFromHash should pass old value to indexing engine

Vladimir Ozerov created IGNITE-6901: --- Summary: IgniteH2Indexing#rebuildIndexesFromHash should pass old value to indexing engine Key: IGNITE-6901 URL: https://issues.apache.org/jira/browse/IGNITE-6901

[jira] [Created] (IGNITE-6903) Implement new JMX metrics for Indexing

Anton Vinogradov created IGNITE-6903: Summary: Implement new JMX metrics for Indexing Key: IGNITE-6903 URL: https://issues.apache.org/jira/browse/IGNITE-6903 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.

Yury Babak created IGNITE-6899: -- Summary: Adding GA Grid to Apache Ignite ML module. Key: IGNITE-6899 URL: https://issues.apache.org/jira/browse/IGNITE-6899 Project: Ignite Issue Type: New

[GitHub] ignite pull request #3027: IGNITE-6901

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

Re: GA Grid: Request to contribute GA library to Apache Ignite

Turik, For making pull-request you should perform the following steps: 1) create JIRA account(in case you dont have one) (https://issues.apache.org/jira) 1.1) write to dev-list and ask contributors permission. 2) assign the ticket which I`ve created for you

Re: Problem in Ignite Server When using it with hiredis to Store and retrieve C++ Class Object

Hello, Please, add checks for success of the operations so we can understand what is the problem. Please, check result of serealization, deserialisation, and command sending. Please, also note that this check is not going to work as intended, because size_t is unsigned type:

[GitHub] ignite pull request #2989: IGNITE-5846: Add support of distributed matrices ...

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

[jira] [Created] (IGNITE-6902) Implement new JMX metrics for Persistence

Anton Vinogradov created IGNITE-6902: Summary: Implement new JMX metrics for Persistence Key: IGNITE-6902 URL: https://issues.apache.org/jira/browse/IGNITE-6902 Project: Ignite Issue

[GitHub] ignite pull request #3026: 5195 DataStreamer can fails if non-data node ente...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/3026 5195 DataStreamer can fails if non-data node enter\leave the grid. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Ignite Enhancement Proposal #6 (Metrics)

Val, Denis, I've updated issues list, thanks for tips. On Tue, Nov 14, 2017 at 3:57 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Here is the link: > > [1] https://issues.apache.org/jira/browse/IGNITE-6846 > > -Val > > On Mon, Nov 13, 2017 at 4:53 PM, Valentin Kulichenko < >

[GitHub] ignite pull request #2985: IGNITE-5343 .NET: Work with JNI directly, get rid...

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

[GitHub] ignite pull request #3033: IGNITE-6527: Solution 2.

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/3033 IGNITE-6527: Solution 2. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-6527_secondSolution Alternatively you

[GitHub] ignite pull request #3032: IGNITE-6445: Solution 1.

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/3032 IGNITE-6445: Solution 1. You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-6527_firstSolution Alternatively you can

[jira] [Created] (IGNITE-6908) Check PartitionLossPolicy during a cluster activation

Sergey Puchnin created IGNITE-6908: -- Summary: Check PartitionLossPolicy during a cluster activation Key: IGNITE-6908 URL: https://issues.apache.org/jira/browse/IGNITE-6908 Project: Ignite

[jira] [Created] (IGNITE-6909) Create an unconditional branching pointing after a snapshot restore

Sergey Puchnin created IGNITE-6909: -- Summary: Create an unconditional branching pointing after a snapshot restore Key: IGNITE-6909 URL: https://issues.apache.org/jira/browse/IGNITE-6909 Project:

Add emergency node closing handler to public Ignite API

Hi Igniters! When some node detects critical error, e.g. OOME, deadlock, etc, it should invoke some user-defined callback and then attempt to close itself gracefully. In order to make this possible we need to enhance Ignite interface by adding something like Ignite.onEmergencyClose(SomeClosure).

Re: Add emergency node closing handler to public Ignite API

I am not sure this makes sense. First, in general case we do not have access to Java. E.g. in case of very long GC pause all Java threads are stuck and it is impossible to invoke anything. Second, some other conditions may be unrecoverable, such as OOME, where there is no guarantee that any

Re: Add emergency node closing handler to public Ignite API

Vova, That's not about "kill -9" or OOM, that's about case when node detected something and decided to stop itself (eg. persistence errors, IgniteOutOfMemoryException, ExchangeWorker died) Sure, we can't handle OOM or 100% CPU utilization by GC it that way, but we can handle some logical

[jira] [Created] (IGNITE-6904) SQL: Partition reservations are released too early in lazy mode

Vladimir Ozerov created IGNITE-6904: --- Summary: SQL: Partition reservations are released too early in lazy mode Key: IGNITE-6904 URL: https://issues.apache.org/jira/browse/IGNITE-6904 Project:

Re: SSL for ODBC connection

I think it would be enough to have a single switch for now. On Tue, Nov 7, 2017 at 10:04 PM, Denis Magda wrote: > Igor, > > Thanks for the clarification. Please file a ticket if nobody else shares a > feedback soon. > > — > Denis > > > On Nov 7, 2017, at 1:23 AM, Igor Sapego

[jira] [Created] (IGNITE-6905) Print a consistent ID into a log file

Sergey Puchnin created IGNITE-6905: -- Summary: Print a consistent ID into a log file Key: IGNITE-6905 URL: https://issues.apache.org/jira/browse/IGNITE-6905 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-6910) Introduce a force join parameter to clear PDS after branching pointing

Sergey Puchnin created IGNITE-6910: -- Summary: Introduce a force join parameter to clear PDS after branching pointing Key: IGNITE-6910 URL: https://issues.apache.org/jira/browse/IGNITE-6910 Project:

[jira] [Created] (IGNITE-6906) Inform user about missed nodes from BLT during a cluster activation

Sergey Puchnin created IGNITE-6906: -- Summary: Inform user about missed nodes from BLT during a cluster activation Key: IGNITE-6906 URL: https://issues.apache.org/jira/browse/IGNITE-6906 Project:

[jira] [Created] (IGNITE-6907) Add LINQ many-to-many test and LINQ with transactions test

Alexey Popov created IGNITE-6907: Summary: Add LINQ many-to-many test and LINQ with transactions test Key: IGNITE-6907 URL: https://issues.apache.org/jira/browse/IGNITE-6907 Project: Ignite

Re: Add emergency node closing handler to public Ignite API

You can get this info from injected Ignite instance. On Tue, Nov 14, 2017 at 10:13 PM, Andrey Kuznetsov wrote: > Lifecycle beans are ok, but they does not accept any info on the Reason in > case of emergency node stop. > > 2017-11-14 21:16 GMT+03:00 Valentin Kulichenko < >

Re: Add emergency node closing handler to public Ignite API

Vladimir, Ignite instance won't tell me whether deadlock occurred or some critical thread has died. 14 нояб. 2017 г. 22:28 пользователь "Vladimir Ozerov" написал: You can get this info from injected Ignite instance.

Re: Add emergency node closing handler to public Ignite API

Andrey, Then let's add API to get this information. There is no need to add another callback as we already have one. -Val On Tue, Nov 14, 2017 at 11:34 AM, Andrey Kuznetsov wrote: > Vladimir, Ignite instance won't tell me whether deadlock occurred or some > critical thread

Re: Add emergency node closing handler to public Ignite API

Can you explain what kind of logic could be placed there? And why do we need another configuration property and/or interface? We already have LifecycleBean, where Ignite instance could be injected, so user is already able to perform anything there. On Tue, Nov 14, 2017 at 7:46 PM, Anton

Re: GA Grid: Request to contribute GA library to Apache Ignite

Turik, Basically, this all is being done in parallel: - submit the software grant form. - prepare and submit the pull-request for code review. - I’ll start filling in the IP clearance form after the steps above are completed. A PMC member has to do it. - once the pull-request is reviewed and

Re: Ignite Enhancement Proposal #6 (Metrics)

Anton, for the IEP to be complete, you should add a list of Jira tickets to the IEP page. Otherwise, it is unclear how to get started on it. Thanks, D. On Tue, Nov 14, 2017 at 3:44 AM, Anton Vinogradov wrote: > Val, Denis, > > I've updated issues list, thanks for

request for contributors permissions

Hello! I want to resolve bugs using my account: da.loginov Please, provide me with necessary permissions. Thanks in advance. Best regards, Denis

request for contributors permissions

Hello. I want to resolve bugs. My account in jira: Username: sergvolkov Email: sergeyvol...@inbox.ru Full Name: Sergey Volkov

Re: Add emergency node closing handler to public Ignite API

Vova, We should provide user ability to be notified in case some node decided to stop itself. Only user know how he want to be notified, so we should provide ability to register custom callback(eg. send sms or call rest service) This will cover cases when node stops gracefuly. Please, see

Re: Ignite Enhancement Proposal #6 (Metrics)

Dmitriy, It looks like a confluence bug. Please login and push refresh button at issues list. Вт, 14 нояб. 2017 г. в 20:51, Dmitriy Setrakyan : > Anton, for the IEP to be complete, you should add a list of Jira tickets to > the IEP page. Otherwise, it is unclear how to

Re: Ignite Enhancement Proposal #6 (Metrics)

On Tue, Nov 14, 2017 at 10:12 AM, Anton Vinogradov wrote: > Dmitriy, > > It looks like a confluence bug. > Please login and push refresh button at issues list. > Works now. It is unfortunate that it does not work for the community members who do not login. Perhaps we

[GitHub] ignite pull request #3035: IGNITE-6867 Implement new JMX metrics for topolog...

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/3035 IGNITE-6867 Implement new JMX metrics for topology monitoring. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-6867

Re: Add emergency node closing handler to public Ignite API

Anton, I agree with Vova - we already have lifecycle bean. Why do we need anything on top of that? -Val On Tue, Nov 14, 2017 at 10:05 AM, Anton Vinogradov wrote: > Vova, > > We should provide user ability to be notified in case some node decided to > stop itself. >

[GitHub] ignite pull request #3007: CI TESTS for Ignite 6844

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

Re: Add emergency node closing handler to public Ignite API

Lifecycle beans are ok, but they does not accept any info on the Reason in case of emergency node stop. 2017-11-14 21:16 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Anton, > > I agree with Vova - we already have lifecycle bean. Why do we need anything > on top of that? > >