So I was able to get a 2 node cluster started, v2.7.5 and got the web-console
running through a docker container. I’m even able to load the MariaDB JDBC
driver and connect to my database.
The problem I’m having is that when I’m done configuring things and I save and
download the .zip file for
Hi I try it, but it does not work
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
To reproduce, create a sample table using JDBC endpoint:
CREATE TABLE person(Id VARCHAR, birthTime TIMESTAMP, name VARCHAR, PRIMARY
KEY(Id)) WITH "TEMPLATE=templateEternal,CACHE_NAME=person,
KEY_TYPE=personKey,VALUE_TYPE=person";
and configure cache expiry policy as below
Correct.
Which is not to say never do it. But the bigger and more complicated your
application, the more likely you’re going to have problems with embedding.
Regards,
Stephen
> On 13 Jun 2019, at 16:45, Loredana Radulescu Ivanoff
> wrote:
>
> Would it be correct to extrapolate this
Ok, but I can't create dynamically a data region ? Because each time I
receive a new file to process, I create a cachegroup to handle it, then I
clean everything.
Le jeu. 13 juin 2019 à 13:28, Alex Plehanov a
écrit :
> Hello,
>
> It's a known issue [1]. Now you can get cache group size via JMX
Hello!
This is unexpected. Is it possible to create a reproducer project to
reproduce this behavior? Can you share it?
Regards,
--
Ilya Kasnacheev
пт, 7 июн. 2019 г. в 18:37, torjt :
> Hello. Thanks for the response. The operation returns with 0 values.
> There
> is no Zookeeper being used
Hello!
You know, there's an even simpler method of authentication. Just use TLS,
have a CA which only signs certificates of trusted nodes. Anyone without a
certificate can't join cluster.
Regards,
--
Ilya Kasnacheev
ср, 12 июн. 2019 г. в 11:09, Jeff Jiao :
> I tried to implement the plugin
Would it be correct to extrapolate this statement and say that Ignite
should be started as a standalone application as opposed to being embedded
inside an application server that has its own lifecycle and additional
responsibilities?
On Thu, Jun 13, 2019 at 7:48 AM Stephen Darlington <
The documentation recommends against using embedded mode for what’s likely to
be a related reason.
Embedded mode implies starting Ignite server nodes within Spark executors which
can cause unexpected rebalancing or even data loss. Therefore this mode is
currently deprecated and will be
Hi,
> we have noticed that Ignite nodes are not responding in the heart beat
interval time and hence the re-balancing of data is happening and followed
by query cancellation.
It looks like a long GC pauses for me. Can you share full logs from all the
nodes? As the fast workaround, I can suggest
Hello!
Please enable verbose logging and share logs from both visor, client and
server nodes, so that we could check that.
There should be messages related to connection attempts.
Regards,
--
Ilya Kasnacheev
чт, 13 июн. 2019 г. в 00:06, John Smith :
> The clients are in the same low latency
Hi,
We are using Apache Ignite in embedded mode to store data in key value pairs
and query the data.
Sometimes, the spark jobs run for really long time than expected and in
those scenarios we have noticed that Ignite nodes are not responding in the
heart beat interval time and hence the
Hello,
It's a known issue [1]. Now you can get cache group size via JMX only if
persistence is used.
If persistence is not used you can get allocated size only for data region
(but you can have more then one data region and assign cache groups to data
regions any way you want)
[1] :
@akurbanov, Its being started by shell script, it runs as an application
inside docker.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
What is the exact Ignite version that you are using, steps to reproduce this
(what is the job, what operations Ignite is doing)?
Also please provide the log file for the node that sees the exception.
I can only suggest that exception is thrown from
GridDiscoveryManager.resolveDiscoCache, and
Hi!
You can use a scan query, that will iterate over the whole dataset and
bring it to memory. You don't need to perform any specific processing. Just
touching it is enough for it to appear in memory.
In version 2.8 there will be a new API, allowing preloading partitions.
Could you please try starting your java applications with
-Dfile.encoding=UTF-8 and check if it works?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
How do you start your nodes? Using a shell script or just as an application?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
You can have only a single instance of collision SPI in the configuration,
but this one is pluggable, you can have your own implementation, have the
implementation class deployed in the cluster and set it in the configuration
via
Hi All,
We wants to use a segmentation policy in a way, that with network
segmentation the jvm process should stop. The standard policy I found in
ignite is RESTART/STOP/NOOP(default), here the stop policy is only stopping
the node, not the JVM.
Is there any policy/way to stop the JVM on network
Hi All,
I want to use Composite CollisionSpi, which does PriorityQueueCollisionSpi
first and the apply JobStealingCollisionSpi. Is there an existing way to
support such case in Ignite.
Thanks,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
21 matches
Mail list logo
