I also found this while trying to resolve this problem which is still
unresolved.
https://issues.apache.org/jira/browse/IGNITE-5998
Will this be impacted?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, how can we use Ignite to start multiple ignite sessions on a remote
server? I tried using TcpDiscoverySpi and TcpCommunicationSpi to resolve
this problem, but this was not working. I basically used a similar setting
as below from ignite website. And I have already added jar under ignite/lib
Hi, does anyone have a solution to the problem I am having right now? thanks
in advance. I really need an input for this problem.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, can I get an update on this? I am just wondering how I should approach
this problem. Thanks again!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Him first of all, thank you very much for your quick response!
Just wondering, in that case, is there any scheduling job within Ignite that
removes the cache itself after the records are removed due to expiry policy,
so that when I call ignite.cacheNames() we know that it is removed? Thanks
Hi, first of all, thank you very much for your quick response!
My case is that on the PCF server, once I execute the ignite against the 1.0
million records, my memory usage displayed by the PCF server increase by
200MB. After I execute the destroy cache function (just like I posted in my
above
Ignite Cache Expiry policy does not remove the cache from cache lists. I have
set it to 2 hrs, but after 2hours, the records seems to have been removed,
but not the entire cache, as I could find that cache name when I call
ignite.cacheNames(); I was basically using the same example from
Hi, I am basically starting Ignite node through my Java project. When I run
the above specified code, I first run the ignite.sh from my remote server as
well.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, this is basically the command that I am using to clear and destroy the
cache from the server that is deployed on the PCF server.
But memory does not free, even after I do this.
private clearCacheByName(String item) {
if (ignite.cacheNames().contains(item)) {
Hi, first of all, thanks once again, I have tried your approach (after
uploading new jar to lib folder as a new class was introduced), but I am
getting a below error. FYI, "ignite-cass-delta" is the name of the default
cache name I am using. Thanks again!
[11:36:25] Topology snapshot [ver=9,
Ok, thanks again. I will try it today and let you know the result. Just
wondering, can I know why we are creating a custom
CassandraCacheStoreFactory? Thanks in advance.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, caheName.loadCache(null, "select * from sampledata") is not returning a
correct number of records every time, the record is fetched from Cassandra
table.
My code generally looks like this;
caheName.loadCache(null, "select * from sampledata")
SqlFieldsQuery sqlQuery = new
Hi, so I have provided my code structures, just in case my POJOExample.java
looks as below; this is used for key-value setting for persistence setting
for Cassandra. Thanks once again!
POJOExample.java
public class POJOExample implements Serializable{
@QuerySqlField(index=true,
Hi, so I have provided my code structures, just in case my POJOExample.java
looks as below; this is used for key-value setting for persistence setting
for Cassandra. Thanks once again!
POJOExample.java
public class POJOExample implements Serializable{
@QuerySqlField(index=true,
Thanks in advance. (This may be duplicate, as I forgot to put few other
details. )
I am basically using the sample xml provided for Ignite
TcpDiscoveryVmIpFinder, but with Cassandra third party persistence.
public Ignite startIgnite {
IgniteConfiguration cfg = new IgniteConfiguration();
How can I use Ignite cluster with remote servers?
Currently, I am getting a below error. FYI, I have already configured my
TcpDiscoveryVmIpFinder and TcpCommunicationSpi correctly, but for some
reason, it is pointing at 10.209.236.58 which is from localhost, and thus
the server is not able to
16 matches
Mail list logo