Re: Right MXBean for new metrics

We have target redundancy level - 4. If, for some reason, minimal redundancy level reached the value of 1, then each next node left the cluster may cause data loss or service unavailability. 2017-11-24 1:31 GMT+03:00 Dmitriy Setrakyan : > Alex, > > I am really confused.

Re: Can not build from source code

Still got the same error when execute below command follow the instructions from https://github.com/kcmvp/ignite/blob/master/DEVNOTES.txt *mvn clean install -Pall-java,all-scala,licenses -DskipTests* [ERROR] Failed to execute goal on project ignite-core: Could not resolve dependencies for

Re: Context switching for pessimistic transactions

Hi, Igntrs! I have implemented context switching for pessimistic transactions. The main idea is to get rid of sending transaction thread id to other nodes. So when switching context you only need to change thread id locally. Please, review. [1] *https://issues.apache.org/jira/browse/IGNITE-5714

[GitHub] ignite pull request #3072: IGNITE-6963: Made PhysicalMemoryPages equal to To...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3072 ---

[jira] [Created] (IGNITE-6997) .NET: Thin client: Move ClientStatus to public API

Pavel Tupitsyn created IGNITE-6997: -- Summary: .NET: Thin client: Move ClientStatus to public API Key: IGNITE-6997 URL: https://issues.apache.org/jira/browse/IGNITE-6997 Project: Ignite

[GitHub] ignite pull request #3082: ignite-6977: fix initial size of BitSet

GitHub user abeliak opened a pull request: https://github.com/apache/ignite/pull/3082 ignite-6977: fix initial size of BitSet You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6977 Alternatively you

[jira] [Created] (IGNITE-7002) .NET: Add cross-platform examples on .NET Core

Pavel Tupitsyn created IGNITE-7002: -- Summary: .NET: Add cross-platform examples on .NET Core Key: IGNITE-7002 URL: https://issues.apache.org/jira/browse/IGNITE-7002 Project: Ignite Issue

[jira] [Created] (IGNITE-7004) Ability to disable WAL (Cross-cache tx should be rescricted while WAL disabled)

Anton Vinogradov created IGNITE-7004: Summary: Ability to disable WAL (Cross-cache tx should be rescricted while WAL disabled) Key: IGNITE-7004 URL: https://issues.apache.org/jira/browse/IGNITE-7004

[jira] [Created] (IGNITE-7005) Ability to disable WAL (Recoverable case)

Anton Vinogradov created IGNITE-7005: Summary: Ability to disable WAL (Recoverable case) Key: IGNITE-7005 URL: https://issues.apache.org/jira/browse/IGNITE-7005 Project: Ignite Issue

Can not build from source code

I forked the latest source code, and try to build the project. but I got below error : [ERROR] Failed to execute goal on project ignite-core: Could not resolve dependencies for project org.apache.ignite:ignite-core:jar:2.3.0-SNAPSHOT: The following artifacts could not be resolved:

Request for contributors permissions

Hello! I want to fix one of ignite issue, but have not access to take issue. Could you give me access or tell how to do it? My nick is heruv1m in jira and email is a.u.kazant...@gmail.com

[jira] [Created] (IGNITE-7001) Refactor dynamic indexes test to use SQL API

Alexander Paschenko created IGNITE-7001: --- Summary: Refactor dynamic indexes test to use SQL API Key: IGNITE-7001 URL: https://issues.apache.org/jira/browse/IGNITE-7001 Project: Ignite

[jira] [Created] (IGNITE-6998) Activation on bigger topology with enabled persistence doesn't work as expected.

Alexei Scherbakov created IGNITE-6998: - Summary: Activation on bigger topology with enabled persistence doesn't work as expected. Key: IGNITE-6998 URL: https://issues.apache.org/jira/browse/IGNITE-6998

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

Denis, I propose start with first three policies (it's already implemented, just await some code combing, commit & review). About of fourth policy (EXEC) I think that it's rather additional property (some script path) than policy. 2017-11-23 0:43 GMT+03:00 Denis Magda : > Just

[jira] [Created] (IGNITE-6999) Add a flag for Visor batch mode to output only command results without additional info.

Alexandr Fedotov created IGNITE-6999: Summary: Add a flag for Visor batch mode to output only command results without additional info. Key: IGNITE-6999 URL: https://issues.apache.org/jira/browse/IGNITE-6999

[jira] [Created] (IGNITE-7003) Ability to disable WAL (Non recoverable case)

Anton Vinogradov created IGNITE-7003: Summary: Ability to disable WAL (Non recoverable case) Key: IGNITE-7003 URL: https://issues.apache.org/jira/browse/IGNITE-7003 Project: Ignite Issue

[jira] [Created] (IGNITE-7000) .NET: Document .NET Core support and running on Linux

Pavel Tupitsyn created IGNITE-7000: -- Summary: .NET: Document .NET Core support and running on Linux Key: IGNITE-7000 URL: https://issues.apache.org/jira/browse/IGNITE-7000 Project: Ignite

[jira] [Created] (IGNITE-6996) Smarter handling of id fields in SQL values

Alexander Paschenko created IGNITE-6996: --- Summary: Smarter handling of id fields in SQL values Key: IGNITE-6996 URL: https://issues.apache.org/jira/browse/IGNITE-6996 Project: Ignite

Re: Transport compression (not store compression)

Denis, Regarding zipped marshaller - this would be inefficient, because compression rate will be lower. On Thu, Nov 23, 2017 at 1:01 AM, Denis Magda wrote: > Nikita, > > Your solution sounds reasonable from the first glance. However, the > communication layer processes a

Re: Losing data during restarting cluster with persistence enabled

As far as I remember, last webinar I heard on Ignite Native Persistence - it actually exposes some interfaces like IgniteWriteAheadLogManager, PageStore, PageStoreManager, etc., with the file-based implementation provided by Ignite being only one possible approach, and users can create their

Re: Transport compression (not store compression)

Hi Igniters! I’m working on the similar feature for my own project. I would like to suggest use in-line compression and write encoded bytes in network channel by bytes array buffer. It allows us avoiding expensive memory allocation. The described design may be implemented in TcpCommunicationSpi

Re: Request for contributors permissions

Hell Alexander, Welcome, added you to the JIRA contributors list. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

[GitHub] ignite pull request #3084: IGNITE-7007: Code cleanups.

GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/3084 IGNITE-7007: Code cleanups. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7007 Alternatively you can

Re: Ignite Enhancement Proposal #7 (Internal problems detection)

No objections here. Additional policies like EXEC might be added later depending on user needs. — Denis > On Nov 23, 2017, at 2:26 AM, Дмитрий Сорокин > wrote: > > Denis, > I propose start with first three policies (it's already implemented, just > await some code

Re: Can not build from source code

Please check up DEVNOTES for the most recent build instructions. The build procedure has been tweaked a bit in 2.3. Let us know if you still can’t overcome the problem. — Denis > On Nov 23, 2017, at 2:44 AM, kcmvp wrote: > > I forked the latest source code, and try to

Re: About readme.io's latest docs

Prachi, Would you mind assisting with this inquiry? — Denis > On Nov 23, 2017, at 5:56 AM, 李玉珏@163 <18624049...@163.com> wrote: > > Hi, > > > If some body in community can help to export all the latest version of > documents in the readme.io to me? > I am ready to make a synchronization of

Re: Transport compression (not store compression)

Nikita, Sounds like a good plan. Please share the design details prior getting down to the implementation. — Denis > On Nov 23, 2017, at 4:38 AM, Nikita Amelchev wrote: > > Hi Igniters! > > I’m working on the similar feature for my own project. > I would like to

[GitHub] ignite pull request #3085: ignite-6944 Fixed lookup of writeReplace and read...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3085 ignite-6944 Fixed lookup of writeReplace and readResolve methods during serialization/deserialization You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3086: IGNITE-6663: SQL: optimize primary key equality l...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3086 IGNITE-6663: SQL: optimize primary key equality lookup You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6663

[GitHub] ignite pull request #2544: Tx recovery fix

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

[GitHub] ignite pull request #1871: ignite-5041 NPE in deadlock detection fixed

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

[GitHub] ignite pull request #3087: IGNITE-7008: Fixed NPE in TcpDiscoverySharedFsIpF...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3087 IGNITE-7008: Fixed NPE in TcpDiscoverySharedFsIpFinder. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7008

[jira] [Created] (IGNITE-7008) TcpDiscoverySharedFsIpFinder fails with NPE if address can't be resolved.

Andrew Mashenkov created IGNITE-7008: Summary: TcpDiscoverySharedFsIpFinder fails with NPE if address can't be resolved. Key: IGNITE-7008 URL: https://issues.apache.org/jira/browse/IGNITE-7008

[GitHub] ignite pull request #3016: Ignite 602

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

[GitHub] ignite pull request #3081: Ignite-gg-13086

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

[GitHub] ignite pull request #2550: ignite-gg-12723 Optimistic tx recovery fixed

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

[GitHub] ignite pull request #2993: ignite-gg-12877 Compact consistent node IDs in WA...

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

Re: Losing data during restarting cluster with persistence enabled

Hi Evgeniy, Technically it is, of course, possible, but still - it is not simple at all - IgniteCacheOffheapManager & IgniteWriteAheadLogManager are internal APIs, and community can change any APIs here in any time. Vyacheslav, Why Ignite Native Persistence is not suitable for this case?

[jira] [Created] (IGNITE-7006) Javadoc warnings during building Windows binaries

Irina Zaporozhtseva created IGNITE-7006: --- Summary: Javadoc warnings during building Windows binaries Key: IGNITE-7006 URL: https://issues.apache.org/jira/browse/IGNITE-7006 Project: Ignite

[GitHub] ignite pull request #3061: IGNITE-2662 .NET Core support (run on Linux)

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

Fwd: Re: About readme.io's latest docs

Hi, If some body in community can help to export all the latest version of documents in the readme.io to me? I am ready to make a synchronization of the chinese version of the document. thanks! 转发的消息 主题: Re: About readme.io's latest docs 日期: Wed, 16 Aug 2017

Re: Use @ServiceResource with property placeholder

Hi Krzysztof! We don't have this capability right now. You can only specify name of a service in this annotation. You are able to use properties in XML config, because it is processed by Spring. But the code, that performs service injection, doesn't know anything about Spring. Ignite uses its own

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

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

[jira] [Created] (IGNITE-7007) Decision tree code cleanup

Artem Malykh created IGNITE-7007: Summary: Decision tree code cleanup Key: IGNITE-7007 URL: https://issues.apache.org/jira/browse/IGNITE-7007 Project: Ignite Issue Type: Task Affects

[GitHub] ignite pull request #3083: IGNITE-6890: + FailureProcessingPolicy; Unexpecte...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3083 IGNITE-6890: + FailureProcessingPolicy; Unexpected ExchangeWorker dea… …th processing. You can merge this pull request into a Git repository by running: $ git pull

Re: Right MXBean for new metrics

Example was in my previous letters: if we have in our cluster for cache group one partition with 2 copies (1 primary and 1 backup) and other partitions with 4 copies (1 primary and 3 backups), then minimal partition redundancy level for this cache group will be 2. Maybe code will be more clear

Re: Right MXBean for new metrics

Alex, I am really confused. What do you need to know the "minimal partition redundancy" for? What will it give you? D. On Thu, Nov 23, 2017 at 2:25 PM, Alex Plehanov wrote: > Example was in my previous letters: if we have in our cluster for cache > group one partition

[jira] [Created] (IGNITE-7009) NPE when Ignite persistence is enabled for Hadoop accelerator

Denis Magda created IGNITE-7009: --- Summary: NPE when Ignite persistence is enabled for Hadoop accelerator Key: IGNITE-7009 URL: https://issues.apache.org/jira/browse/IGNITE-7009 Project: Ignite

Re: Unable to start Hadoop Accelerator with Persistence

Alex, Totally agree with you that even if the use case is meaningless the platform has to show a meaningful exception. Don’t hesitate reporting usability issues like this immediately going forward: https://issues.apache.org/jira/browse/IGNITE-7009