Re: Hello! IGNITE-5823

Hi Sergey, This ticket is unassigned. Feel free to assign it to yourself. Sincerely, Dmitry Pavlov пт, 28 июл. 2017 г. в 18:18, Серега Дорожкин <stalk007s...@gmail.com>: > Thank you! > > Can I pick this ticket (IGNITE-5823)? > > 2017-07-28 18:13 GMT+03:00 Alexey Gon

Re: [IGNITE-5717] improvements of MemoryPolicy default size

+1 to Sergey, I think OOME may confuse user and and may spoil the user's impression at first check of Apache Ignite. вт, 1 авг. 2017 г. в 12:36, Vladimir Ozerov : > +1 > > 80% of RAM is way too aggressive. With this value virtually every user will > have problems with OOME

Ignite.close(), G.stop(name, true). Change flag cancel to false

Hi Igniters, I’ve created the simplest example using Ignite 2.1 and persistence (see the code below). I've included Ignite instance into try-with-resources (I think it is default approach for AutoCloseable inheritors). But next time when I started this server I got message: “Ignite node crashed

Re: Ignite.close(), G.stop(name, true). Change flag cancel to false

will restore memory state if stopped at any > > moment. > > On the other hand, checkpoint may last for a long time. Thread hanging on > > Ignite.close() may confuse user much more than "crashed in the middle of > > checkpoint" message. > > > > Best Reg

Re: Cluster auto activation design proposal

Igniters, what about Target Node Set? Complete Node Set? As when we reach this topology, we can activate cluster. чт, 3 авг. 2017 г. в 12:58, Sergey Chugunov : > Dmitriy, > > Obvious connotation of "minimal set" is a set that cannot be decreased. > > But lets consider

Re: Ignite Teamcity email notifications

enis Magda <dma...@apache.org> wrote: > >> > >>> What’s about c...@ignite.apache.org <mailto:c...@ignite.apache.org>? If > there > >>> are no objections I’ll create the alias. > >>> > >>> — > >>> Denis > >>>

Re: IGNITE-5123 Review

component callbacks, was introduced by this commit - > > https://github.com/apache/ignite/commit/6b7bf97158c097b80bcf5c2150e67a5210269e6d > - but I have no clue what was the reason. > > > On 7/20/2017 7:51 PM, Dmitry Pavlov wrote: > > Hi Nick, > > > > Thank you for

Re: IGNITE-5123 Review

ev wrote: > > Scheduled "Run All" in Ignite 2.0 Tests for pull/2285/head - > > http://ci.ignite.apache.org/viewQueued.html?itemId=734208 > > > > > > On 19.07.2017 17:55, Dmitry Pavlov wrote: > >> Hi Evgeniy, > >> > >> Thank you. Ign

Re: IGNITE-5123 Review

> The ticket was a regression from 1.9 to 2.0. I don't think anyone would be > expecting the behavior in 2.0 as it doesn't align with the javadoc and has > only been broken since the 2.0 release. > > -Nick > > On Wed, Jul 19, 2017, 6:55 AM Dmitry Pavlov <dpavlov@gmail.com> wro

Re: Hello

Hi Denis, Welcome to the Ignite community! If you need contributor access to Apache JIRA, could you please sign up and share your JIRA ID. Looking forward to your contributions! Sincerely, Dmitry Pavlov вт, 25 июл. 2017 г. в 14:21, Denis Mekhanikov <dmekhani...@gmail.com>: > Hi

Re: сhecksum algorythm

Hi Oleg, Both MD5 and SHA1 are deprecated and can't be considered as trustfull. I think at-least-256 bit member of the SHA-2 family (e. g. sha512) should be used. Sincerely, Dmitriy Pavlov ср, 26 июл. 2017 г. в 22:27, Oleg Ostanin : > Hi, > > We need to decide what

Re: IGNITE-5123 Review

Hi Evgeniy, I was not able to find Teamcity run for this change. Could you please run http://ci.ignite.apache.org test for example on branch pull/2285/head using 'Ignite 2.0 Tests' target 'Run All'. Or could you please share link to previous run on this changes? Sincerely, Dmitriy Pavlov ср, 19

Re: IGNITE-5123 Review

ed > tests seem to fail in several other reviews too and are unrelated to my > changes. > > > On 19.07.2017 17:35, Dmitry Pavlov wrote: > > Hi Evgeniy, > > > > I was not able to find Teamcity run for this change. > > Could you please run http://ci.ignite.apache.org

Make Teamcity Green Again

Hi Igniters, We all know that there are a lot of open tasks in Ignite project. To be able to handle all these tasks, we need to grow our community. And to achieve that, we should pay special attention to new community members. As recent newcomer I’ve faced the following problem: There is no way

Re: Ignite Teamcity email notifications

n't think ign...@apache.org is a valid email address. Why > creating a mailing list for TC is not a good option? > > On Thu, Jun 29, 2017 at 8:17 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi Igniters, > > > > I want to set up a email notifications

Ignite Teamcity email notifications

Hi Igniters, I want to set up a email notifications from the public Teamcity about broken builds. But there is no configured address and email account. To set up notifications we need some mail box (account) to send messages from. I asked the apache infrastructure team in

Re: abbrevation rules plugin

Hi, Val, No, this plugin is not available in apache-ignite code base. May be we should remove reference from JIRA or add this plugin (and also other code inspections) into AI code base. Thoughts? Sincerely, Dmitriy Pavlov вт, 4 июл. 2017 г. в 1:29, Valentin Kulichenko <

Re: abbrevation rules plugin

> вт, 4 июл. 2017 г. в 18:40, Dmitry Pavlov <dpavlov@gmail.com>: > > > Hi, Val, > > > > No, this plugin is not available in apache-ignite code base. > > May be we should remove reference from JIRA or add this plugin (and also > > other code inspectio

Re: Can we move tests to Java 8?

. This may be done by creating standalone module, in case of IGNITE-5483, e.g., sql-query-java8, and Run Configuration which will run this module test will be configured to use java 8. Best Regards, Dmitriy Pavlov чт, 6 июл. 2017 г. в 12:30, Dmitry Pavlov <dpavlov@gmail.com>: > Hi

Re: Can we move tests to Java 8?

Hi Vladimir, +1 from me, in addition we will be able to use java8 lambdas in test code. This make code shorter, and in the same time more expressive. Please involve me in this activity when it starts. Best Regards, Dmitriy Pavlov чт, 6 июл. 2017 г. в 11:21, Vladimir Ozerov

Re: daemon nodes

Hi, ok, if we have 3 type of nodes: - clients - servers - daemons. Let us merge all types of daemons in one daemon type and remove unused code for server daemon. Are there any concerns about this idea? Best Regards, Dmitry Pavlov ср, 28 июн. 2017 г. в 12:19, Dmitriy Govorukhin < dmitriy.govo

Re: Optimize transaction prepare step when store is enabled IGNITE-1553

Hi Aleksey, I am not able to change status for this issue. Could you please change to "Patch Available"? Best Regards, Dmitry Pavlov пт, 23 июн. 2017 г. в 22:17, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Yeah, it can be set "Patch available" because I need

Re: Get a ticket

Hi Andrei , IGNITE-5597 <https://issues.apache.org/jira/browse/IGNITE-5597> is unassigned. Usually such issue can be picked up by any community member. So please feel free to assign issue to yourself. Best Regards, Dmitry Pavlov чт, 29 июн. 2017 г. в 9:25, Elen Code <

Contributions

Hello, Ignite Community! My name is Dmitriy. I would like to contribute to Apache Ignite and want to start with this issue - IGNITE-5078. JIRA ID: dpavlov. Any help on this will be appreciated. Thanks! Best Regards, Dmitriy Pavlov

Re: IgniteUtils#currentTimeMillis

It seems System.currentTimeMillis () is now in intrinsic list. This means on modern JVMs performance penalty will not be so significiant. Nickolay, could you please raise standalone ticket for U.currentTimeMillis () ? Could you also please check if system.nanoTime / system.currentTimeMs can fix

Re: IgniteUtils#currentTimeMillis

Vladimir, could we check it using benchmarks? Internet contains a lot of articles about this issue. But do we know if it is still actual for new VMs? ср, 9 авг. 2017 г. в 14:50, Dmitry Pavlov <dpavlov@gmail.com>: > It seems System.currentTimeMillis () is now in intrinsic list. T

Re: IgniteUtils#currentTimeMillis

id > > unnecessary work. There is nothing wrong with U.currentTimeMillis() at > the > > moment. > > > > On Wed, Aug 9, 2017 at 2:52 PM, Dmitry Pavlov <dpavlov@gmail.com> > > wrote: > > > > > Vladimir, could we check it using benchmarks? Internet cont

Re: GridVersionSelfTest.testVersions #MakeTeamCityGreenAgain

Hi, Nikolay, I guess it may be related to http://apache-ignite-developers.2346864.n4.nabble.com/usage-analytics-td19504.html Test is now decided to be muted until decision is made. Actual scope of failures can be found in

Re: [IGNITE-5717] improvements of MemoryPolicy default size

Hi Igniters, When I was Ignite user before installing product on production server I’ve always used this page https://apacheignite.readme.io/docs/jvm-and-system-tuning for selecting appropriate parameters. But before go live, I’ve used Ignition.start() 20 times per day to check if my changes in

Re: SSL certificate for the CI server

Hi Dmitriy, I can see your user in user list. Moreover according to recent discussion http://apache-ignite-developers.2346864.n4.nabble.com/CI-Server-permissions-changed-td18500.html you have admin rigths. It is possible to 'Reset Password' using link on login page and passoword reset link will

Re: partitions exchange protocol details question

( GridDhtPartitionsSingleMessage), it removes one node from remaining set. The same is true for node left message. Best Regards, Dmitry Pavlov ср, 3 мая 2017 г. в 19:10, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Hi, Igntrs! When processing single partitions message in > GridDhtPartitionsExchangeFuture#pr

Ignite 2.0 TeamCity Run configurations

about what is to be migrated are appreciated. Best Regards, Dmitry Pavlov

Re: Negative non-heap memory maximum

should show a clean picture in the node output and will > also protect us from ambiguous -1 output. > > 2017-05-24 18:45 GMT+03:00 Dmitry Pavlov <dpavlov@gmail.com>: > > > Igniters, > > > > > > > > On my jdk 1.8.0_131 there is negative amou

Re: Optimize transaction prepare step when store is enabled IGNITE-1553

Hi Alexey, This ticket status is 'in progress'. Is it still in development or 'patch available' can be set? Sincerely, Dmitry Pavlov ср, 7 июн. 2017 г. в 17:03, ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>: > Hi, Igntrs! > Feel free to reviewing the ticket > https://issues.

Re: TC for master is moved to Ignite 2.0 test suite

. Best Regards, Dmitry Pavlov вт, 23 мая 2017 г. в 10:24, Vladimir Ozerov <voze...@gridgain.com>: > Fantastic news, thank you guys! Though, I still see "Basic" and "Binary > Object Basic" suites. Should we drop one of them as well? > > On Tue, May

Re: TC for master is moved to Ignite 2.0 test suite

Hi Igniters, Please review PR with 'Binary Basic' merge into 'Basic' https://github.com/apache/ignite/pull/1991 After PR is merged it will be possible to remove snapshot dependency from ‘Run All’ to ‘Binary Basic’ and remove run configuration. Best Regards, Dmitry Pavlov PS. TC run http

Re: Minimize amount of inner classes, predicates, tuples, etc

Hi Vladimir, Do you have any idea how this rules may be automatically controlled by, for example, code inspections and/or TeamCity? I do beleive if rule is controlled by some automatic way (not only by argreement) it has a chance to become true practice in real life. If this excellent idea

Negative non-heap memory maximum

Igniters, On my jdk 1.8.0_131 there is negative amount of maximum non heap memory returned by following code: ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax()); returns -1. And this value is used in ignite metrics in GridLocalMetrics.getNonHeapMemoryMaximum() which

Re: Ignite 2.0 TeamCity Run configurations

; > wrote: > > > What about 'Ignite H2 Indexing' suite', it does not execute any test? > > > > On Fri, May 26, 2017 at 2:18 PM, Dmitry Pavlov <dpavlov@gmail.com> > > wrote: > > > > > Hi Semen, > > > > > > > > > >

Re: Ignite 2.0 TeamCity Run configurations

s required in 2.0 run configs? Sincerely, Dmitriy Pavlov пт, 26 мая 2017 г. в 14:57, Dmitry Pavlov <dpavlov@gmail.com>: > Thank you! > > I've commited removal of both suites to PR > https://github.com/apache/ignite/pull/2014 > > > пт, 26 мая 2017 г. в 14:53,

Re: Ignite 2.0 TeamCity Run configurations

Hi, Igniters! Could you please review and merge changes from https://github.com/apache/ignite/pull/1956 into master. These changes makes running tests with similar results in TC Run configs "Ignite 2.0 Tests" as it is in "Ignite Tests". Best regards, Dmitry Pavlov ср, 17

Re: Ignite 2.0 TeamCity Run configurations

Igniters, I've created new PR https://github.com/apache/ignite/pull/1986 without merge conflicts against master. Please review these changes instead of PR1956. Thank you Best Regards, Dmitry Pavlov пн, 22 мая 2017 г. в 13:21, Alexey Goncharuk <alexey.goncha...@gmail.com>: > Thanks

Re: Default SQL schema name

+1 for ignite пн, 29 мая 2017 г. в 17:03, Igor Sapego : > I like "ignite" as it has lower chance to interfere with anything > which is already reserved. > > Best Regards, > Igor > > On Mon, May 29, 2017 at 5:01 PM, Sergi Vladykin > wrote: > > >

Re: TC for master is moved to Ignite 2.0 test suite

:54, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Igniters, > > > Please review PR with 'Binary Basic' merge into 'Basic' > https://github.com/apache/ignite/pull/1991 > > > After PR is merged it will be possible to remove snapshot dependency from > ‘Run All’ to

Re: TC for master is moved to Ignite 2.0 test suite

-testAllNodesDieOnRequest() -testNoNodesDieOnRequest() -testOneNodeDiesOnRequest() -testRequestedMappingIsStoredInFS() -testTwoNodesDieOnRequest() it will save 37 minutes of agent time more. I'll prepare PR Best Regards, Dmitry Pavlov вт, 23 мая 2017 г. в 10:43, Vladimir Ozerov <voze...@gridgain.

Re: "Review workflow" changes to prevent "broken review" issues.

Hi Igniters, Anton, Let’s imagine that development process as a chain of production stages 1) Developing patch by contributor 2) Review changes by committer Reviews waiting too long time to be done at stage 2 may indicate that speed (potential throughput) of step 2 is less than throughput at

Re: "Review workflow" changes to prevent "broken review" issues.

s > problem to periodically check is there somebody waiting. > > Guys, > Let's try this approach, and I'm pretty sure it will help. > > On Mon, Jun 5, 2017 at 7:58 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi Igniters, Anton, > > > > Le

Re: "Review workflow" changes to prevent "broken review" issues.

to help with analysis and assignment of these 66 tasks from next week. вт, 6 июн. 2017 г. в 12:57, Anton Vinogradov <avinogra...@gridgain.com>: > Dmitry Pavlov, > > There is *HUGE *difference between "Devlist, please review my changes" > and "Dmitry Pavlov, pleas

Re: "Review workflow" changes to prevent "broken review" issues.

; pretty low. > > > > To solve this issue I see two options: > > 1) Proposed by Anton. > > 2) Having a guy in the community who’ll keep an eye on all the incoming > > pull-requests shuffling them between committer in the same way proposed > in > > 1

TeamCity triggers change proposal

Hi Igniters, Most of us at least once have faced with situation that we have important fix to be tested, but TeamCity is busy and queue is too long. Ignite 2.0 test introduction helped to reduce time to wait, but still there is potential to get results for your PR tests faster. Contribution

Re: TeamCity triggers change proposal

welcome. Best Regards, Dmitry Pavlov пн, 19 июн. 2017 г. в 14:50, Semyon Boikov <sboi...@gridgain.com>: > Hi Dmitry, > > Is it possible instead to set priority for manually started builds higher > than for builds triggered by git? > > Thanks > > On Fri, Jun 16,

Re: TC-tests: is default-branch the master-branch?

lt;voze...@gridgain.com>: > >> Hi Vyacheslav, >> >> 1) Yes >> 2) Yes >> 3) Probably Dmitry Pavlov or Dmitry Govorukhin could give more info on >> current state and goals of "Broken Tests" suite. >> >> On Thu, Jun 8, 2017 at 4:32 PM, Vyache

Re: partitions exchange protocol details question

ssages from different nodes has got equal > exchangeId. > > ср, 3 мая 2017 г. в 19:23, Dmitry Pavlov <dpavlov@gmail.com>: > > > Hi, Aleksey, > > > > empty remaining set > > > > > (org.apache.ignite.internal.processors.cache.distributed.dht.p

Ignite PDS WAL analysis with human readable records

Hi Igniters, Eduard Shangareev created WAL converter utility which shows WAL archive/work directory segments content in human readable form. This utility outputs all WAL records to output stream (may be redirected to file). How to use tips can be found in issue

Re: Ignite PDS WAL analysis with human readable records

dealing with the issue in IGNITE-6342. It > > helped to find out the error in how we deal with partition size. > > > > Best regards, > > Ed. > > > > > > > > > > On Sat, Sep 16, 2017 at 2:09 AM, Dmitry Pavlov <dpavlov@gmail.com> > >

Re: Ignite PDS WAL analysis with human readable records

Tag=0, > > lastAllocatedPageCount=0, > > candidatePageCount=0 > > ], > > PagePartitionMeta[ > > size=198, > > updateCounter=198, > > globalRemoveId=150541242286100, > > partitionState=1(OWNING), > > countersPageId=281513631416333 > &g

Re: Ignite PDS WAL analysis with human readable records

he ticket? > > Here is the link for easier access: > https://issues.apache.org/jira/browse/IGNITE-6421 > > D. > > On Mon, Sep 18, 2017 at 7:02 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Dmitriy, > > > > Thank you for your feedback I've create

Re: Exception handling in thin client: should we pass stack traces to the client?

Hi Vladimir, All of these arguments are relevant. I suggest to provide full stacktrace at least by server option. This is also common practice on web servers. Sincerely, Dmitriy Pavlov вт, 19 сент. 2017 г. в 10:20, Vladimir Ozerov : > Igniters, > > We had a discussion

Re: Binary compatibility of persistent storage

I have same idea about testing of WAL compatibilty between releases. It will be actual since 2.3 release (as 2.2 was emergency release without impact changes). I look forward to IGNITE-5732 completion and merge. And then I able to start writting first test. I think it is quite unexpected for

Re: Binary compatibility of persistent storage

Denis, the argument sounds convincing to me. When you use 3rd party DB, you rarely have to care how to migrate DB data. Igniters, I suggest keeping compatibility as long as we can, even with the transition to a new major release. If incompatibility will become unavoidable we will consider

Re: Monitoring of active transactions

; > Good point, > > but, seems you should start separate thread to discuss this. > > > > On Fri, Sep 8, 2017 at 4:28 PM, Dmitry Pavlov <dpavlov@gmail.com> > > wrote: > > > > > Hi Ilya, > > > > > > I'm definitely +1 for in

Re: Ignite cluster with persistent store enabled did not load from wal after restarting.

Hi Denis, I agree that data presence should be double-checked. In case check will show that 1) cache doesn't exist at all after restart and 2) we can find two folders with binary_meta and wal that means this question is similar with recent question

Re: Ignite PDS WAL analysis with human readable records

y, Eduard, > > Sounds like a useful thing. I’ll be happy to give a feedback but need a > documentation that explains how to use the tool, what’s the output format, > how do decipher the output, etc (basic things). The Wiki description should > be enough. > > — > Denis > >

Re: Identifying grid transactions

Hi Igniters, Would it be useful to provide some traceability identifier for messages participating in the partition map exchange? This can be used to filter all logs associated with the exchange. Or now there is some possibility? Sincerely, Dmitriy Pavlov чт, 5 окт. 2017 г. в 2:01, Valentin

Re: Logical Cache Documented

Hi, bigger B+ Tree = more operations to find a value. User may expect that cache having 20 entries (e.g. dictionary) will have great performance on get() and put(). But instead (if the 1 global cache group became default), such caches will take the same amount of time as the huge cache with

Re: Should we take care of Java 9 in Ignite 2.0 scope?

I'll personally would also greatly appreciate if ignite-core is build using (source and target) version of JDK 8. All contributors will be able to write code shorter and more expressively using code Java 8. ср, 4 окт. 2017 г. в 11:55, Yury Babak : > It`s true, now building

Re: Logical Cache Documented

+1 to Vladimir. I think it is better to keep this feature disabled by default. And enable cache groups only in case this feature is required by user needs. Enabling this will cause all caches will be placed into one tree. After collapsing all B+-trees into one we will get log(N1+N2+N3) instead

Enhance persistent store paths: new persistent store folders naming

Hi Igniters, Issue for improve persistent store paths https://issues.apache.org/jira/browse/IGNITE-6285 has been resolved. Thanks to Alexey G. and Yakov for review. Details of change are available in wiki

Re: Enhance persistent store paths: new persistent store folders naming

ence-23#section-configuration > > > > That page is hidden and will be released along with 2.3. Provided you with > required permissions. > > Please send me for review once you’re ready. > > — > Denis > > > On Oct 4, 2017, at 10:26 AM, Dmitry Pavlov <dpavlov@

Re: Enhance persistent store paths: new persistent store folders naming

Thank you! чт, 5 окт. 2017 г., 19:51 Denis Magda <dma...@apache.org>: > Dmitriy, > > Ok, I’ll take care of the docs. > > — > Denis > > > On Oct 5, 2017, at 9:41 AM, Dmitry Pavlov <dpavlov@gmail.com> wrote: > > > > Hi Denis, > > &g

Re: Cluster name

I like this idea too. Some imdg have such feature and allow to limit cluster building only within cluster name. ср, 11 окт. 2017 г. в 12:38, Alexey Kuznetsov : > Hi, > > I'd like to up this thread for discussion. > > It seems that cluster name could be very useful together

Re: Monitoring of active transactions

Hi Ilya, I'm definitely +1 for including the utility in the product. Perfect contribution. Sincerely, Dmitriy Pavlov пт, 8 сент. 2017 г. в 14:28, Ilya Lantukh : > Igniters, > > According to our current design and implementation, unclosed transaction or > unreleased lock

Re: Massive commit sizes for processes with local Ignite Grid servers

Hi Raymond, Total memory usage since 2.0 version is determined as sum of heap size and memory policies MaxSizes (overall segment sizes). If it is not configured there is 80% of physical RAM is used for each node (before 2.2). In 2.2 this behaviour will be changed. To run several nodes at one PC

Re: P2P Deployment - Local Ownership Flag

Hi Igniters, I assume this may be related to case desctibed by user in http://apache-ignite-users.70518.x6.nabble.com/Understanding-the-mechanics-of-peer-class-loading-td12661.html We didn't managed to create a reproducer for this issue. But case is similar: - server has cache classes in

Re: Check Ignite build for different Java before VOTE

Hi Aleksey, I think all types of release automation is very good for improving our processes and provide stable product. Currently I am not able to view new Run configs: You do not have enough permissions to access build type with id: IgniteRelease_427CheckBuildIgniteFabricOpenJDK8 What should

Re: Default CacheConfiguration instance can't be serialized

Hi Nikolay, It is strange, because Cache Configuration is saved under StoreConfiguration into persistent store cache_data file. Did you find an anwser? Sincerely, Dmitriy Pavlov вт, 26 сент. 2017 г. в 19:02, Николай Ижиков : > Hello, Guys. > > I found that

Re: Persistence per memory policy configuration

es to be in-memory only and others to be on disk. > > Given that we are already refactoring, it only makes sense to pick better, > more appropriate names. > > D. > > On Tue, Sep 26, 2017 at 7:20 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Vladimi

Re: Persistence per memory policy configuration

Hi Igniters, sorry for late response. I didn't catch idea of renaming. PersistentStoreConfiguration is intuitive, and MemoryPolicyConfiguration is intuitive also. If we rename these classes now, it will bring more questions to user list. Users may be confused by old and new names and by trying to

Re: Persistence per memory policy configuration

have to put additional efforts to docs and JavaDocs. > But the earlier we do that, the better. > > On Tue, Sep 26, 2017 at 4:50 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi Igniters, sorry for late response. I didn't catch idea of renaming. > &

Re: Binary compatibility of persistent storage

in the chain RunAll, and daily for master. Sincerely, Dmitriy Pavlov чт, 21 сент. 2017 г. в 0:39, Dmitry Pavlov <dpavlov@gmail.com>: > Denis, the argument sounds convincing to me. When you use 3rd party DB, > you rarely have to care how to migrate DB data. > > Igniters,

Re: Ignite Durable Memory & Persistent Store introduction for developers

to pages. чт, 31 авг. 2017 г. в 3:53, Dmitriy Setrakyan <dsetrak...@apache.org>: > Dmitriy, this is very useful! Any chance you can also blog about it? > > On Wed, Aug 30, 2017 at 6:24 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi Igniters, > > >

Re: IgniteFuture -> CompletableFuture

+1 for migrating to java 8. Sincerely, Dmitriy Pavlov On чт, 31 авг. 2017 г., 11:03 Yakov Zhdanov wrote: > CompletableFuture is part of java 8. > > --Yakov > > 2017-08-31 4:46 GMT+03:00 Dmitriy Setrakyan : > > > Igniters, > > > > I received the

Re: Ignite Durable Memory & Persistent Store introduction for developers

5) "If memory amount less than whole index size, Ignite still can operate.” > > How do we define “index size”? Is this the page size? > > > — > Denis > > > > On Aug 30, 2017, at 8:24 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > > H

Ignite Durable Memory & Persistent Store introduction for developers

Hi Igniters, I am glad to introduce two new wiki articles. These articles contain high-level description of - Ignite Durable Memory ( https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood ) - and Ignite Persistent Store (

Re: IgniteFuture -> CompletableFuture

> > There is no need to migrate to Java 8 to support CompletableFuture. > Create > > separate Maven project and compile it with Java 8 - this is it. > > > > Vova, I am not sure I understand. How will it be released? > > > > > > On Thu, Aug 31

Re: [DISCUSSION] Urgent Ignite bug fix release

Hi, at least for this release I suggest to keep versioning as is and use 2.2 Without solved issue with http://apache-ignite-developers.2346864.n4.nabble.com/usage-analytics-td19504.html Ignite will not remind users about latest available ignite version. Versioning structure change will confuse

Re: Ignite Durable Memory & Persistent Store introduction for developers

is. > > 5) "If memory amount less than whole index size, Ignite still can operate.” > > How do we define “index size”? Is this the page size? > > > — > Denis > > > > On Aug 30, 2017, at 8:24 AM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > &

Re: request for contributors permissions

Hi, Thank you for interest in Apache Ignite! Could you please share your Jira Id? Sincerely, Dmitry Pavlov вс, 26 нояб. 2017 г., 11:14 Ruslan Shlin <shli...@gmail.com>: > I want to participate and contribute to Ignite project >

Re: Losing data during restarting cluster with persistence enabled

e is short explanation and this - > > > https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/localstore/LocalRecoverableStoreExample.java > > - is example implementation. > > > > > > On 11/23/2017 4:42 PM, Dmitry P

Re: Losing data during restarting cluster with persistence enabled

Please see the discussion on the user list. It seems that the same happened there: http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-td7461.html#a7468 it contains examples when the data can diverge. пт, 24 нояб. 2017 г. в 16:42, Dmitry Pavlov <dpavlov@gmail.com>: &

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?

Re: IgniteProjectionStartStopRestartSelfTest is failing for about a week on TC

Hi Igniters, Who can became Jedi of TeamCity and substitute me in this research? Sincerely, Dmitry Pavlov пт, 15 дек. 2017 г. в 12:38, Anton Vinogradov <avinogra...@gridgain.com>: > Dmitry, > > Could you please investigate? > > On Fri, Dec 15, 2017 at 9:16 AM, A

Re: Switching Java language level to 8

+1 Java 8 has a lot of APIs, we sometimes need it to improve our performance. чт, 14 дек. 2017 г. в 15:16, Дмитрий Рябов : > +1 > Agree, I think changes will be less difficult if we go through 7/8 -> > 8 -> 8/9 than 7/8 -> 7/8/9 ( -> possible 7/8/9/10 huh?) -> 8/9. > >

Re: Data eviction/expiration from Ignite persistence

Hi Denis, What is the difference of required by users functionality with TTL cache expiration? By some posts I can suppose TTL cache is compatible with native persistence. Sincerely, Dmitriy Pavlov сб, 18 нояб. 2017 г. в 0:41, Denis Magda : > Igniters, > > I’ve been talking

Re: Data compression in Ignite

oze...@gridgain.com>: > Dmitry, > > What we've discussed so far in this topic is essentially the same concept. > We will deduplicate same byte sequences on page level. > > On Fri, Nov 10, 2017 at 6:10 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: > > > Hi

Re: Data compression in Ignite

Memory? Sincerely, Dmitry Pavlov ср, 18 окт. 2017 г. в 18:52, daradurvs <daradu...@gmail.com>: > Hi, Igniters! > > Are there any results of researching or a prototype of compression feature? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >

Re: Data compression in Ignite

e doesn't dominate in user models, so I do not see > why it should be a kind of special case. > > пт, 10 нояб. 2017 г. в 18:45, Dmitry Pavlov <dpavlov@gmail.com>: > > > Vladimir, > > > > orientation on string will also allow us to deduplicate strings in

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

Hi Anton, > - GC STW duration exceed maximum possible length (node should be stopped > before STW finished) Are you sure we should kill node in case long STW? Can we produce warnings into logs and monitoring tools an wait node to become alive a little bit longer if we detect STW. In this case

Re: Data eviction/expiration from Ignite persistence

plus https://apacheignite.readme.io/docs/distributed-persistent-store Sincerely, Dmitriy Pavlov сб, 18 нояб. 2017 г. в 12:12, Dmitry Pavlov <dpavlov@gmail.com>: > Hi Denis, > > What is the difference of required by users functionality with TTL cache > expiration? >

Re: Stop Ignite opening 47500 and 47100

Hi, please see examples in org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneNoopCommunicationSpi and StandaloneNoopDiscoverySpi. also please make sure classes are annotated @IgniteSpiNoop This annotation helps Ignite ingernal stuff to identify this implementation

  1   2   3   4   5   6   7   >