Hi,
I am running a program that connects to a remote spark cluster. I get the
following error. Any insight into the error?
Spark 2.4.4
Scala 2.11.12
Ignite 2.8.1
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.spark.sql.catalyst.expressions.AttributeReference.withQualifier
Hi!
You may get worse performance with a thin client compared to an ordinary
client because as the thin client works through an intermediary node, so
your request will always go to node A in your case and then it will be
handled there, a normal client would go straight to the node where the
d
Hello, I read this page,
https://apacheignite.readme.io/docs/memory-architecture.
and I would like to know what is going to be happen if there are 3 remote
server nodes(A,B,C)
, and cache mode is partitioned and backups 1.
If I wanna get '1' cache data and my application is connected with node A
Hello, I have 4 nodes for server node and I'd like to allocate 4G each node.
but I don't know how to calculate heap size set for each node of percentage.
what percentage is proper for node (JVM -Xmx) if I use only off-heap cache.
Is there any best practice for heap size for node?? or reference li
Thanks Wesley, Alex. Attached is a snapshot of the client log. I don't see
anything on the ignite server side.
I am/was trying to do get data from a replicated cache.
On Tue, Jun 2, 2020 at 10:36 AM Alexandr Shapkin wrote:
> Hi,
>
>
>
> As Wesley mentioned, It’s quite difficult to say something
Hi, thanks for the prompt response
We can have several of these caches, one for each query (is an exceptional
case but, with load, there can be several simultaneously) that is being
executed so we would like to preserve the persistence to take advantage of
the swapping in case the amount of memory
Hi,
Have you tried to put the temp cache into the different, non persisted,
memory region?
You can also try to use a node filter to control what nodes should store
the cache.
On Tue, Jun 2, 2020, 19:24 xero wrote:
> Hi Ignite team, We have a use case where a small portion of the dataset
> mus
Hi Ignite team, We have a use case where a small portion of the dataset must
answer successive queries that could be relatively expensive. For this, we
create a temporary cache with that small subset of the dataset and operate
on that new cache. At the end of the process, that cache is destroyed. T
Server 1 -> Let's say IP is X. Status is running.
Server 2 -> Let's say IP is Y. Status is not running. We stopped this node
for various reasons.
Client1 -> TcpDiscoveryVmIpFinder ipAddress list has two server IPs - X,Y
Client 2 -> TcpDiscoveryVmIpFinder ipAddress list has two server IPs - X,Y
Hello!
I have merged this fix to master.
Regards,
--
Ilya Kasnacheev
ср, 27 мая 2020 г. в 16:14, Ivan Fedorenkov :
> Hello, Ilya!
>
> Yes, there is an existing ticket and I thought that it hasn’t been merged
> yet for a reason. If it was just missed and it should be merged, then
> should I do
Also wanted to mention that there is a working semaphore example available:
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datastructures/IgniteSemaphoreExample.java
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
In an older version there was an issue that caused this condition
https://issues.apache.org/jira/browse/IGNITE-8987
Send a reproducer, mention the version you are using, along with Ignite
logs(from both nodes) and a stack trace of both servers when this condition
occurs.
How to take
Hi, As Wesley mentioned, It’s quite difficult to say something specific about without the logs. As for the additional questions, can you explain, what Ignite API is being used? Is it a Compute API call or a regular cache GETs? It’s totally fine to spawn several user threads and access the server s
Courtney,
This config should be enough
It will load the ML plugin and initialize model storage.
You can send me a reproducer and I'll take a look.
Thanks, Alex
--
Sent from: http://apache-ignite-
It turned out if I inject a pause of 4-5 seconds, then the client
connection goes through.
Why the service grid requests go through immediately but the regular cache
access requires a pause from the time an ignite instance is acquired?
Subsequent calls are fast. The caches are replicated.
Another
Does either client or server have any logs?
Thanks
On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse wrote:
> I'd appreciate your help with this issue.
> I have a server and a client node, the latter running in tomcat. I get
> connection refused if I try to connect to the server node from the client
I'd appreciate your help with this issue.
I have a server and a client node, the latter running in tomcat. I get
connection refused if I try to connect to the server node from the client,
although the server shows the client has joined the cluster. I don't have a
problem running a service on the se
17 matches
Mail list logo