Re: H2 SQL query optimiser strategy in Ignite
Hi Ignite Team, Have the system architects explored the option of maintaining table statistics on each node (as Postgres and other legacy SQL engines do), and then distributing the raw SQL query to each node and letting each node execute the query planner locally, optimising the query based on the statistics on hand for the given node...? Would this not optimise overall performance of the query, and eliminate the need for developers and DBAs to have try to guess the optimum JOIN order? (which may in fact vary on each node...?) Thanks, Jose -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: What is the convenient way to import data from a large number of files in HDFS?
Hi, You can load data with Spark that connects to Hadoop in one end and to Ignite on the other. Denis On Wednesday, May 8, 2019, liyuj <18624049...@163.com> wrote: > Hi, > > What is the convenient way to import data from a large number of files in > HDFS? > > > -- -- Denis Magda
What is the convenient way to import data from a large number of files in HDFS?
Hi, What is the convenient way to import data from a large number of files in HDFS?
Re: Web Console: Monitoring?
GridGain is not planning to donate this feature. Not sure if the community is willing to implement it from scratch. - Denis On Wed, May 8, 2019 at 12:13 AM sv wrote: > Are there any plans to add Monitoring to Web Console? Seems like a highly > desirable feature. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: SQL delete command is slow and can cause OOM
Hi, You have to also fetch values to do a "compare-and-delete". Before deleting each entry you check if it has been concurrently modified. If it was then it's possible that the entry doesn't match your WHERE anymore. So yes, for now deleting a large number of entries is heap-intensive. It should improve when https://issues.apache.org/jira/browse/IGNITE-9182?jql=text%20~%20%22delete%20lazy%22%20and%20project%20%3D%20ignite is fixed. When it is done, you'll be able to set lazy=true for a DELETE and avoid the OOM. For now though I suggest to change the query in a way that it returns less entries, or use key-value API for deletions. Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite statistics in the logs
Yes, thank you, I guess I missed setting the IGNITE_QUIET to false when I tried it out. As far as performance overhead, do you have any pointers? Of course, every environment is different, but I am hoping setting the 'metricsLogFrequency' to something like once every 5 minutes would not be too bad. On Wed, May 8, 2019 at 9:13 AM Vladimir Pligin wrote: > Hi, > > As far as I know this information should be shown in Ignite logs with > default setup. > The only thing you need to do is to run ignite.sh with -v option or set > system property IGNITE_QUIET to false if you run a node without ignite.sh. > In my setup it looks like > > [18:47:30,425][INFO][grid-timeout-worker-#39][IgniteKernal] > Metrics for local node (to disable set 'metricsLogFrequency' to 0) > ^-- Node [id=029b4aeb, uptime=30:41:07.843] > ^-- H/N/C [hosts=1, nodes=2, CPUs=16] > ^-- CPU [cur=0%, avg=0.01%, GC=0%] > ^-- PageMemory [pages=200] > ^-- Heap [used=77MB, free=92.35%, comm=1010MB] > ^-- Non heap [used=69MB, free=90.67%, comm=71MB] > ^-- Outbound messages queue [size=0] > ^-- Public thread pool [active=0, idle=0, qSize=0] > ^-- System thread pool [active=0, idle=6, qSize=0] > > Does it make sense for you? > - > Vladimir > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Ignite statistics in the logs
Hi, As far as I know this information should be shown in Ignite logs with default setup. The only thing you need to do is to run ignite.sh with -v option or set system property IGNITE_QUIET to false if you run a node without ignite.sh. In my setup it looks like [18:47:30,425][INFO][grid-timeout-worker-#39][IgniteKernal] Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=029b4aeb, uptime=30:41:07.843] ^-- H/N/C [hosts=1, nodes=2, CPUs=16] ^-- CPU [cur=0%, avg=0.01%, GC=0%] ^-- PageMemory [pages=200] ^-- Heap [used=77MB, free=92.35%, comm=1010MB] ^-- Non heap [used=69MB, free=90.67%, comm=71MB] ^-- Outbound messages queue [size=0] ^-- Public thread pool [active=0, idle=0, qSize=0] ^-- System thread pool [active=0, idle=6, qSize=0] Does it make sense for you? - Vladimir -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite with Hibernate 5.3
When it will be released? > On 8 May 2019, at 15:29, Vladimir Pligin wrote: > > Hi Tomasz, > > It seems like Hibernate 5.3 support has been already added to Ignite in the > master branch. > I suppose this feature will be delivered as a part of upcoming Ignite > release. Here is the corresponding ticket > https://issues.apache.org/jira/browse/IGNITE-9893, fix version is 2.8. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ignite statistics in the logs
Hello, I would like to see some periodic basic topology health statistics in the logs, such as CPU, heap/off heap usage etc. What would be a preferred way to configure that in a production like environment, without a significant performance overhead? Thank you, Loredana Radulescu Ivanoff
Re: Error installing Ignite on K8s
Hi, As far as can see you're facing an issue related to k8s service configuration. It's quite difficult to say whether you have issues with Ignite pods at this stage. So let's try to figure it out step by step. I suppose that the error is related to load balancing. As far as I know AWS provides multiple load balancer types and it seems like the particular one doesn't support session affinity based on client IP. Could you please check whether this one works for you https://pastebin.com/uEfL0rDd? I've changed a type of load balancer to network load balancer. Depending on the result let's discuss further steps. - Vladimir -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite with Hibernate 5.3
Hi Tomasz, It seems like Hibernate 5.3 support has been already added to Ignite in the master branch. I suppose this feature will be delivered as a part of upcoming Ignite release. Here is the corresponding ticket https://issues.apache.org/jira/browse/IGNITE-9893, fix version is 2.8. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ignite with Hibernate 5.3
Hi, we are developing Spring application with Hibernate 5.3... Does Ignite works with Hibernate 5.3? What Maven dependencies i can use? Thanks, Tomasz Prus
Re: Web Console: Monitoring?
Are there any plans to add Monitoring to Web Console? Seems like a highly desirable feature. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
