Re: Professional Ignite Course

Hi Denis, This is great to hear about course on Ignite. Will there be one addressing Ignite in .Net technology? Regards, Sudhir On Thursday, September 26, 2019, Denis Magda wrote: > Igniters, > > Recently, I've come across a professionally crafted course about Apache > Ignite. It will be

Re: Professional Ignite Course

I did went trough the course and I asked pluralsight to add more, in the next course I would like to see ignite installation on aws and spark + ignite integration. Real time analytics with spark + ignite. On Wednesday, September 25, 2019, Denis Magda wrote: > Igniters, > > Recently, I've come

RE: Exception during exception handling

I don’t know how fix deserialization, it seems very internal. But I can do something for exception handling, but only on weekend. Andrey. От: Denis Magda Отправлено: 26 сентября 2019 г. в 0:30 Кому: user@ignite.apache.org Копия: Ilya Kasnacheev Тема: Re: Exception during exception handling

Re: Exception during exception handling

Andrey, Would you mind sending a pull-request if you have a clear understanding of how this needs to be fixed? - Denis On Wed, Sep 25, 2019 at 2:06 PM Andrey Davydov wrote: > There are two root causes. > > > > The first one is deserialization of binary object for “toString” when it > is

RE: Exception during exception handling

There are two root causes. The first one is deserialization of binary object for “toString” when it is impossible to deserialize (like IGNITE-12178). I saw stackowerflow discussion about fails on debug logging while googling current problem. The second, but it may be more important, it is

Professional Ignite Course

Igniters, Recently, I've come across a professionally crafted course about Apache Ignite. It will be interesting for some of you: https://www.pluralsight.com/courses/apache-ignite-getting-started Edward, thanks for the course! I've added it to Ignite Doc's menu right below the book. - Denis

Re: Service Registry

Hi, Please check this documentation pages and let us know if you need any clarification: https://apacheignite.readme.io/docs/ignite-service https://apacheignite.readme.io/docs/kubernetes-ip-finder - Denis On Sat, Sep 21, 2019 at 6:27 PM narges saleh wrote: > Hi All, > > I understand that I

Re: Too many file descriptors on ignite node

Hi, This sounds more like a need for configuration changes. You might need to adjust a number of WAL segments and tweak WAL archive related parameters. Please check this discussion below http://apache-ignite-users.70518.x6.nabble.com/WAL-size-control-td18323.html and WAL parameters of

Re: Application for Ignite Contributor

Hi Deepak and welcome! Sorry for the late response. You sent this message to the user list, forwarded it to the dev list. I added you to the Ignite contributors list in JIRA. Feel free to take over any ticket you like. Do you have any specific interest (SQL, ML, caching, etc.? - Denis On Sat,

Re: Ignite transaction recovery on third-party persistence

SQL APIs are not transactional yet. You need to use key-value calls within Ignite transactions if ACID guarantees are required. SQL will become fully transactional once MVCC becomes ready for the GA release. https://apacheignite.readme.io/docs/multiversion-concurrency-control - Denis On Wed,

Re: Exception during exception handling

Hello Andrey and thanks for reporting! This reminds me of this issue that has a similar stack trace: https://issues.apache.org/jira/browse/IGNITE-12178 Ilya, looks like the root cause is absolutely the same, doesn't it? - Denis On Wed, Sep 25, 2019 at 10:02 AM Andrey Davydov wrote: > In

Exception during exception handling

In ignite 2.7.5 I got following exception: org.apache.ignite.IgniteException: Failed to create string representation of binary object. at org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1022) ~[ignite-core-2.7.5.jar:2.7.5] at

Re: Failed to read magic header (too few bytes received)

Update 2: Digging more in the logging, the issue seems to be: [tcp-disco-ip-finder-cleaner-#5] ERROR org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed to clean IP finder up. class org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the bucket:

Re: Ignite bulk data load issue

Well, yes, that's definitely could be the reason - it's probably not enough. To make initial data load faster, you can either disable WAL for some time or move WAL to the separate disk: https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal Also, you can

Re: Ignite performance - sudden drop after upgrade from 2.3.0

Hello! Please collect profiling (e.g. using JFR) from both runs and search for hot spots in both scenarios. If you find anything suspicious, please file a ticket. We can also look at profiling results for you. Unfortunately I'm not that good with yardstick to run your benchmarks locally. It

Re: Ignite transaction recovery on third-party persistence

Thanks Denis & Ilya! We found an issue if the transaction coordinator exits after successfully committing to the third-party store, but before propagating the commit to the Ignite server nodes in the cluster. We observe two behaviors: 1. *If the committed transaction had insert() statements,

Re: possible ignite bug around binary marshaller and data affinity

Hello! I have trouble contemplating your reproducer, but I think it's related to the fact you are using QueryEntity. QueryEntity means that your annotations are not used. In this case you should use CacheKeyConfiguration to configure affinity for such caches:

Re: How to update QueryEntities property of CacheConfiguration for existing/already created cache

Thanks Pavel for helping,Ok i do go through documentation for cache groups and will check once -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to update QueryEntities property of CacheConfiguration for existing/already created cache

Turns out we can't create multiple tables per cache with SQL DDL, this is a design limitation. The error message is misleading, I'll file a ticket to fix it. So again, I would advise to use one table per cache approach. To reduce the overhead of creating 1000s of caches, you can leverage Cache

Re: How to update QueryEntities property of CacheConfiguration for existing/already created cache

Yes, you are correct, now I see the problem too. Let me investigate it a bit and get back to you. On Wed, Sep 25, 2019 at 10:37 AM siva wrote: > Hi Pavel, > ' > > actually Lecturer table not exists since the cache created with Student > query entity only ,if we try to create another table (lets

Re: nodes are restarting when i try to drop a table created with persistence enabled

I think, the issue is that Ignite can't recover from IgniteOutOfMemory, even by removing data. Shiva, did IgniteOutOfMemory occur for the first time when you did the DROP TABLE, or before that? Denis ср, 25 сент. 2019 г. в 02:30, Denis Magda : > > Shiva, > > Does this issue still exist? Ignite

Re: How to update QueryEntities property of CacheConfiguration for existing/already created cache

Hi Pavel, ' actually Lecturer table not exists since the cache created with Student query entity only ,if we try to create another table (lets say HODepartment) with already created cache also same exception is throwing . Thanks siva -- Sent from:

Re: How to update QueryEntities property of CacheConfiguration for existing/already created cache

Ok, so Lecturer table already exists when you try to create it again. Just run DROP TABLE IF EXISTS Lecturer before trying to create it. On Tue, Sep 24, 2019 at 12:26 PM siva wrote: > Hi Pavel, > > I have attached github link for the reproducer of above exception > > >