Re: Issue of ignite run in docker

Hi Joe Chen, Could you please run ignite in verbose mode and share logs? In verbose mode Ignite prints useful information which should clarify your issue. ENTRYPOINT ["bin/ignite.sh -v"] Also you opened ports for Discovery, but need to open ports for Communication too. -p 47100-47109:47100-471

Re: Ignite for Spark on YARN Deployment

You set wrong value to IGNITE_XML_CONFIG property. The property should contains path to ignite configuration file. For example IGNITE_XML_CONFIG=/u/hongmei/apache-ignite/config/default-config.xml I think you can comment this line in property file and ignite will start with default configuration.

Re: Ignite for Spark on YARN Deployment

: >> container_e24_1464374946035_29722_01_18. State: COMPLETE. >> Jun 09, 2016 10:48:31 AM org.apache.ignite.yarn.ApplicationMaster >> onContainersCompleted >> INFO: Container completed. Container id: >> container_e24_1464374946035_29722_01_17. State: COMPLET

Re: Why the Continuous Queries ignore expired event permanently?

Hi Lin, CQ doesn't support expired events by historical reason. But you can use CacheEntryListener [1] which support the same functionality that CQ and allow to get expired events [2]. [1] IgniteCache#registerCacheEntryListener [2] javax.cache.event.CacheEntryExpiredListener On Wed, Jul 6, 2016

Re: secured mesos deployment

gnite > framework... > > Le 11 oct. 2016 3:10 AM, "Denis Magda" a écrit : > >> I’m not an expert in Apache Mesos but think that this can be done using >> standard Mesos configuration files. However, it depends on what part of the >> deployment you wish to sec

Re: secured mesos deployment

same question for the > mesos role because I don't use *, problem is that ignite tries to request > resources with role *, which is forbiden... > Rgds > > 2016-10-11 15:12 GMT+02:00 Nikolay Tikhonov : > >> Hi Vincent, >> >> Ignite Mesos Framework connecting

Re: Cache Memory Behavior \ GridDhtLocalPartition

Hi Isaeed Mohanna, Could you please try to use ignite with the following JVM oprtion -DIGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE=100? For atomic caches Ignite does not remove entry from memory immediately to avoid some data consistency issue and this behaviour can to encrease memory consumption. On

Re: Affinity

Anil, This SQL query will not work correctly due to IGNITE-3860. It contains subquery which will not distribute on all nodes and will execute locally. Please, see on limitations https://apacheignite.readme.io/v1.8/docs/dml#known-limitations Thanks, Nikolay On Mon, Jan 2, 2017 at 3:48 PM, Anil w

Re: Release 1.9.x?

Hi Steve, Exist vendors that make builds based on different versions of Apache Ignite. I think you can easy find them. On Wed, Jul 5, 2017 at 6:48 PM, Michael Cherkasov < michael.cherka...@gmail.com> wrote: > Hi Steve, > > if something that you need is fixed in master or 2.x releases, you always

Re: Apache ignite mesos tried to connect tiny.cc for self updating

Hi, Yunfeng! Yes, it's right way to deploy ignite over mesos. I'm sorry but I don't see any workaround in your case. I've created ticket https://issues.apache.org/jira/browse/IGNITE-2435 and hope that fix will be avalible in the nearest release. On Thu, Jan 21, 2016 at 10:27 PM, Yunfeng wrote: