Hi! It's a good question and note about integration.
We have no this integration on roadmap, but I agree, that we have no good
'workbench environment'.
But should it be a kind of destop workbench or something else? I don't know.
I don't any examples of integration with the Weka for another distrib
Yeah, it is hard to say anything on above. What else do you need? Will
provide you the information.
Just wanted to understand what happened here.
BR,
Ashish
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi getting allot of these messages. It seems to be coming from a single
client. The client was restarted briefly because of updates...
The client is an apache flink streaming job.
[21:38:12,775][INFO][grid-nio-worker-tcp-comm-1-#25%xx%][TcpCommunicationSpi]
Accepted incoming communication con
Please attach all the thread dumps and log files for the investigation.
-
Denis
On Wed, Feb 5, 2020 at 8:03 AM pg31 wrote:
> Hi
>
> Cluster Configuration:
> 3 Nodes (112 GB Memory / 512 GB Disk)
>
> Ignite Configuration:
> 1. Persistence Enabled
> 2. Version: 2.6.0
> 3. Configuration is as fol
We have recently encountered the following:
Caused by: org.apache.ignite.spi.IgniteSpiException: BaselineTopology of
joining node (404d8988-6c2d-4612-ab17-fde635b9da8f) is not compatible with
BaselineTopology in the cluster.
Branching history of cluster BlT ([-205608975, 383765073, 1797002251,
Hello!
Are you sure it does not write to /tmp?
Regards,
--
Ilya Kasnacheev
ср, 5 февр. 2020 г. в 10:15, Mikael :
> Hi!
>
> Well, the message say no space left on device so you are sure the
> persistence/WAL data is stored on the drive where you have 100GB free
> space ? you don't have any use
Hello!
It's hard to say what happens here, AtomicLong definitely did not start
your PESSIMISTIC, REPEATABLE_READ transaction.
More information is needed to be able to understand what's going on here.
Regards,
--
Ilya Kasnacheev
ср, 5 февр. 2020 г. в 08:58, ashishb888 :
> Thank you Ilya. I as
Hi
Cluster Configuration:
3 Nodes (112 GB Memory / 512 GB Disk)
Ignite Configuration:
1. Persistence Enabled
2. Version: 2.6.0
3. Configuration is as follows:
What if you reduce MaxSize to some small number, like 10, does it solve the
problem?
Can you please run jvisualvm and see what happens with the JVM heap?
On Wed, Feb 5, 2020 at 12:28 PM Eduard Llull wrote:
> Hi Pavel,
>
> We have six servers, but these don't have any issue, and 40 client nodes
>
Hi,
Indeed it is a bug. We are already working on it in scope of
https://issues.apache.org/jira/browse/IGNITE-12468
ср, 5 февр. 2020 г. в 11:42, PereTang :
>
> I use the thin java client.
>
>
> I Create a ArrayList and put the Person object into it.
> -
Hi Pavel,
We have six servers, but these don't have any issue, and 40 client nodes
(the Igntie node is started with IgniteConfiguration.ClientMode = true).
The 40 client nodes are the ones where we are having the memory issue.
The _ignite.GetOrCreateNearCache is execute on the client nodes. We a
Hi Eduard,
Do you have any client nodes (IgniteConfiguration.ClientMode=true), or just
servers?
Is the following line executed on Ignite server node?
_ignite.GetOrCreateNearCache
On Wed, Feb 5, 2020 at 11:44 AM Eduard Llull wrote:
> Hi everyone,
>
> We have been using Ignite and Ignite.NET in
Hi everyone,
We have been using Ignite and Ignite.NET in the recent months in a project.
We currently have six Ignite servers (started with ignite.sh) and a bunch
of thick clients split in two .NET Core application deployed in 30 servers.
We store de-normalized data in the Ignite data grid: one o
I use the thin java client.
I Create a ArrayList and put the Person object into it.
--
try (IgniteClient igniteClient = Ignition.startClient(new
ClientConfiguration().setAddresses("127.0.0.1:10800"))) {
final ClientCache> dem
14 matches
Mail list logo
