Thanks Pavel!
Does the priority on the Jira ticket suggest this will target IA 2.8?
Thanks,
Raymond.
On Wed, Jul 24, 2019 at 8:21 PM Pavel Tupitsyn wrote:
> Denis, yes, looks like a simple thing to add.
>
> On Tue, Jul 23, 2019 at 10:38 PM Denis Magda wrote:
>
>> Looping in the dev list.
>>
This message means that you are trying to start two ignite instances in
the same JVM with the same
igniteInstanceName in your configuration.
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setIgniteInstanceName-java.lang.String-
I am trying to reference a cache from within a CacheInterceptorAdapter
(onAfterPut method) to invoke an entry processor to another cache after a
put.
How to get a refrence to a cache?
I tried the followings:
Ignite ignite = Ignition.start("default-config.xml");
IgniteCache cache =
Hello, I plan on using an Ignite node topology as follows:
1) Application configured as an Ignite Client that handles distributing
requests to the correct server node.
2) 3+ Partitioned Server nodes that handle cache storage and processing of
requests.
3) Each server node has two caches which use
Hi,
I've tried to reproduce the issue by using your examples with Ignite 2.7.5
and seems like it works correctly for me.
On node start I see next information regarding log level:
log4j: Level value for root is [INFO].
log4j: root level set to INFO
Did you specify IGNITE_HOME property in your
Hello Simon,
Can you, please, share a full log? There should be an internal Java exception
with that message.
It would be perfect if you can share a little reproducer as well.
From: simonatelier
Sent: Thursday, July 25, 2019 3:20 PM
To: user@ignite.apache.org
Subject: Ignite .NET 2.7.5 -
Hi there
We have a Client node-Server node setup where the Client node is running a
RemoteQuery on the cluster for CacheEvents.
When the IEventFilter runs for the RemoteQuery it returns true
but once that happens, the following error is raised in the Ignite logs:
Failed to unmarshal events
IGNITE_DISCOVERY_HISTORY_SIZE=700
Does this go on the server side or the thick client side ?
Hi Mahesh,
It definitely looks like a bug. I have created this ticket in order to
track the issue https://issues.apache.org/jira/browse/IGNITE-12013
As a temporary workaround, I would propose increasing discovery history size
Denis, I've just created one:
https://issues.apache.org/jira/browse/IGNITE-12012
Thanks
On Thu, Jul 25, 2019 at 2:25 AM Denis Magda wrote:
> Pavel,
>
> Do we already have a ticket or do you want me to create one?
>
> -
> Denis
>
>
> On Wed, Jul 24, 2019 at 1:21 AM Pavel Tupitsyn
> wrote:
>
>
10 matches
Mail list logo
