I am sorry, I am not able to get your question fully. But you should exchange
messages between nodes via topics. It may possible, you sent a message and
no subscriber was there to receive the message.
Can you provide more details on this question?
Thanks
--
Sent from:
Hello experts,
I met an issue on topic based messaging between two Ignite nodes.
I start two nodes one by one.
The first started node send a message, the second node can receive the
message and handle it in the predicate as expected.
you can see the full thread dump in the attarchment,the filename is dump.zip
yu...@toonyoo.net
From: Ilya Kasnacheev
Date: 2019-03-04 16:21
To: user
Subject: Re: Re: TPS does not increase even though new server nodes added
Hello!
Is it a single node dump? Looks like it is idle.
Please
Ignite version: 2.7.0#20181130-sha1:256ae401
Hello!
Can you please share a) approximate hardware and data region config that
you are using, and b) approximate size of your data.
How large is 18 million entries? What's the size of db/ directory at this
point?
Regards,
--
Ilya Kasnacheev
пн, 4 мар. 2019 г. в 17:36, Antonio Conforti :
>
Hello!
I hope that this field will be abandoned in AI 3.0.
Regards,
--
Ilya Kasnacheev
вт, 5 мар. 2019 г. в 19:30, Scott Cote :
> Ilya,
>
>
>
> The “long.class” was a bug-feature (creature feature) that I was trying to
> trap in a unit test.
>
>
>
> My unit test was asserting that the
Ilya,
The “long.class” was a bug-feature (creature feature) that I was trying to trap
in a unit test.
My unit test was asserting that the returned indexTypes would have …
“java.lang.String” as an element in the array, but would fail the assertion
because it would find a “long.class” instead.
Hello.
I have exception on node startup:
java.lang.IllegalMonitorStateException: Attempted to release write lock
while not holding it [lock=7fa721ec8610, state=0001
at
org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
at
Hello!
Recent versions of Ignite will indeed fill QueryEntity and never use
indexedTypes field. QueryEntity and Indexed Types are mutually exclusive
anyway.
Return type is CacheConfiguration for invocations chaining, so that you can
use:
CacheConfiguration cacheConfiguration = *new
All config 2
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:util="http://www.springframework.org/schema/util;
xsi:schemaLocation="
http://www.springframework.org/schema/beans
Thanks Ilya. I guess conceptually there are many explanations and
definitions about those two on Internet which may agree, disagree, or
consensus on some point. My question is more about their impact when they
are true or false in Ignite.
For example, if it's always the case, why doesn't Ignite
Hello!
[12:23:16,734][INFO][grid-nio-worker-tcp-comm-3-#27%StaticGrid27_CommonDev%][TcpCommunicationSpi]
Accepted incoming communication connection [locAddr=/10.201.30.63:9600,
rmtAddr=/10.201.50.40:53366]
[12:24:00,259][INFO][tcp-disco-sock-reader-#368%StaticGrid27_CommonDev%][TcpDiscoverySpi]
Hello!
Can you please provide complete stack trace?
Regards,
--
Ilya Kasnacheev
вт, 5 мар. 2019 г. в 13:48, Arpit Jain :
> Hi,
>
> I am running Ignite in Server mode with my application. I am able to
> insert the first record in the Key/Value Map in Ignite but it fails when I
> try second
Hello!
It is because write-behing is a kind of write-through. Like random access
memory is a kind of computer memory.
Regards,
--
Ilya Kasnacheev
вт, 5 мар. 2019 г. в 14:43, relax ken :
> Hi,
>
> I am new to Ignite. When I enable write behind, I always get a warning
> "Write-behind mode for
Hello!
Is there a chance you were using affinityCall() and you're on Ignite 2.7?
We have a bug which can cause spurious OOMs here:
https://issues.apache.org/jira/browse/IGNITE-10925 - disabling cache
statistics will help
Regards,
--
Ilya Kasnacheev
сб, 2 мар. 2019 г. в 18:13, James Wang 王升平
I use Apache Ignite 2.7.0
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I use Apache Ignite 2.7.0
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Dmitry,
There is a test for WeightedRandomLoadBalancingSpi [1]. It passes on master.
Which version of Ignite do you use? Could you share a reproducer of the
issue so I can have a look?
[1]
Hi,
I am new to Ignite. When I enable write behind, I always get a warning
"Write-behind mode for the cache store also requires
CacheConfiguration.setWriteThrough(true) property." Why does write behind
require write through when I am using write behind only?
Here is my configuration
Hi,
I am running Ignite in Server mode with my application. I am able to insert
the first record in the Key/Value Map in Ignite but it fails when I try
second time. The key is just a Long and value is simple class like this:
class A implements Serializable {
private static final long
Hello!
Have you seen https://apacheignite.readme.io/docs/capacity-planning ?
Do you have any specific issues?
Regards,
--
Ilya Kasnacheev
вт, 5 мар. 2019 г. в 12:25, Navneet Kumar :
> Hi All,
> We are using Cassandra database with very simple table schema which
> consists
> two columns of
Hello!
The preferred approach is to use Thin JDBC client:
https://apacheignite-sql.readme.io/docs/jdbc-driver
Regards,
--
Ilya Kasnacheev
пн, 4 мар. 2019 г. в 19:39, Mike Needham :
> Thanks for the links, If SET STREAMING ON is the preferred method, how
> would you do this in code rather
table schema:
CREATE TABLE `Wa` (
`GameType` smallint(5) unsigned NOT NULL DEFAULT 0
);
ResultSet rs = conn.createStatement().executeQuery("select GameType from
Wa");
ResultSetMetaData resultSetMetaData = rs.getMetaData();
String name=getMetaData.getColumnLabel(1);
The name here is GAMETYPE,
Hi All,
We are using Cassandra database with very simple table schema which consists
two columns of type string and both the columns length is less than 16
characters, first column is Primary Key and all queries/updates performed
using it. This table holds around billion records.
To optimize the
Hi Navneet,
As discussed here is brief information of our use case and observations.
Request your inputs to overcome these
We are using Cassandra database with very simple table schema which consists
two columns of type string and both the columns length is less than 16
characters, first
25 matches
Mail list logo