Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

[mvkarp]

I've attached another set of screenshots, might be more clear.
heap.zip
  


mvkarp wrote
> I've attached some extra screenshots showing what is inside these records
> and path to GC roots. heap.zip
> http://apache-ignite-users.70518.x6.nabble.com/file/t2658/heap.zip;  
> 
> 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

[mvkarp]

I've created ticket, not too sure about how to go about creating a reproducer
for this - https://issues.apache.org/jira/browse/IGNITE-12350

I've attached some extra screenshots showing what is inside these records
and path to GC roots. heap.zip
  





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Service grid webinar

[Scott Cote]

Looking forward to it – Thank you Denis

From: Denis Mekhanikov 
Sent: Tuesday, November 5, 2019 4:00 PM
To: d...@ignite.apache.org; user@ignite.apache.org
Subject: Service grid webinar

Hi Igniters!

I’ve been working on the Service Grid functionality in Apache Ignite for a 
while, and at some point I've decided to make a webinar with a high-level 
overview of this part of the project.

If you want to learn more about services, look at some use-cases or just ask a 
few questions somebody who takes part in the development, please feel free to 
join the presentation on November 6th, at 10 AM PST.

You can sign up by the following link: 
https://www.gridgain.com/resources/webinars/best-practices-microservices-architecture-apache-ignite

Denis

Re: Data is lost during rebalance

[novacean.alex]

This is the test i am performing:

1. I have an Ignite Cluster of 3 Server Nodes running in Kubernetes. (the
cluster is created using a StatefulSet)
2. Once the cluster is up i use a Deployment to run 5 pods each with a
Client Node that performs put operations on my cache.
3. Once i see in the logs "Page-based evictions started. Consider increasing
'maxSize' on Data Region configuration: default" on all 3 Server Nodes i
delete the deployment, thus stopping the put opperations.
4. Once the deployment is deleted i restart node-2 from the cluster and once
it is up again i wait for it to finish rebalancing.
5. The result of the test so far is that entries are missing from node-2
after the rebalance is complete.

Log Files before the restart:
node-0.log
  
node-1.log
  
node-2.log
  

Log Files after the restart:

node-0.log
  
node-1.log
  
node-2.log
  

I want to use the cluster to store web-session and i have ~400 request per
second of cahe read and put operation.
Would disabling the page eviction for the default data region end up and
getting OOM Exceptions?
If no, i will try and disable it as you suggested and perform more tests.

Thanks,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Data is lost during rebalance

[Вячеслав Коптилин]

We are definitely missing something obvious. )))

1. Let's check log files for the following message: "Page-based evictions
started. Consider increasing 'maxSize' on Data Region configuration:"
2. Please try to disable page eviction for the default data region.
3. Could you please describe your test scenario in detail and attach log
files from all nodes.

Thanks,
S.

ср, 6 нояб. 2019 г. в 15:48, novacean.alex :

> Hello Slava,
>
> Apparently i celebrated to early. The first test i performed after i used
> the 'backup' cache property in the config it was a success indeed, but the
> test was performed with a half full cache. When performing the test with
> the
> cache full the results are the same as previously, entries missing after re
> balance.
>
> The code snipped you provided returned : REPLICATED. And in visor i also
> had
> this which i missed to share earlier:
> 
>
> Thank you,
> Alex Novacean.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: apache ignite installation fails in kubernetes

[Andrei Aleksandrov]

Hi,

As I know it should be fixed in Apache Ignite 2.7.6. Also as an option 
you can try to modify your current Docker file as next (master version):


https://github.com/apache/ignite/blob/master/docker/apache-ignite/Dockerfile 



BR,
Andrei

11/6/2019 10:33 AM, Gokulnath Chidambaram пишет:

Hello,

I am trying to run Apache ignite : 2.5.0 inside the kubernetes 
cluster. My organization security policy doesn't allow to run as 
'root' inside any container. I tried to add security context 
(runAsNonRoot) in kubernetes yaml file. I am always getting the 
following error.


cp: can't create '/opt/ignite/apache-ignite-fabric/libs/README.txt': 
File exists
cp: can't create 
'/opt/ignite/apache-ignite-fabric/libs/ignite-kubernetes-2.5.0.jar': 
Permission denied
cp: can't create 
'/opt/ignite/apache-ignite-fabric/libs/jackson-core-asl-1.9.13.jar': 
Permission denied
cp: can't create 
'/opt/ignite/apache-ignite-fabric/libs/jackson-mapper-asl-1.9.13.jar': 
Permission denied
cp: can't create 
'/opt/ignite/apache-ignite-fabric/libs/licenses/apache-2.0.txt': File 
exists
cp: can't create 
'/opt/ignite/apache-ignite-fabric/libs/licenses/ignite-kubernetes-licenses.txt': 
Permission denied


Any insights is appreciated.

Thanks

Re: Persistence store

[slut_hunter]

In this screenshot, we see 3 nodes with a full cache.
 

In this screenshot, we see 3 nodes after restarting one.
 


Node log before restart
befor_stop.log
  


Node log after restart
after_start.log
  



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite YARN deployment - how to use TCP IP Discovery?

[Andrei Aleksandrov]

Hi,

I guess you can try collect all IP addresses from all nodes that managed 
by YARN (where you are going to start Ignite) and add them all to 
addresses into TcpDiscoveryVmIpFinder part of Ignite configuration.


Also you should provide the guarantee that each such hosts will be able 
to connect each other.


BR,
Andrei

11/5/2019 9:15 PM, Seshan, Manoj N. (TR Tech, Content & Ops) пишет:


We are using Ignite as a Distributed In-Memory cache, deployed using 
YARN on a Hadoop Cluster.  We have configured Zookeeper Discovery, and 
this is working fine.


Given this is a small 20 node Ignite cluster, Zookeeper Discovery 
seems overkill. Would it be possible to switch to TCP Discovery? 
Multicast Finding is not an option, as that is disabled. Static IP 
Finding would also not work, as the Ignite Containers are dynamically 
allocated by YARN to arbitrary nodes of the Hadoop Cluster.


Rgds

*Manoj Seshan - Senior Architect*

Platform Content Technology, Bangalore

cid:image001.gif@01C95541.6801BF70

*Voice:*+91-98806 72987  +91-80-67492572

Re: Data is lost during rebalance

[novacean.alex]

Hello Slava,

Apparently i celebrated to early. The first test i performed after i used
the 'backup' cache property in the config it was a success indeed, but the
test was performed with a half full cache. When performing the test with the
cache full the results are the same as previously, entries missing after re
balance.

The code snipped you provided returned : REPLICATED. And in visor i also had
this which i missed to share earlier:
 

Thank you,
Alex Novacean.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: recoveryBallotBoxes in MvccProcessorImpl memory leak?

[Ilya Kasnacheev]

Hello!

Can you please show contents of some of these records, as well as their
referential path to MvccProcessorImpl?

Regards,
-- 
Ilya Kasnacheev


пт, 1 нояб. 2019 г. в 03:25, mvkarp :

> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2658/heapanalysisMAT.jpg>
>
>
> I've attached an Eclipse MAT heap analysis. As you can see MVCC is disabled
> (there are no TRANSACTIONAL_SNAPSHOT caches in the cluster)
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Persistence store

[Ilya Kasnacheev]

Hello!

It should be restored from persistent store. Can you provide logs from
nodes? Are you sure you don't clear persistence dirs between restarts?

Regards,
-- 
Ilya Kasnacheev


ср, 6 нояб. 2019 г. в 15:09, slut_hunter :

> From Persistent store.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite 2.7.0 YARN deployment - IGNITE_JVM_OPTS doesn't seem to work

[Ilya Kasnacheev]

Hello!

You should use Static IP Finder without specifying any hosts, Yarn launcher
will pass the list of hosts to discover via environment variable.

IGNITE_JVM_OPTS should work. Please try to debug this issue, file a ticket
against IGNITE JIRA if you have any specifics.

Regards,
-- 
Ilya Kasnacheev


вт, 5 нояб. 2019 г. в 21:34, Seshan, Manoj N. (TR Tech, Content & Ops) <
manoj.ses...@thomsonreuters.com>:

> We are trying to …
>
>1. Use the G1 garbage collector for smaller stop-the-world GC pauses.
>2. Obtain verbose logs from Ignite for troubleshooting purposes
>
>
>
> We have tried setting IGNITE_JVM_OPTS=”-DIGNITE_QUIET=false -XX:+UseG1GC”,
> but the JVM options are not taking effect on the Server nodes.
>
>
>
> Please help.
>
>
>
> Rgds, Manoj
>
>
>
> *Manoj Seshan - Senior Architect*
>
> Platform Content Technology, Bangalore
>
> [image: cid:image001.gif@01C95541.6801BF70]
>
> *Voice:* +91-98806 72987  +91-80-67492572
>
>
>
> *From:* Seshan, Manoj N. (TR Tech, Content & Ops)
> *Sent:* Tuesday, November 05, 2019 11:45 PM
> *To:* user@ignite.apache.org
> *Subject:* Ignite YARN deployment - how to use TCP IP Discovery?
>
>
>
> We are using Ignite as a Distributed In-Memory cache, deployed using YARN
> on a Hadoop Cluster.  We have configured Zookeeper Discovery, and this is
> working fine.
>
>
>
> Given this is a small 20 node Ignite cluster, Zookeeper Discovery seems
> overkill. Would it be possible to switch to TCP Discovery? Multicast
> Finding is not an option, as that is disabled. Static IP Finding would also
> not work, as the Ignite Containers are dynamically allocated by YARN to
> arbitrary nodes of the Hadoop Cluster.
>
>
>
> Rgds
>
>
>
> *Manoj Seshan - Senior Architect*
>
> Platform Content Technology, Bangalore
>
> [image: cid:image001.gif@01C95541.6801BF70]
>
> *Voice:* +91-98806 72987  +91-80-67492572
>
>
>

Re: Data is lost during rebalance

[Вячеслав Коптилин]

Hi Alex,

Oh... I missed the fact that your cache is replicated. In that case, you
don't need to specify the number of backups.
Could you please check, that the cache mode is replicated? You can try the
following code snippet:

System.out.println(ignite.cache("session-cache").getConfiguration(CacheConfiguration.class).getCacheMode());

Thanks,

S.


ср, 6 нояб. 2019 г. в 14:53, novacean.alex :

> Hello Slava,
>
> Thank you very much for the answer. It worked! Now every time 1 ignite node
> gets restarted it re-balances the exact number of keys.
>
> I was aware of the "backup" cache property but i think i misunderstood it's
> usages. As my cache is REPLICATED and in the documentations says that */"In
> Ignite, replicated caches are implemented in a way similar to partitioned
> caches where every key has a primary copy and is also backed up on all
> other
> nodes in the cluster."/ * i thought that really implies that i already have
> the backups.
>
> Thank you again,
> Alex.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Persistence store

[slut_hunter]

>From Persistent store.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Persistence store

[Ilya Kasnacheev]

Hello!

Since you have two storages (Persistent store and Cassandra) I would like
to ask which one you are expecting to be restored from?

Regards,
-- 
Ilya Kasnacheev


ср, 6 нояб. 2019 г. в 12:23, slut_hunter :

> Good afternoon. Help me please. I use a cluster of 3 nodes 2,7,6 with the
> settings 
> but if I turn off 1 node and turn it back on, the cluster does not restore
> the cache from the storage
> There is 1 warning in the logs Persistence store is configured, but both
> read-through and write-through are disabled.
> Tell me how to properly restore the cache from storage.
>
> Full config:
>
>
> Java client example:
> String cacheName =
> ContactRepository.prepareCacheName(orgId);
> CacheConfiguration cacheConfig = new CacheConfiguration(cacheName);
> cacheConfig.setCacheMode(CacheMode.PARTITIONED);
> cacheConfig.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
>
> cacheConfig.setBackups(0);
> ContactCassandraCacheStoreExFactory factory = new
> ContactCassandraCacheStoreExFactory();
> factory.setDataSource(cassandraSource);
> factory.setThreadsCount(4);
> factory.setCacheName(cacheName);
> factory.setLoadCacheConfig(new LoadCacheConfig(keyspace, table));
> cacheConfig.setCacheStoreFactory(factory);
> cacheConfig.setIndexedTypes(Integer.class, ContactDto.class);
> IgniteConfiguration cfg = new IgniteConfiguration();
> // Ignite persistence configuration.
> DataStorageConfiguration storageCfg = new
> DataStorageConfiguration();
>
> storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
> cfg.setDataStorageConfiguration(storageCfg);
> cfg.setIgniteInstanceName("springDataNode");
> cfg.setWorkDirectory("/tmp/ignite");
>
> cfg.setClientMode(clientMode);
> cfg.setPeerClassLoadingEnabled(true);
>
> cfg.setMetricsLogFrequency(0);
> cfg.setFailureDetectionTimeout(560_000);
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Data is lost during rebalance

[novacean.alex]

Hello Slava,

Thank you very much for the answer. It worked! Now every time 1 ignite node
gets restarted it re-balances the exact number of keys.

I was aware of the "backup" cache property but i think i misunderstood it's
usages. As my cache is REPLICATED and in the documentations says that */"In
Ignite, replicated caches are implemented in a way similar to partitioned
caches where every key has a primary copy and is also backed up on all other
nodes in the cluster."/ * i thought that really implies that i already have
the backups.

Thank you again,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Not able to start second server node due to authentication failure

[Zaheer]

Hi Sankar,

What Andei said is correct. We need to return a security subject. I faced
this problem and solved it like this : 

*1. Create your own SecurityPermissionSet class that implements
org.apache.ignite.plugin.security.SecurityPermissionSet .*

/public class TestSecurityPermissionSet implements SecurityPermissionSet,
Serializable {
private boolean defaultAllowAll;
private Map> taskPermissions;
private Map> cachePermissions;
private Map>
servicePermissions;
private Collection systemPermissions;

public TestSecurityPermissionSet(boolean defaultAllowAll, Map> taskPermissions, Map> cachePermissions, Map> servicePermissions,
Collection systemPermissions) {
this.defaultAllowAll = defaultAllowAll;
this.taskPermissions = taskPermissions;
this.cachePermissions = cachePermissions;
this.servicePermissions = servicePermissions;
this.systemPermissions = systemPermissions;
}

public boolean defaultAllowAll() {
return defaultAllowAll;
}

public Map> taskPermissions()
{
return taskPermissions;
}

public Map> cachePermissions()
{
return cachePermissions;
}

public Map>
servicePermissions() {
return servicePermissions;
}

@Nullable
public Collection systemPermissions() {
return systemPermissions;
}
}/
*2. Create your own security subject (say TestSecuritySubject) class that
implements org.apache.ignite.plugin.security.SecuritySubject.*
 /public class TestSecuritySubject implements SecuritySubject, Serializable
{

private SecuritySubjectType subjectType;
private UUID uuid;
private Object login;
private TestSecurityPermissionSet securityPermissionSet;

public TestSecuritySubject(SecuritySubjectType subjectType, UUID uuid,
Object login, TestSecurityPermissionSet securityPermissionSet) {
this.subjectType = subjectType;
this.uuid = uuid;
this.login = login;
this.securityPermissionSet = securityPermissionSet;
}

public UUID id() {
return uuid;
}

public SecuritySubjectType type() {
return subjectType;
}

public Object login() {
return login;
}

public InetSocketAddress address() {
return null;
}

public TestSecurityPermissionSet permissions() {
return securityPermissionSet;
}
}/
*3. Create your own security context class that implements
org.apache.ignite.internal.processors.security.SecurityContext , with a
TestSecuritySubject field in the class.*
/public class TestSecurityContext implements SecurityContext, Serializable {
private TestSecuritySubject securitySubject;

public TestSecurityContext(TestSecuritySubject securitySubject) {
this.securitySubject = securitySubject;
}

public SecuritySubject subject() {
return securitySubject;
}

public boolean taskOperationAllowed(String taskClsName,
SecurityPermission perm) {
//Check if the security subject task permissions contain the given
taskClsName and given perm and return true/false accordingly
}

public boolean cacheOperationAllowed(String cacheName,
SecurityPermission perm) {
//Check if the security subject cache permissions contain the given
cacheName and given perm and return true/false accordingly

}

public boolean serviceOperationAllowed(String srvcName,
SecurityPermission perm) {
   //Check if the security subject service permissions contain the given
srvcName and given perm and return true/false accordingly
}

public boolean systemOperationAllowed(SecurityPermission perm) {
//Check if the security subject system permissions contain the given 
perm and return true/false accordingly
}

   
}/

*4. In the authenticateNode method, create an instance of your
SecuritySubject and set it in your SecurityContext instance and return it*. 

/public SecurityContext authenticateNode(ClusterNode node,
SecurityCredentials cred) throws IgniteCheckedException {
 TestSecurityPermissionSet permissionSet = new
TestSecurityPermissionSet(true, null, null, null, null);

TestSecuritySubject securitySubject = new
TestSecuritySubject(SecuritySubjectType.REMOTE_NODE, node.id(), "",
permissionSet);

return new TestSecurityContext(securitySubject);

}/

*In the above snippet, I gave
TestSecurityPermissionSet(true,null,null,null,null) ==> That is default
allow all is true. This way, you returned a security context with proper
subject and proper permissions.*

Let me know if you need more clarification. 







--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Not able to start second server node due to authentication failure

[Andrei Aleksandrov]

Hi,

It's correct that SecurityContext is null in your case:

    SecurityContext subj = spi.nodeAuth.authenticateNode(node, cred);

    if (subj == null) {
        // Node has not pass authentication.
        LT.warn(log, "Authentication failed [nodeId=" + node.id() +
            ", addrs=" + U.addressesAsString(node) + ']');

This subject should be returned from security processor (here spi is 
DiscoverySPI):


    spi.setAuthenticator(new DiscoverySpiNodeAuthenticator() {
    @Override public SecurityContext 
authenticateNode(ClusterNode node, SecurityCredentials cred) {

    try {
    return ctx.security().authenticateNode(node, cred);
    }
    catch (IgniteCheckedException e) {
    throw U.convertException(e);
    }
    }

    @Override public boolean isGlobalNodeAuthentication() {
    return ctx.security().isGlobalNodeAuthentication();
    }
    });

From ctx.security().authenticateNode(node, cred); method.

But there is no security processor by default in Ignite. However, looks 
like you should re-implement your DiscoverySPI and setAuthenticator method:


https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/DiscoverySpi.html#setAuthenticator-org.apache.ignite.spi.discovery.DiscoverySpiNodeAuthenticator-

BR,
Andei

11/6/2019 1:26 PM, Sankar Ramiah пишет:
I have implemented custom authentication and authorization through a 
plugin.


/public class MyPlugin implements GridSecurityProcessor, IgnitePlugin {/

Implemented authenticateNode method which bypasses authentication for 
server nodes and returns a security context instance. validateNode is 
returning null always. When I start the second server node, 
authenticateNode is being invoked and it goes through code which 
bypasses authentication but the startup fails after that with 
Authentication Failed error. validateNode doesn't seem to be invoked.
ERROR: org.apache.ignite.internal.IgniteKernal - Got exception while 
starting (will rollback startup routine). 
org.apache.ignite.IgniteCheckedException: Failed to start manager: 
GridManagerAdapter [enabled=true, 
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager] 
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1687) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066) 
[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038) 
[ignite-core-2.7.0.jar!/:2.7.0] Caused by: 
org.apache.ignite.IgniteCheckedException: Failed to start SPI: 
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, 
marsh=JdkMarshaller 
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5b51df3f], 
reconCnt=10, reconDelay=2000, maxAckTimeout=60, 
forceSrvMode=false, clientReconnectDisabled=false, internalLsnr=null] 
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:939) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1682) 
~[ignite-core-2.7.0.jar!/:2.7.0] ... 66 more Caused by: 
org.apache.ignite.spi.IgniteSpiException: Authentication failed 
[nodeId=e3ab993e-0acf-4e55-86a7-473989e0fdca, addr=0.0.0.0] at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.authenticationFailedError(TcpDiscoverySpi.java:1935) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:967) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020) 
~[ignite-core-2.7.0.jar!/:2.7.0] at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297) 
~[ignite-core-2.7.0.jar!/:2.7.0]



I have spent quiet sometime with this error. The first node starts 
without any issues. Multiple server start fine without the security 
plugin in place. Any help in this regard would be highly appreciated. 
Thanks.


Sent from the Apache Ignite Users mailing list archive 
 at Nabble.com.

Re: Data is lost during rebalance

[Вячеслав Коптилин]

Hello Alex,

You need to specify the number of backups for your cache. For instance,




...

...




Please take a look at the page for details:
https://apacheignite.readme.io/docs/primary-and-backup-copies

Thanks,
S.

ср, 6 нояб. 2019 г. в 12:20, novacean.alex :

> Hello,
>
> I am a new user of Ignite and i'm trying to get a cluster with 3 server
> nodes up and running in Kubernetes. Everything works perfectly until one
> ignite node gets restarted. During the rebalance process i noticed that
> ~20.000 entries are lost, This happens with each restart. If two ignite
> nodes are restarted at the same time at the end of the rebalance process of
> the ~40.000 entries are lost.
>
> Before the restart:
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2660/misskeystest.png>
>
>
>
> After restart and rebalance:
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2660/misskeuresults.png>
>
>
>
> After the rebalance process is done @n2 is missing 18705 entries.
>
> This is the config file i am using:
>
> 
> http://www.springframework.org/schema/beans;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd
> http://www.springframework.org/schema/context
> https://www.springframework.org/schema/context/spring-context.xsd;>
> 
> 
>  value="${IGNITE_OVERRIDE_CONSISTENT_ID}"/>
> 
> 
> 
> 
> 
>  class="org.apache.ignite.configuration.DataStorageConfiguration">
> 
> 
>  class="org.apache.ignite.configuration.DataRegionConfiguration">
>  value="false"/>
> 
> 
>  value="RANDOM_2_LRU"/>
> 
> 
> 
> 
> 
> 
>class="org.apache.ignite.configuration.CacheConfiguration">
>   
>   
>   
>   
>   
>   
>   
>   
>   
>value="PRIMARY_SYNC"/>
>   
>class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>  
>   
>   
>   
> 
>  
>class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>   
>   
>   
>   
> 
>   
>   
>   
>   
>  
> 
>  class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> 
> 
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder">
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> I have't found any other issue related to this so my guess is that must be
> a
> configuration problem.
> Any help would be greatly appreciated.
>
> Thank you,
> Alex.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Not able to start second server node due to authentication failure

[Sankar Ramiah]

I have implemented custom authentication and authorization through a plugin.

/public class MyPlugin implements GridSecurityProcessor, IgnitePlugin {/

Implemented authenticateNode method which bypasses authentication for server
nodes and returns a security context instance. validateNode is returning
null always. When I start the second server node, authenticateNode is being
invoked and it goes through code which bypasses authentication but the
startup fails after that with Authentication Failed error. validateNode
doesn't seem to be invoked.
ERROR: org.apache.ignite.internal.IgniteKernal - Got exception while
starting (will rollback startup
routine).org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]   
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1687)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1066)
[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
[ignite-core-2.7.0.jar!/:2.7.0]Caused by:
org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@5b51df3f],
reconCnt=10, reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
clientReconnectDisabled=false, internalLsnr=null]at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:939)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1682)
~[ignite-core-2.7.0.jar!/:2.7.0]... 66 moreCaused by:
org.apache.ignite.spi.IgniteSpiException: Authentication failed
[nodeId=e3ab993e-0acf-4e55-86a7-473989e0fdca, addr=0.0.0.0]at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.authenticationFailedError(TcpDiscoverySpi.java:1935)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:967)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020)
~[ignite-core-2.7.0.jar!/:2.7.0]at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
~[ignite-core-2.7.0.jar!/:2.7.0] 


I have spent quiet sometime with this error. The first node starts without
any issues. Multiple server start fine without the security plugin in place.
Any help in this regard would be highly appreciated. Thanks.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Persistence store

[slut_hunter]

Good afternoon. Help me please. I use a cluster of 3 nodes 2,7,6 with the
settings 
but if I turn off 1 node and turn it back on, the cluster does not restore
the cache from the storage
There is 1 warning in the logs Persistence store is configured, but both
read-through and write-through are disabled.
Tell me how to properly restore the cache from storage.

Full config:


Java client example:
String cacheName = ContactRepository.prepareCacheName(orgId);
CacheConfiguration cacheConfig = new CacheConfiguration(cacheName);
cacheConfig.setCacheMode(CacheMode.PARTITIONED);
cacheConfig.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);

cacheConfig.setBackups(0);
ContactCassandraCacheStoreExFactory factory = new
ContactCassandraCacheStoreExFactory();
factory.setDataSource(cassandraSource);
factory.setThreadsCount(4);
factory.setCacheName(cacheName);
factory.setLoadCacheConfig(new LoadCacheConfig(keyspace, table));
cacheConfig.setCacheStoreFactory(factory);
cacheConfig.setIndexedTypes(Integer.class, ContactDto.class);
IgniteConfiguration cfg = new IgniteConfiguration();
// Ignite persistence configuration.
DataStorageConfiguration storageCfg = new
DataStorageConfiguration();
   
storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
cfg.setDataStorageConfiguration(storageCfg);
cfg.setIgniteInstanceName("springDataNode");
cfg.setWorkDirectory("/tmp/ignite");

cfg.setClientMode(clientMode);
cfg.setPeerClassLoadingEnabled(true);

cfg.setMetricsLogFrequency(0);
cfg.setFailureDetectionTimeout(560_000);



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Data is lost during rebalance

[novacean.alex]

Hello,

I am a new user of Ignite and i'm trying to get a cluster with 3 server
nodes up and running in Kubernetes. Everything works perfectly until one
ignite node gets restarted. During the rebalance process i noticed that
~20.000 entries are lost, This happens with each restart. If two ignite
nodes are restarted at the same time at the end of the rebalance process of
the ~40.000 entries are lost.

Before the restart:
 


After restart and rebalance:
 


After the rebalance process is done @n2 is missing 18705 entries.

This is the config file i am using:


http://www.springframework.org/schema/beans;
xmlns:context="http://www.springframework.org/schema/context;
xmlns:util="http://www.springframework.org/schema/util;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd
http://www.springframework.org/schema/context  
https://www.springframework.org/schema/context/spring-context.xsd;>






















  
  
  
  
  
  
  
  
  
  
  
  
  
 
  
  
  

 
  
  
  
  
  

  
  
  
  
 














I have't found any other issue related to this so my guess is that must be a
configuration problem.
Any help would be greatly appreciated.

Thank you,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to insert data?

[BorisBelozerov]

When I run your code in one node, It run OK
But when I run your code in a cluster, It can't run. I can select but can't
insert or do other things



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to insert data?

[BorisBelozerov]

Now I can show table DATAX by run "!tables"
But when I insert data, it can't run
In Eclipse, the error is: Key is missing from query
In Sqlline, the error is: Failed to execute DML statement [stmt=insert into
"tdCache".DATAX (key,value) values (1,'value 1');]




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to insert data?

[BorisBelozerov]

When I run "!tables", there isn't any tables or schemas



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/