Hi Stan
The result will be the same without transaction, even with atomic mode. So
wondering if there is other reason capped the performance. Attach is our POC
source code which give around 1700 TPS, with or without transaction, may be you
can advise what's wrong with it.
Hello,
I am trying to run Apache ignite : 2.5.0 inside the kubernetes cluster. My
organization security policy doesn't allow to run as 'root' inside any
container. I tried to add security context (runAsNonRoot) in kubernetes
yaml file. I am always getting the following error.
cp: can't create
First, 1700 TPS given your transaction structure is 17 simple
operations per second, which is quite substantial - especially if you're
doing that from a single thread / single ODBC client.
Second, note that TRANSACTIONAL_SNAPSHOT is in beta and is not ready for
production use. There are no
This message actually looks worrisome:
2019-10-22 10:31:42,441][WARN
][data-streamer-stripe-3-#52][PageMemoryImpl] Parking
thread=data-streamer-stripe-3-#52 for timeout (ms)=771038
It means that Ignite's throttling algorithm has decided to put a thread to
sleep for 771 seconds.
Can you share
Hi,
Web Console requires ignite-rest-http module to be enabled. It is not
enabled by default in Ignite binaries nor Docker image.
The steps that you've taken are done while the container is running - so,
AFTER the Ignite process has started. That's why copying the module has no
effect.
Try
There are multiple ways to configure a cache to use SQL. The easiest is to
use @QuerySqlField annotation. Check out this doc
https://www.gridgain.com/docs/8.7.6/developers-guide/SQL/sql-api#querysqlfield-annotation
.
On Tue, Nov 5, 2019 at 5:52 PM BorisBelozerov
wrote:
> I have 3 nodes, and I
Hello, please make sure Ignite is allowed through the firewall, ports:
47500~47600 for discovery, 47100~47200 for communication
On Tue, Nov 5, 2019 at 9:26 PM Manan Joshi wrote:
> Hello Ignite Comunity,
>
>
>
> We are trying to use apache ignite as our distributed caching solution and
> we
Hello Ignite Comunity,
We are trying to use apache ignite as our distributed caching solution and
we want to have clustering of ignite nodes into distributed environment. So
far we know that nodes are discovered automatically on single machine but
when we run two instance in different machines
We are using Ignite as a Distributed In-Memory cache, deployed using YARN on a
Hadoop Cluster. We have configured Zookeeper Discovery, and this is working
fine.
Given this is a small 20 node Ignite cluster, Zookeeper Discovery seems
overkill. Would it be possible to switch to TCP Discovery?
We are trying to ...
1. Use the G1 garbage collector for smaller stop-the-world GC pauses.
2. Obtain verbose logs from Ignite for troubleshooting purposes
We have tried setting IGNITE_JVM_OPTS="-DIGNITE_QUIET=false -XX:+UseG1GC", but
the JVM options are not taking effect on the Server
Hi Igniters!
I’ve been working on the Service Grid functionality in Apache Ignite for a
while, and at some point I've decided to make a webinar with a high-level
overview of this part of the project.
If you want to learn more about services, look at some use-cases or just ask a
few questions
Hi Hemambara,
Check my example [1].
1. Launch step1.
2. Uncomment code and enable Address.number field.
3. Launch step2.
Actually the problem here is type mismatch for "number" int vs
varchar. Work with nested fields could be really tricky. Subsequently
there is not much activity to improve
Hi, Wellington
I'll be happy to help you if you give me more information of your goal.
I have a few questions, could you answer please?
1. What's your main goal? To solve optimization task on the data in Ignite
or in Spark?
2. What's the average size of initial population?
3. Did you run these
Thank you!!
How many nodes that I run your code??
I only run the "CREATE database" code in one node or all nodes??
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Okay, so the issue you are facing with is incorrect data type which is valid,
so its not an issue then.
Yes agreed that it requires more testing, but I feel the fix that is going
in, is safe and good to do. This fix is really important for us to proceed
further. I have tested few other scnearios
Hi Hemambara,
You can a write an email to d...@ignite.apache.org with reference to
the issue and a description of the fix. It might be that someone will
be ready to do a review and merge.
вт, 5 нояб. 2019 г. в 15:57, Hemambara :
>
> Okay, so the issue you are facing with is incorrect data type
Hi,
1. What's your main goal?
We need to run Genetic Algorithms in parallel to return the best
execution plan for a factory production line.
To solve optimization task on the data in Ignite or in Spark?
As I have little experience, I'm evaluating the best architecture we
can be
Hi,
I am currently researching an architecture on AWS - Elastic MapReduce (EMR)
to run Genetic Algorithms (GA).
Apache Ignite already has some genetic algorithms (GA) defined, so we would
like to do some testing with it integrated with Apache Spark.
But I found little material on how to
Hi Kurt,
It might be that you faced https://issues.apache.org/jira/browse/IGNITE-12068
Was fixed in 2.7.6
пн, 21 окт. 2019 г. в 17:56, Denis Mekhanikov :
>
> Kurt,
>
> I tried reproducing this issue using your data, but I didn’t manage to make
> the query for id return only one entry.
>
> What
I believe that the correct answer to your question - don't do that.
The strength of distributed systems is that you have a number of identical
pieces which you can scale out virtually with no limits.
If your cluster is heterogenous - i.e. all the nodes are different in size,
amount of data and
Each node is supposed to add its own IP and port to the S3 bucket when it
starts. That said, I wouldn't check the cluster state based on the contents
of the bucket alone.
Check your logs for errors. Try using some tools (e.g. check out Web
Console - either the one in Ignite
val cacheConfiguration = new CacheConfiguration[Integer,DataX]()
val valQE = new QueryEntity()
valQE.setKeyFieldName("key")
valQE.setKeyType("java.lang.Integer")
valQE.setValueType("DataX")
valQE.addQueryField("key", "java.lang.Integer", "key")
One. The cache is cluster-wide, so once it’s created every node can see it.
> On 5 Nov 2019, at 12:36, BorisBelozerov wrote:
>
> Thank you!!
> How many nodes that I run your code??
> I only run the "CREATE database" code in one node or all nodes??
>
>
>
> --
> Sent from:
Hello!
I think I saw one here:
https://bitbucket.org/lokesh_blue/bugdemo/src/master/
Regards,
--
Ilya Kasnacheev
ср, 30 окт. 2019 г. в 21:34, niamin :
> Can you share a pom.xml that includes the dependencies that have been
> tested
> and known to work with Spring Data? I used spring-data-2.0
Hello!
I don't think so, since we don't use clock for anything critical.
Regards,
--
Ilya Kasnacheev
пн, 4 нояб. 2019 г. в 14:49, Shiva Kumar :
> Hi all,
>
> I wanted to know if Leap Day 29.02.2020 has any impact on Apache Ignite?
>
> best regards,
> shiva
>
Hello!
Please try the following dependency:
org.springframework.data
spring-data-commons
2.0.9.RELEASE
org.slf4j
jcl-over-slf4j
It seems that they have changed API in 2.2 (which you get by default) and
we're not compatible
I have 3 nodes, and I code in each node:
The 1st node: in Main function
Ignite ignite=Ignition.start();
CacheConfiguration cacheConfiguration = new
CacheConfiguration();
QueryEntity valQE = new QueryEntity();
27 matches
Mail list logo
