Hello.
There is difficult transaction in my system, requires to put about 50 objects
to 7 different ignite caches. Objects have 7 different classes. Some of them
have difficult internal structure with object and collection fileds.
The first execution of this transaction after empty cluster
, it will work
like pre-defined types.
Evgenii
вт, 2 окт. 2018 г. в 14:58, Andrey Davydov :
Hello.
There is difficult transaction in my system, requires to put about 50 objects
to 7 different ignite caches. Objects have 7 different classes. Some of them
have difficult internal structure with object
nicate via network freely and without delay?
Regards,
--
Ilya Kasnacheev
вт, 15 янв. 2019 г. в 20:12, Andrey Davydov :
Hello,
You can find full log there:
https://drive.google.com/file/d/1FwCjsXMw5LQJnKO0x5GNJ2w9gVsDbXlc/view?usp=sharing
I can rerun tests with additional logging settings
by condition on slow IO. Initialy I got problem when I build my
project on external drive.
Andrey.
On Wed, Jan 9, 2019 at 8:43 PM Andrey Davydov
wrote:
>
>
> Hello,
>
> I found in test logs of my project that Ignite warns about failed
> partition maps exchange. In test enviro
the full verbose log somewhere?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 9 янв. 2019 г. в 20:43, Andrey Davydov :
>
>>
>>
>> Hello,
>>
>> I found in test logs of my project that Ignite warns about failed
>> partition maps exchange.
ges which will then go away. This is by design.
> Nevertheless I will try to run your reproducer.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 16 янв. 2019 г. в 21:28, Andrey Davydov :
>>
>> I create small reproducer project/ It is available on:
>>
https://dr
Hello all,
The first write transaction on empty cluster with persistence enabled takes
some seconds. After that, cluster works fast. It seems it is because of WAL
file creation and so on. But I can’t setup real transaction timeout in
configuration, because it cause exception on the first
I’ve got strange exception after update my project from 2.6 to 2.7. It happens
when I run DELETE SQL query on empty cache. Smt like this "DELETE FROM
EventNode WHERE processTimeStamp < ? ".
Class definitions:
public class EventNode {
@QuerySqlField(index = true)
private MlEvent
Hello,
When I update Ignite from 2.6 to 2.7, I have to update Spring to
corresponding version too (from 4.16 to 4.18). And I got some exceptions on
application stop (org.apache.ignite.internal.IgniteInterruptedCheckedExcept
ion on backplane scheduled queries).
As I find with debugger, in
Hello,
When 2.7 release will be available? We have some problems with
https://issues.apache.org/jira/browse/IGNITE-7972 in CI process of our system
(test runner server is not powerful enough and we get NPE from Ignite on every
third build attempt =((( )
Andrey.
Thanks
Andrey.
От: Maxim.Pudov
Отправлено: 26 ноября 2018 г. в 12:56
Кому: user@ignite.apache.org
Тема: Re: Ignite 2.7
It is up to community to decide.
You can track the progress here:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-Last-Mile-td36359i40.html
I think it
Hello,
I found in test logs of my project that Ignite warns about failed partition
maps exchange. In test environment 3 Ignite 2.7 server nodes run in the same
JVM8 on Win10, using localhost networking.
2019-01-09 20:15:27,719 [sys-#164%TestNode-2%] INFO
Hello all,
Sometimes we get very strange ignite cluster crush during execution of tests
for our system.
2019-07-09 11:02:59,710 [main] ERROR com.imperva.ddc.core.Driver:176 - Ldap
Connection to nodelegateddomen.local failed
2019-07-09 11:02:59,715 [main] ERROR com.imperva.ddc.core.Driver:116
catch (CacheException e) {
> assert e.getCause() instanceof TransactionTimeoutException;
> }
>
> So could you please provide the reproducer for your issue? We will check
> it and create the JIRA for it.
>
> BR,
> Andrei
>
> 8/9/2019 5:16 PM, Andrey D
On ignite 2.7.5 I got TransactionTimeoutException not wrapped
in CacheException. If it is normal behaviour and I should catch
TransactionTimeoutException too. My current logic is to
catch CacheException and check CacheException.getCause() if it
was TransactionTimeoutException.
Thanks.
Full
and example on
https://apacheignite.readme.io/docs/transactions
On Fri, Aug 9, 2019 at 6:12 PM Andrey Davydov
wrote:
> Sorry fo misprint, test does not check that there are no any way to get
> TimeoutException
>
> On Fri, Aug 9, 2019 at 5:55 PM Andrey Davydov
> wrote:
>
>
PM, Andrey Davydov пишет:
As I see In javadocs for org.apache.ignite.transactions.Transaction
/**
* Commits this transaction by initiating {@code two-phase-commit} process.
*
* @throws IgniteException If commit failed.
* @throws TransactionTimeoutException If transaction is ti
Sorry fo misprint, test does not check that there are no any way to get
TimeoutException
On Fri, Aug 9, 2019 at 5:55 PM Andrey Davydov
wrote:
> It is a little bit difficult to reproduce. We got unhadled exception on
> pre prod performance test of our system. I will try to rep
Hello, Yesterday we got error on node shutdown while test our system: 2019-12-03 18:49:53,653 [pool-228-thread-1] INFO r.s.d.m.c.m.PoisonPill:54 - Poison pill works on e45190a6-de52-4e43-b710-1ee8cd1f60a6 2019-12-03 18:49:53,657 [pool-228-thread-1] INFO r.s.d.m.c.m.ClusterLifecycleBean:61 -
periences the
> exception? It looks like the exception is treated as a failure but
> actually it is not (as it is normal Ignite node stop). I would like to
> understand how critical is it for users.
>
> ср, 4 дек. 2019 г. в 19:25, Andrey Davydov :
> >
> > Hello,
> >
Hello all,
If there is any way to understand how many nodes from baseline topology are
active in TopologyValidator.validate() method?
Thanks.
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
cause is absolutely the same, doesn't it?
-
Denis
On Wed, Sep 25, 2019 at 10:02 AM Andrey Davydov
wrote:
In ignite 2.7.5 I got following exception:
org.apache.ignite.IgniteException: Failed to create string representation of
binary object
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
impossible
Hello, We have Ignite data directory from system with following data region configuration:
I recommend filing an issue about this problem in Apache Ignite JIRA
> because it is obviously unexpected, but I think that your expectations are
> also off.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 27 мар. 2020 г. в 17:06, Andrey Davydov :
>
>>
>>
>> Hello,
for this behavior? Regards,-- Ilya Kasnacheev пт, 20 мар. 2020 г. в 20:20, Andrey Davydov <andrey.davy...@gmail.com>:Hello, Current implementation is really unsafe for multiple Ignite in same JVM.In tests for our system when we stop/start nodes in different order we get following error: Caused by:
, for offheap, for this region, will be used ${config.node.memory.max}.
> Also, don't forget about heap and checkpoint buffer size.
> 3. With enabled pageEvictionMode, data will be evicted from disk too.
>
> Evgenii
>
> вт, 24 мар. 2020 г. в 10:23, Andrey Davydov :
>
>> Hello,
Hello,
org.h2.util.JdbcUtils is utility class with all static methods and
configured via System.properties. So it system wide resource. It is
incorrect inject Ignite specific settings in it.
this - value: org.apache.ignite.internal.IgniteKernal #1
<- grid - class:
Hello, There are at least two way link to IgniteKernal leaks to GC root and makes it unavailable for GC. The first one: this - value: org.apache.ignite.internal.IgniteKernal #1 <- grid - class: org.apache.ignite.internal.GridKernalContextImpl, value: org.apache.ignite.internal.IgniteKernal
-loading, however. Do you bring a new class loader for each test? Can you file an issue about this so that we code a proper de-allocation? Regards,-- Ilya Kasnacheev ср, 18 мар. 2020 г. в 18:37, Andrey Davydov <andrey.davy...@gmail.com>:Hello, There are at least two way link to IgniteKernal
om root class loader and isolated from any Ignite classes. Regards,-- Ilya Kasnacheev ср, 18 мар. 2020 г. в 18:54, Andrey Davydov <andrey.davy...@gmail.com>:Hello, org.h2.util.JdbcUtils is utility class with all static methods and configured via System.properties. So it system wide resour
ated from any Ignite classes. Regards,-- Ilya Kasnacheev ср, 18 мар. 2020 г. в 18:54, Andrey Davydov <andrey.davy...@gmail.com>:Hello, org.h2.util.JdbcUtils is utility class with all static methods and configured via System.properties. So it system wide resource. It is incorrect injec
that implements JavaObjectSerializer.Seems, this won't be released in 2.8https://issues.apache.org/jira/browse/IGNITE-12609 On Thu, Mar 19, 2020 at 4:03 PM Andrey Davydov <andrey.davy...@gmail.com> wrote:Seem that refactor h2serilizer method in following manner will be safe for marshallers
2.opt.GridH2DefaultTableEngine
at java.sql.DriverManager.getConnection(DriverManager.java:689)
at java.sql.DriverManager.getConnection(DriverManager.java:270)
at
org.apache.ignite.internal.processors.query.h2.ConnectionManager.connectionNoCache(ConnectionManager.java:206)
... 51 more
On Thu, Mar 19, 2020 at 6:52 PM Andrey Davydov
l local link, check weak ref
and see heap dump.
Andrey.
*От: *Andrey Davydov
*Отправлено: *18 марта 2020 г. в 18:37
*Кому: *user@ignite.apache.org
*Тема: *Ignite memory leaks in 2.8.0
Hello,
There are at least two way link to IgniteKernal leaks to GC root and makes
it unavailable for G
return testName;
}
public String getIgniteName() {
return name;
}
}
On Fri, Mar 20, 2020 at 11:51 PM Andrey Davydov
wrote:
> I found one more way for leak and understand reason:
>
>
> this - value: org.apache.ignite.internal.IgniteKernal #1
> <- grid - clas
As I see in heapDump: There are 29000+ connections stored here: this - value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1 <- key - class: java.util.concurrent.ConcurrentHashMap$Node, value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1 <-
e done it in GG Community Edition and it works OK.[1]. https://issues.apache.org/jira/browse/IGNITE-12804On 21.03.2020 22:50, Andrey Davydov wrote:A simple diagnostic utility I use to detect these problems: import java.lang.ref.WeakReference;import java.util.ArrayList;import java.util.LinkedList;
It seems detached connection NEVER become attached to thread other it was born. Because borrow method always return object related to caller thread. I.e. all detached connection borned in joined thread are not collectable forewer. So possible reproduce scenario: start separate thread. Run in this
sue to remove mess ThreadLocal logic from
> ConnectionManager. [1]
> We 've done it in GG Community Edition and it works OK.
>
> [1]. https://issues.apache.org/jira/browse/IGNITE-12804
> On 21.03.2020 22:50, Andrey Davydov wrote:
>
> A simple diagnostic utility I u
owner thread is terminated.take a look at the test: H2ConnectionLeaksSelfTest#testConnectionLeaksBut I wrote: thread local logic of connection manager is mess, hard to understand and promising to many troubles.I think we have to change it.On 23.03.2020 23:00, Andrey Davydov wrote:It seems de
Hello, Please help me to setup data region properly. I would like to have region which can store up to ${config.node.total.memory.max} bytes, but only small part of data in RAM. My current config (Ignite 2.7.6):
Hello, It seems that SqlFieldsQuery.setCollocated and SqlFieldsQuery.setDistributedJoins has no affect on subqueries under IN and EXISTS expressions. I didn’t find any information about subqueries specific in actual documentation. Subqueries is important part of sql, please describe it in
Hello, We test migration from 2.7.6 to 2.8.1 in our DEV environment and got problem: new code doesn’t start over old data. Some history:Initially we had following base cache configuration on 2.7.6: id="cache-template" abstract="true"
in a new group, then delete the old conflicting cache. Regards,-- Ilya Kasnacheev чт, 18 июн. 2020 г. в 18:47, Andrey Davydov <andrey.davy...@gmail.com>: Hello, We test migration from 2.7.6 to 2.8.1 in our DEV environment and got problem: new code doesn’t start over old data. Some history:Initially w
Hello, We start test our system on Ignite 2.8.1 and got very strange log. As I understand, It was error in system (on 2.7.6 this test works without any problem, I will investigate it later) and it was NPE during handling of this error: [01:08:11] Configured failure handler:
Yes, I think that initial problem was with communication and it need to be tested more on my side. But during handling this error, Ignite throw NPE, I think that NPE during communication exception handling is bug. [01:08:22] Possible failure suppressed accordingly to a configured handler
48 matches
Mail list logo
