Thanks Slave, this is working for us now. There was a configuration issue in
org.apache:clsLdr=*
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/I-am-not-able-to-read-mxbean-values-of-ignite-tp16022p16123.html
Sent from the Apache Ignite Users mailing list archiv
sorry, Ignore this.
ThanksShawn
On 08/11/2017 11:03,shawn.du wrote:
Hi community,I have a ignite server(1.9.0) and a ignite client.Recently my client crashed 4 times. I found it may be caused by s
This simply means that environment variable is not picked up by the process.
If you run in Eclipse, probably you just need to restart it.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Setting-custom-Log-location-log4j-tp16106p16121.html
Sent from the Apac
Thanks for the response.
So does that mean with onHeap enabled, the normal JVM Memory and GC tuning
parameters don't work as expected? I am using CMS garbage collector and was
hoping that it will take care of cache-keys eviction from the onHeap memory.
--
View this message in context:
http:/
Hi community,I have a ignite server(1.9.0) and a ignite client.Recently my client crashed 4 times. I found it may be caused by server send big data to client. see blow picture. this is AWS Cloud Watch network-out-bytes picture of ignite server. It seems that ignite server do somethi
Hi Val,
Can you help me out with the configuration change for log4j ? I have
provided the value of LOG_HOME in environment variables in eclipse. Here is
what I have
I am having similar problem setting persistent
Hi Val,
I have seen the hadoop accelerator link you shared.
If i have to choose from the following combination for the performance
reason which one should i choose? why? and when should i choose?
1) Hive on MR(Standard Hadoop MR)
2) Hive on Ignite MR
3) Hive on Spark
4) Hive on Tez
5) Hive on Te
Val, thanks for pointing it out. Now I call AtomicLong Function from
service#execute() and it's working. Thank you very much!
Jessie
On Thu, Aug 10, 2017 at 3:08 PM, vkulichenko
wrote:
> Jessie,
>
> You still call atomicLong() method from Service#init(). As I already
> mentioned, this is causin
Ravi,
If you need to speed up SQL, you should make sure Ignite uses indexes to
execute queries. I think you can do the following:
- Create Hive RDD and map it to RDD of key value pairs.
- Create new IgniteRDD on top of a cache and use IgniteRDD#savePairs method
to load data from Hive to Ignite.
-
Ravi,
Have you seen the Hadoop Accelerator?
https://apacheignite-fs.readme.io/docs/hadoop-accelerator
It also provides custom implementation of MR engine.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Apache-Tez-support-for-Ignite-tp16086p16114.html
Sen
Jessie,
You still call atomicLong() method from Service#init(). As I already
mentioned, this is causing the startup hang. You should move
IgniteAtomicLong creation out of init() method to avoid it.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Streaming-
Hi Roger,
It's a known issue and fixed in master. You can try to build from there or
check the latest nightly build:
https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Viso
Path for log files is ${IGNITE_HOME}/work/log/, as specified in the log4j
file. If log4j logger is used and if configuration was not changed, then
most likely the change to IGNITE_HOME property variable you made was not
picked by the process. You can check it in the log - Ignite prints out
IGNITE_H
Hello,
the cache counts that are shown in Visor seem to be twice the number that is
expected.
I am using ver. 2.1.0#20170720-sha1:a6ca5c8a, with native persistence.
For a replicated cache, with 363 objects loaded (select count(*) returns 363):
Nodes for: FabricCache(@c0)
+=
Val, please see thread print attached.
This is take after a server is run by "bin\ignite.bat
config\ignite-writebehind.xml" and the service initialization didn't
complete.
Thank you very much for helping out!
"srvc-deploy-#33%null%" #59 prio=5 os_prio=0 tid=0x577b8000
nid=0x1ef8 waiting on
Folks,
I’ve updated the documentation avoiding any misunderstanding - " If Ignite
Persistence is enabled then the page-based evictions have no effect because the
oldest pages will be evicted from RAM automatically if there is not enough
space available.”
https://apacheignite.readme.io/v2.1/doc
Thank you.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Persistent-store-and-eviction-policy-tp16092p16107.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi all,
I intend to use log4j for Apache Ignite logging. The steps I followed are
1) add maven dependency of
org.apache.ignite
ignite-log4j
2.0.0
2) set the following in IgniteConfiguration file
Hi,
Provided configuration works as expected on Ignite version 2.1.
On my side, in this configuration, I got 3 memory segment allocations.
Have you tried requesting cache.size() after populating the cache?
Please provide the full configuration files so as I could check them.
Kind regards,
Alex.
Hi
Thanks for the details. I have sent the email to subscribe now and got
confirmation back. The reason i have asked the question about Tez and LLAP
is apache hive community has deprecated the MR as execution engine and
moving towards Tez and LLAP, Will Ignite have equivalent In Memory Tez/LLAP
im
Hi Rodrigo,
I'm not sure how Flink works, but to write to IGFS you need to use special
implantation of HDFS:
fs.igfs.impl
org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem
fs.AbstractFileSystem.igfs.impl
org.apache.ignite.hadoop.fs.v2.IgniteHadoopFileSystem
Somehow
Hi Rodrigo,
I'm not sure how Flink works, but to write to IGFS you need to use special
implantation of HDFS:
fs.igfs.impl
org.apache.ignite.hadoop.fs.v1.IgniteHadoopFileSystem
fs.AbstractFileSystem.igfs.impl
org.apache.ignite.hadoop.fs.v2.IgniteHadoopFileSystem
Somehow
Hi! I am trying to configure and test my custom memory policy for the simple
1 client - 1 server node topology.
In order to do this I added memory configuration for my server node like
this with 1GB_Region_Eviction memory policy configured.
Hi Ravi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
> Similarly hive on spark with ignite will it work?.
Hi,
Please share full logs from all nodes so I can help in investigating of your
problem.
Evgenii
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Activating-Cluster-taking-too-long-tp16093p16099.html
Sent from the Apache Ignite Users mailing list archive at Nab
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages.
To subscribe, send an empty email to user-subscr...@ignite.apache.org and
follow simple instructions in the reply.
Out of the box, Ignite supports ANSI 99 SQL compatible feat
Hi!
I'm afraid, description of page-based eviction in documentation is not
quite correct.
Page-based eviction (RANDOM_LRU or RANDOM_2_LRU) can be activated only
if persistent store is /disabled/. It defines algorithm for choosing
page in RAM to remove all contents completely.
On the other h
Hi,
1. Persistence and Data Eviction are alternative options to handle
out-of-memory scenarios.Persistence makes Ignite fill all available RAM and
move the oldest page to the “disk” part of the cache when there is not enough
memory.
Data eviction policy makes Ignite to completely remove some ent
Hi!
I am experimenting with v2.1 persistence store enabled.
1. Created 8 caches and pumped data into them.
2. Restarted the ignite cluster.
3. Waited for all server nodes to join the cluster.
4. called Ignite.active(true);
I observed the cluster activation time is more than 1 hour with the
follo
29 matches
Mail list logo