Hi All,
I'm getting an error on application startup which has me stumped. I've
imported ignite-core, indexing, slf4j and spring-data via maven, version
2.6.0. I'm using ignite to do some cache operations, basic stuff
cross-node. However when I start it, it runs until the config of static ip
Gordon,
Yes, generally we do recommend using thin client for such applications.
However, it doesn't mean that you can't us client node in case it's really
needed, although it might require some additional tuning.
Would you mind telling if you have any other technology in mind? I highly
doubt
Thanks Val. We are currently using a client node in our desktop gui, but it
performs very poorly when the latency to our server nodes is high. We also have
other problems, such as when new client nodes join, the whole cluster will
pause, which is unacceptable for an end user application. I
Does it work without specifying sessionAffinity?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Gordon,
Ignite thin client uses request-response model, which is not really suitable
for functionality like this. I would never say never, but I think it's very
unlikely that thin client would get any feature that imply pushing updates
from server to client (this includes near caches, any type of
Hi,
Thanks for the response.
I went ahead and implemented a custom indexing SPI. Works like a charm. As
long as Ignite doesn't drop support for the indexing SPI interface this is
exactly what we need.
I'm happy to create Jira issues and extract this into something more
generic for upstream if
Hi,
I'm having an LinkageError in spark trying to read a hive table that has
the external location in IGFS:
java.lang.LinkageError: loader constraint violation: when resolving field
"LOG" the class loader (instance of
org/apache/spark/sql/hive/client/IsolatedClientLoader$$anon$1) of the
referring
Thank you very much for the thorough discussion/explanation and pending fix
for public schemas. Much appreciated !
As an aside, I also contacted QLIK to see if they will fix their product
behavior, which does not seem correct to me either.
--
Sent from:
Hello,
This feature has not been planned yet as far as I know, I didn't manage to
find JIRA's for this, but I think discussion on this feature may be started
on dev list.
Regards
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, trying to install ignite on k8s running on ec2. K8s cluster is running on
EC2 in AWS (not using EKS.)
Following the guide at https://apacheignite.readme.io/docs/stateless-deployment
Getting the following error when trying to create the k8s service:
"unsupported load balancer affinity:
Denis, Konstantin, Thank you for your feedback.
After a private discussion with Ksenia, we've created a new idea of how to
name the event: 'Apache Ignite Day, Workshop: Open Source contribution is
simple'.
It can be slightly better because we don't want competition between
members, just fun and a
Thank you for the answer! It helped.
I discovered two functions that can help in controlling the way ignite the
attributes onto table aliases.
QueryEntity.addQueryField("homeAddress.zip", "java.lang.String", "ha_zip")
would allow programmatically define the "homeAddress.zip" field in the table
Hello!
There's a WAL reader somewhere in the code, it could help if you have
persistence. Note that both invocation and output of this tool is confusing.
It would be nice if you had a reproducer which would show this behavior.
The snippet that you have posted previously isn't very clear on
Hello!
I can see a lot of errors like this one:
[04:05:29,268][INFO][tcp-comm-worker-#1%Server%][ZookeeperDiscoveryImpl]
Created new communication error process future
[errNode=598e3ead-99b8-4c49-b7df-04d578dcbf5f, err=class
org.apache.ignite.IgniteCheckedException: Failed to connect to node (is
Ilya,
Apologies for the slow response..
You are right - this fixed my issue.
Thanks,
Steve
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Great. Thank you for looking into it.
On Mon, Sep 10, 2018, 9:11 PM Maxim.Pudov wrote:
> Hello!
> The answer is yes. It is safe to subscribe to AFTER_NODE_START.
> I've just checked the sequence of events happening during the node startup
> and org.apache.ignite.events.EventType#EVT_NODE_JOINED
Hello!
The answer is yes. It is safe to subscribe to AFTER_NODE_START.
I've just checked the sequence of events happening during the node startup
and org.apache.ignite.events.EventType#EVT_NODE_JOINED happens *before
*org.apache.ignite.lifecycle.LifecycleEventType#AFTER_NODE_START.
With Regards,
I require a record to be present in the ignite database all the time. For
this I have written a function like following:
>
> @PostConstruct
> public void createRecordIfNotPresent() {
> if (entityRepository.findById(1) == null) {
> createRecord()
> }
> }
I have added
Hello,
In case if your nodes don't see each other then try to check next:
1)That your IP finder configuration for every node contains the IP addresses
of every AWS node from the cluster like next:
Ok. Thx for quick answer. January 2019 sounds good.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
For now seems that JDK 11 is not available yet (EAP is not an option).
I think the best hope of full JDK11 support is JDK8 maintenance drop date
(around Jan 2019).
> On 10 Sep 2018, at 16:17, ipsxd wrote:
>
> For now seems that Ignite cannot start with JDK 11, I assume there is a plan
> to
For now seems that Ignite cannot start with JDK 11, I assume there is a plan
to migrate to 11 and if can you specify what the timeline ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I've filed a ticket: [1]
[1] - https://issues.apache.org/jira/browse/IGNITE-9515
Best Regards,
Igor
On Mon, Sep 10, 2018 at 2:56 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Yes, I'm pretty confident that PUBLIC should work without quotes. I'm even
> not sure that it would work even with ordinary
Hello!
Yes, I'm pretty confident that PUBLIC should work without quotes. I'm even
not sure that it would work even with ordinary double quotes set.
Regards,
--
Ilya Kasnacheev
пн, 10 сент. 2018 г. в 14:28, Igor Sapego :
> Ilya,
>
> If we won't bother with quotes, then many other tools will
Ilya,
If we won't bother with quotes, then many other tools will stop working,
as cache-names-schemas MUST be quoted, but they won't be. By the way,
even QLIK will not work with any other schema, except for PUBLIC.
So for now, what I propose is not apply quotes to PUBLIC schema. This is
the only
Hello guys,
I am also facing the similar problem. Does community users have any
solution for this?
This has become blocking issue for me. Can someone please help?
Thanks,
Akash
On Mon, Sep 10, 2018 at 8:33 AM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
> Guys, is there any
Hi Ilya,
Yes growing not so quick but in production we lost near 1GB every day with
15GB of data on each node.
I had simplify data classes by remove annotations and this does not help.
Is it possible debug off-heap memory? How I can understand where memory
goes?
--
Sent from:
Hi,
Is there any plan to support continuous query in the Ignite Thin client.
This would be very useful for us. Without it, we probably have to use some
other technology for serialization and streaming updates to the desktop.
Thanks,
Gordon
This email and any attachments are proprietary &
28 matches
Mail list logo