Hi,
I would like to add below points :
1) Ignite YARN is started once [Server] and it will not be stopped between
iterations. This means that only once the Ignite nodes are negotiated
between YARN and Ignite. Once finalized this should be the same.
Please find below the server logs.
[12:30:46]
Hi,
Looks like logs from the server is still not full. If you've checked them
and you sure that you don't have any exceptions in it before witnessing this
problem, then, I think that you could have some connection problems or a
long GC pause. Do you have any network monitoring? Also, I would
Hi Guys,
If i set back up count to 3 and rebalncing mode to None , do you think
there are any issues? I want to avoid the rebalncing of data when a node
crashes and a new one joins which is slowing down loading the data to
cache.
Thanks,
Ranjit
Hi,
1) Load data to cache
var cacheConf: CacheConfiguration[Long, Data] = new
CacheConfiguration[Long, Data]("DataCache")
cacheConf.setCacheMode(CacheMode.PARTITIONED)
cacheConf.setIndexedTypes(classOf[Long], classOf[Data])
val cache = ignite.getOrCreateCache(cacheConf)
var dataMap =
Hello!
Sorry that I didn't answer earlier. Took some courage.
> int getPerNodeBatchSize()
Internally, IGFS uses DataStreamer. This is DataStreamer's
perNodeBufferSize() that is called when it is created.
> int getPerNodeParallelBatchCount()
Ditto. It is perNodeParallelOperations().
So, remote
I can see two options here:
- Between iteration 1 and iteration 2 some nodes were stopped. Perhaps some
new nodes were started. Data on stopped nodes became unavailab.e
- Cache key collisions between iterations 1 and 2 so that 80% keys are
identical and only 20% are distinct the second time.
I
Hello!
I don't think that anything will get evicted with the configuration that
you have provided.
I think you should check whether keys are really unique (yes I remember
that you include currentTimeMillis in them, still it makes sense to
double-check) and also that all values are of type Data.
Hi, Evgenii
Thank you for your reply.
The logs files are too big and same mostly, so collect the logs at the
moment of connection.
Because clients cannot connect to cluster any more and always show these
error messages when we try to connect them again, I don't think it's the
problem of that
Hi,
Do you understand that in this case rebalance won't happen automatically at
all and you will need to make it manually?
Evgenii
2018-01-30 18:16 GMT+03:00 Ranjit Sahu :
> Hi Guys,
>
> If i set back up count to 3 and rebalncing mode to None , do you think
> there are
I am testing IndexingSpi in cluster of 2 nodes for the the following cache
config:
private IgniteCache createCache() {
CacheConfiguration cCfg = new
CacheConfiguration<>();
cCfg.setName("MyCache");
cCfg.setStoreKeepBinary(true);
I am also experiencing this issue. I'm running ignite in a kubernetes cluster
and I am trying to do a rolling update. so I have 2 ignite nodes running and
I am using K8's rolling update api in a deployment. eg. I am running an
application that starts up the 2 nodes. the nodes cluster and I then
Apache Ignite community applied security patches against the notorious Meltdown
Spectre vulnerabilities and completed performance testing of general operations
and workloads that are typical for Ignite deployments.
The details are under the link:
Hi,
I'm encountering an issue when I start an ignite client inside a spring boot
app (with hate-aos).
It seems as if there are classloader or marshalling conflicts between both
frameworks.
Can anyone confirm (or even better: a clue on how to solve this?):
--
Sent from:
Hi,
1. How do you load data to cache? Is it possible keys have duplicates?
2. How did you check there are 120k records in cache? Is it whole cache
metric or node local metric?
3. Are there any error in logs?
On Tue, Jan 30, 2018 at 3:17 PM, Raghav wrote:
> Hello,
>
> Am
Hi Thomas,
Let's start with the table (I will use java api for that)
// Create dummy cache to act as an entry point for SQL queries (new
SQL API which do not require this
// will appear in future versions, JDBC and ODBC drivers do not
require it already).
CacheConfiguration cacheCfg = new
Update:
Not quite sure if this is the problem but the issue is with client nodes.
I have peer class loading disabled and the client is also logging unknown
classes of Ignite lifecyclebeans which are present on server nodes (but
definitely NOT on client nodes).
This behaviour seems really awkward
Hi Pim,
Can you please provide more details on your issue?
1. What is the issue and what is the expected behavior?
2. Server and client configurations
3. It would be nice to have a small reproducer for better understanding.
Thanks,
Amir
On Tue, Jan 30, 2018 at 2:19 PM, Pim D
Hi
I'm wondering if there is a way to get TTL of specific (K,V) entry,
something similar to Redis TTL:
https://redis.io/commands/ttl
Thank you
Ariel
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
To add a detail, value will have an index created for it if it is a primitive
(or an “SQL-friendly” type like Date).
I don’t think there is an easy way to avoid that. You could use a wrapper for
the primitive value, but it will also
have some overhead and it’s hard to say whether it will be
Looks like you have a node filter in cache configuration and using lambda to
provide it. I would recommend to create a static class instead, deploy it on
all nodes in topology (both clients and servers) and then restart. Most
likely the issue will go away.
-Val
--
Sent from:
Umur,
No, it doesn't use shared memory and I doubt what you tell is even possible.
However, I still not sure I understand what is the purpose of all this. What
is your ultimate goal here?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ariel,
There is no way to do this with the current API. What is the use case for
this?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ranjit,
Is it a really frequent event for node to crash in the middle of loading
process? If so, then I think you should fix that instead of working around
by disabling rebalancing. Such configuration definitely has a lot drawbacks
and therefore can cause issues.
-Val
--
Sent from:
No worries, the value is a hashmap that store some configuration and I
just use index on the key to get the stuff out of there so should not be
a problem.
Mikael
Den 2018-01-30 kl. 10:19, skrev Stanislav Lukyanov:
To add a detail, value will have an index created for it if it is a
Hello!
Can you please also provide full cache configuration and your hardware specs
(especially for storage)?
After 2.4 release is done, I hope your case will get attention of PDS
developers.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Svonn,
So, the issue is related to Kafka configuration. Am I right?
If you think that something should be done on Ignite side, please share a
small reproducer.
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
26 matches
Mail list logo