YARN parameters and default values

I see that our YARN parameters and default values do not quite align with Ignite 2.x Durable Memory: IGNITE_MEMORY_OVERHEAD_PER_NODE: The amount of memory allocated to handle JV

Re: Move documentation from readme.io to GitHub pages

I noticed that Facebook open-sourced a documentation platform last month, https://docusaurus.io/, which may be worth considering. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Per-entry overhead - some questions

Thanks Alexey, understood. What is the format of the object that is stored off-heap, is it a BinaryObjectOffheapImpl (or a parent class/interface) or something else? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Per-entry overhead - some questions

Hi Igniters, I have been looking in to the per-entry overhead for Ignite cache entries and have a couple of questions. 1. Does each GridCacheMapEntry require a reference to GridCacheContext or could this field be removed/optimized in some way? Is the GridCacheContext instance the same for every e

Re: [VOTE] Apache Ignite 1.6.0 RC1

-1 I'm struggling to get the tests to pass on Solaris 10. Have twice had what appear to me to be deadlocks in IgniteCrossCacheTxNearEnabledSelfTest3 -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-6-0-RC1-tp8992p9030.html Sent from t

Re: Ignite Release Schedules - a suggestion

dsetrakyan wrote > I actually think that the structure can be simpler and we should just > create a branch per release. Most likely, everything that is currently in > master should be released anyway, as we all work very hard on making sure > that master branch is always stable. > > I think it doe

Re: Ignite Release Schedules - a suggestion

Konstantin Boudnik-2 wrote > On Tue, May 17, 2016 at 01:09AM, endianignite wrote: > [...] > How would you propagate bug fixed among releases in this case? > signature.asc (237 bytes) > <http://apache-ignite-developers.2346864.n4.nabble.com/attachment/8959/0/signature.asc>; I

Re: Ignite Release Schedules - a suggestion

With regard to branch structure, I took some time to think and have a suggestion. Feel free to pick holes in it. Major feature releases would continue to have major version numbers: e.g., 1.7, 1.8, 2.x and so on. Bug-fix releases would be minor releases: e.g., 1.7.1, 1.7.2, 1.7.x, etc. Major re

Ignite Release Schedules - a suggestion

Dear Igniters, First of all, congratulations on heading towards the 1.6 release. Each Ignite release is a huge amount of work, done to a very high standard by a great group of people. I raise my hat to each and every one of you! I would like to open a discussion regarding release schedules, and

Re: Deprecate GridFunc

Wow, that really is an infamous class. Yikes. +1 from me for deprecate & refactor. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-GridFunc-tp8214p8217.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

CacheStoreBalancingWrapper is not serializable

Should I make CacheStoreBalancingWrapper serializable, or is there a reason not to? If no objections I will raise a JIRA and make the change. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/CacheStoreBalancingWrapper-is-not-serializable-tp8215.html Sent f

Re: Serialization exception when migrating from 1.3 to 1.5

There turned out to be a stray Ignite instance referenced in a field in the CacheStore implementation. I've refactored to remove that and now 1.5 is working fine. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Serialization-exception-when-migrating-from-

Serialization exception when migrating from 1.3 to 1.5

I am attempting to migrate from 1.3.0-incubating to 1.5.0.final. However, when I start my cache I get the following exception Exception in thread "main" java.lang.IllegalArgumentException: This method should be accessed under org.apache.ignite.thread.IgniteThread at org.apache.ignite.internal.Ign