Hi,
I have a cluster of 10 nodes, and a cache with replication factor 3 and no persistency enabled.
The SQL query is pretty simple -- "SELECT * FROM Logs ORDER by time DESC LIMIT 100".
I have checked the index for "time" attribute is applied.
When I increase the number of nodes,
Hi Roman,
Thanks for the information. I was able to get ignite working with RBAC
enabled K8s cluster.
The issue was with K8s calico networking, I had set it up wrongly because of
which I was getting errors.
Regards,
Vishwas
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Very strange. By default, there is no any timeout. I will take a look more
carefully.
Also is it possible that you cancel the closure somehow?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
> So when we need to add a new field, say in "addr", we can use current
> ALTER TABLE to add a normal column,
> but now the problem is how to map the new field to the column.
Yes, that is a problem. ALTER TABLE command does not support adding new
columns to nested objects.
So, if you need
Hi,
Now in case of the node was left the BLT cluster will wait for it. In case
if it can't return for a long time user should manually remove it from BTL
and it will do rebalance like in this example:
Some of the code is proprietary, but this is the exception. No, I have not
set a manual timeout
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Monitor.ObjWait(Boolean exitContext, Int32
millisecondsTimeout, Object obj)
at
Hi,
Could you please provide some more details: cache configuration, an example
of code that was failed and logs?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Could you please provide the exception?
As I see from the code if you didn't set some timeout manual using
writeTimeout method then Long.MAX_VALUE should be used.
Long timeout = (Long)map.get(TC_TIMEOUT);
long timeout0 = timeout == null || timeout == 0 ? Long.MAX_VALUE :
Hi Dmitry,
We are again seeing segmentation failure in one of the node of our prod env.
This time we did not run jmap, but still node failed.
-> CPU, memory utilization and network are in optimal state.
We observed that there are page faults in memory at the same time of
segmentation failure,
Hi all
Is there a timeout implied or otherwise with Apply() method for a
Distributed closure? Seems to kick out a exception after roughly two mins.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Dennis,
Would you please consider writing a blog post on 'Ignite + kubernetes' for
us folks who are not in NY? Also if you can record this session and post
links later, it would be very useful.
Thanks,
Arun
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
"When receiver is invoked for key K, it’s holding the lock for K." is not
correct, at least in the 2.4 code.
When a custom stream receiver is called, the data streamer thread has a
read-lock preventing termination, and there is a real-lock on the topology,
but DataStreamerUpdateJob.call() does
Hi,
In case dial timeout, client is nil so that client.Close() can't work.
Thanks.
Using Ignite 2.4 for Hibernate query cache and getting an exception:
Caused by: java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast
to [Ljava.io.Serializable;
at
org.hibernate.cache.internal.StandardQueryCache.get(StandardQueryCache.java:189)
at
Hi,
It is recommended to set baseline at first if grid was upgraded from <2.4
version.
Then you need to deactivate the grid to force checkpoint, this can reduce
time of next startup.
Then stop grid and update jars to newer version and start the grid.
Then you may be need to activate grid if it
ok, thanks
So where i can find information about migration procedure?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
It should not be possible by default and highly not recommended.
As there can be differences in communication protocol between versions ans
compatibility is not tested.
However, persistence format should be backward compatible that means Ignite
newer version can work with persistence created
Hi,
Thank you for attaching the code sample and configration. Most likely this
information will be enough to reproduce the issue.
Meanwhile could you please try to add `defer client.Close()` into your code:
func main() {
client, err := redis.DialTimeout("tcp", "10.1.14.221:11211", 500 *
Hi ppl!
I have cluser of 5 nodes ignite 2.4.
Is it possible to add new nodes with 2.5 version to it?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Sorry I have no knowledge about maven.
Here is my config file and sample code of the client.
I reproduced "Connection reset by peer" by adjust the timeout setting,
but ignite's file descriptor count didn't increase.
Before ignite was halted by "Too many open files", there was a close
wait
Hi,
I checked the logs and it saw there are a lot of "Connection reset by peer"
exceptions there which can be a cause of "Too many open files".
It seems that the clients connect to Ignite server node via REST API. Could
you please share a small reproducer (maven project at github) and server
21 matches
Mail list logo