Re: Ignite on RBAC enabled K8s cluster
Hi Vishwas, Usually, this issue happens because of: 1. Default service account doesn't have permissions to use the endpoint to get all related IP addresses (of Ignite nodes). 2. A cluster is deployed in not default namespace. For example, in Openshift namespace is a project name. To resolve that you need to create a service account and grant necessary permissions (we don't need cluster-admin role): *sa.yml* *role.yml* *rolebind.yml* Do not forget to replace , add `serviceAccountName` into DeploymentConfig [1] and specify namespace property of TcpDiscoveryKubernetesIpFinder [1]. Best Regards, Roman [1] https://apacheignite.readme.io/docs/kubernetes-deployment#section-deploying-on-openshift -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Ignite on RBAC enabled K8s cluster
Hi, I am trying to bring up Ignite on RBAC enabled K8s cluster. As part of discovery, when ignite nodes are trying to discover one another, I am seeing below error: [02:16:08,755][SEVERE][tcp-disco-ip-finder-cleaner-#4][TcpDiscoverySpi] Failed to clean IP finder up. class org.apache.ignite.spi.IgniteSpiException: Failed to retrieve Ignite pods IP addresses. at org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:172) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1810) at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.cleanIpFinder(ServerImpl.java:1921) at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body(ServerImpl.java:1896) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/ignite at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) at org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder.getRegisteredAddresses(TcpDiscoveryKubernetesIpFinder.java:153) I see there is a ticket on it, but it uses a cluster-admin role. Not sure why we need cluster-admin role. I tried the steps mentioned in the ticket, but still I am getting the same error. I was not able to find any documentation on the same. Has anyone tried bringing up Ignite on RBAC enabled K8s cluster ? Regards, Vishwas -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Throwing error after enabling
Thanks Val, I am on Ignite 2.4 and spark 2.2 . If I move to Ignite 2.5 what version of spark is supported? Thanks Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Distributed Database as best choice for persistence
What's the point of scaling persistence manually over allowing Ignite to scale both RAM and disk layers for you? So, if to answer your question set in the subj, Ignite persistence is the best scalable and strongly consistent disk option for Ignite. If you need Multi DC or backups, then you can look for enterprise Ignite offerings like GridGain. - Denis On Tue, Jun 19, 2018 at 1:18 AM piyush wrote: > >> May I ask why don't you want to go for Ignite persistence? > > > To operate and scale the storage layer independently and process related to > it like Compaction for example. > I intent to bundle WebServer (Netty) + Application Server (Netty) + DB > Engine (Ignite) + Cache in single deployable jar artifacts for my > application > > Also to have other features like Multi DC, Hot back up etc. which are there > in other distributed KV databases. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Throwing error after enabling
Bhaskar, Which version are you on? This configuration was added in 2.5. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Cache Configuration for a data region
Hello, > Do I need to configure something else for off heap eviction? If you are using Ignite Native Persistence, you don't need to configure page-based eviction. In that case, it will be automatically enabled. Please take a look at this page for the details: https://apacheignite.readme.io/docs/evictions#section-off-heap-memory > As per the thread below, I need to set some data page eviction too, but > official documentation says it is deprecated If I am not mistaken, it is not deprecated. At least I did not find any mention of it. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
"Connect timed out" errors during cluster restart
Hi Igniters, I'm getting "connect timed out" errors on each cluster restart Errors are logged ~10 times before cluster activation Everything is working fine after that They are looking as false alarms... looks like nodes are trying to connect each other when they are not UP yet. Why it is logged with ERROR level? I have SSL=on and Authentication=on Topology: 2 server nodes Ignite version: 2.5.0 OS: Windows Server 2012 R2 I have custome discovery SPI implementation but it just injects auth credentials on local node init, nothing more (it extends TcpDiscoverySpi) Sample error: 2018-06-19 19:43:29.347 [main] ERROR com.xxx.lk.ignite.AuthTcpDiscoverySpi - Exception on direct send: connect timed out java.net.SocketTimeoutException: connect timed out at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_162] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_162] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_162] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_162] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) ~[?:1.8.0_162] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_162] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_162] at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) ~[?:1.8.0_162] at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1450) ~[ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1413) ~[ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1199) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1046) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:890) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:373) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1948) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:915) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1720) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1033) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693) [ignite-core-2.5.0.jar:2.5.0] at org.apache.ignite.Ignition.start(Ignition.java:352) [ignite-core-2.5.0.jar:2.5.0] at com.xxx.lk.ignite.WindowsService.start(WindowsService.java:45) [lk.ignite_auth-1.0.0.jar:?] 2018-06-19 19:43:29.362 [main] DEBUG com.xxx.lk.ignite.AuthTcpDiscoverySpi - Failed to send join request message [addr=v-hp-lk-dcn02.xxxgroup.tek.loc/ 10.2.0.252:47502, msg=connect timed out] [ignite-server.xml] v-hp-lk-dcn01.xxxgroup.tek.loc:47500..47504 v-hp-lk-dcn02.xxxgroup.tek.loc:47500..47504 BR, Oleksandr
Throwing error after enabling
Hi, Iam trying o enable authentication by setting , but geting "class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context" , where is the missing part? My default-config.xml http://www.springframework.org/schema/beans; 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;> The error log: class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context [springUrl=file:/config/default-config.xml, err=Error creating bean with name 'ignite.cfg' defined in URL [file:/config/default-config.xml]: Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'authenticationEnabled' of bean class [org.apache.ignite.configuration.IgniteConfiguration]: Bean property 'authenticationEnabled' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:980) at org.apache.ignite.Ignition.start(Ignition.java:350) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to instantiate Spring XML application context [springUrl=file:/config/default-config.xml, err=Error creating bean with name 'ignite.cfg' defined in URL [file:/config/default-config.xml]: Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'authenticationEnabled' of bean class [org.apache.ignite.configuration.IgniteConfiguration]: Bean property 'authenticationEnabled' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?] at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:392) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104) at org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98) at org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:737) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:938) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:717) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:686) at org.apache.ignite.Ignition.start(Ignition.java:347) ... 1 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ignite.cfg' defined in URL [file:/config/default-config.xml]: Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'authenticationEnabled' of bean class [org.apache.ignite.configuration.IgniteConfiguration]: Bean property 'authenticationEnabled' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter? at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1568) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1276) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866) at
SQL Query full table scan, Node goes down
Hi, I have Ignite 5 node cluster with more than dozen tables(Cache) . Our client are using SQL and Tableau. The node goes down when any client quries select * from table which is bigger than RAM size. we have 3 years data but last 2 months data is actively quried 80% of time. 1. How can I control such SQL when the rows are more than RAM size? 2. We have to control on the node not client as we can't conrol client. Thanks Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Data region and Data storage metrics via Ignite Client
We have a ssl enabled 2.5.0 ignite cluster. I am trying to grab some of the
DataRegionMetrics and DataStorageMetrics via spinning up an ignite client.
We have already created caches with data region on the cluster. We also have
the metrics enabled on our cluster.
We get the ignite client as follows:
/cfg.setClientMode(true);
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
ipFinder.setShared(true);
ipFinder.setAddresses(Arrays.asList(igniteHosts.split(",")));
discoverySpi.setIpFinder(ipFinder);
cfg.setSslContextFactory(ssl);
cfg.setDiscoverySpi(discoverySpi);
Ignite ignite = Ignition.getOrStart(cfg)/
And then I try to get the Data Region metrics as follows:
/Collection regionsMetrics = ignite.dataRegionMetrics();/
And the Data Storage metrics as follows:
/DataStorageMetrics storageMetrics = ignite.dataStorageMetrics();/
The problem I am facing is that the above code basically gives us an empty
list of DataRegionMetrics and null DataStorageMetrics.
So, my question is whether this is expected behaviour or am I missing
something obvious? How do I go about getting these metrics via a client?
P.S: I am able to get ALL the cache metrics via the client. its just the
data storage and data region ones that I am not able to get.
Thanks
Aniket
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: IgniteCheckedException: Error while creating file page store caused by NullPointerException
As a workaround, you can try to add execution rights (like in your example) to all files under work directory. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Using Persistent ignite queues
Hi, Could you please provide next for investigation: 1)Thread dump that you should create at the moment when cluster hung. 2)Code of your service 3)Logs of the cluster nodes. 4)The configuration of the clusters. BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: IgniteCheckedException: Error while creating file page store caused by NullPointerException
Hi, Is this issue reproducible? Can you change the work directory path or clear your work directory and check again? Did you try to modify or copy anything from work directory? However, could you please provide the cluster configuration and code reproducer? BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Using Persistent ignite queues
Hi, I have a scenario where I use a persistent ignite queue across cluster nodes. This is my setup using ignite 2.5- Few server nodes which hosts some caches in persistance mode and a cluster singleton ignite service. This ignite service upon initialization, initializes two persistent queues. Rest of the nodes in cluster are client nodes. They either put data in queue or consume data from queue (depending on their role). Basically I am using Ignite queue as a worker queue, one party fills the queue and another party empties it. I have observed that sometimes the queue gets stuck, as in the queue.take() method on one node keeps blocking even if there are items in the queue. This issue does not go away until I restart the whole cluster from fresh state. I looked into the /etc/ignite/peristance/1 folder (1 is the consistent node id for one of the nodes). It only contains folders to store the caches. I cannot see any reference of queue getting saved. I am missing something here? Thanks, Arun -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Deleting a ticket from https://issues.apache.org/jira/projects/IGNITE/issues
Hi ptupitsyn, Thanks a lot !!! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
RE: A bug in SQL "CREATE TABLE" and its underlying Ignite cache
Hi,
How should I use BinaryObject in the CREATE TABLE statement? I try using
BinaryObject.class.getName() as the value_type, but get the following exception:
class org.apache.ignite.IgniteCheckedException: Failed to initialize property
'ORGID' of type 'java.lang.Long' for key class 'class java.lang.Long' and value
class 'interface org.apache.ignite.binary.BinaryObject'. Make sure that one of
these classes contains respective getter method or field.
I want to use BinaryObject here for some flexibility.
Thanks,
Cong
From: Вячеслав Коптилин [mailto:slava.kopti...@gmail.com]
Sent: 2018年6月18日 18:10
To: user@ignite.apache.org
Subject: Re: A bug in SQL "CREATE TABLE" and its underlying Ignite cache
Hello,
It seems that the root cause of the issue is wrong values of 'KEY_TYPE' and
'VALUE_TYPE' parameters.
In your case, there is no need to specify 'KEY_TYPE' at all, and 'VALUE_TYPE'
should Person.class.getName() I think.
Please try the following:
String createTableSQL = "CREATE TABLE Persons (id LONG, orgId LONG,
firstName VARCHAR, lastName VARCHAR, resume VARCHAR, salary FLOAT, PRIMARY
KEY(firstName))" +
"WITH \"BACKUPS=1, ATOMICITY=TRANSACTIONAL,
WRITE_SYNCHRONIZATION_MODE=PRIMARY_SYNC, CACHE_NAME=" + PERSON_CACHE_NAME +
", VALUE_TYPE=" + Person.class.getName() + "\"";
Best regards,
Slava.
пн, 18 июн. 2018 г. в 21:50, Cong Guo
mailto:cong.g...@huawei.com>>:
Hi,
I need to use both SQL and non-SQL APIs (key-value) on a single cache. I follow
the document in:
https://apacheignite-sql.readme.io/docs/create-table
I use “CREATE TABLE” to create the table and its underlying cache. I can use
both SQL “INSERT” and put to add data to the cache. However, when I run a
SqlFieldsQuery, only the row added by SQL “INSERT” can be seen. The Ignite
version is 2.4.0.
You can reproduce the bug using the following code:
CacheConfiguration dummyCfg = new
CacheConfiguration<>("DUMMY");
dummyCfg.setSqlSchema("PUBLIC");
try(IgniteCache dummyCache = ignite.getOrCreateCache(dummyCfg)){
String
createTableSQL = "CREATE TABLE Persons (id LONG, orgId LONG, firstName VARCHAR,
lastName VARCHAR, resume VARCHAR, salary FLOAT, PRIMARY KEY(firstName))" +
"WITH \"BACKUPS=1, ATOMICITY=TRANSACTIONAL,
WRITE_SYNCHRONIZATION_MODE=PRIMARY_SYNC, CACHE_NAME=" + PERSON_CACHE_NAME +
", KEY_TYPE=String,
VALUE_TYPE=BinaryObject\"";
dummyCache.query(new SqlFieldsQuery(createTableSQL)).getAll();
SqlFieldsQuery
firstInsert = new SqlFieldsQuery("INSERT INTO Persons (id, orgId, firstName,
lastname, resume, salary) VALUES (?,?,?,?,?,?)");
firstInsert.setArgs(1L, 1L, "John", "Smith", "PhD", 1.0d);
dummyCache.query(firstInsert).getAll();
try(IgniteCache personCache = ignite.cache(PERSON_CACHE_NAME)){
Person p2 = new Person(2L, 1L, "Hello", "World", "Master", 1000.0d);
personCache.put("Hello", p2);
IgniteCache binaryCache = personCache.withKeepBinary();
System.out.println("Size of the cache is: " +
binaryCache.size(CachePeekMode.ALL));
binaryCache.query(new ScanQuery<>(null)).forEach(entry ->
System.out.println(entry.getKey()));
System.out.println("Select results: ");
SqlFieldsQuery qry = new SqlFieldsQuery("select * from Persons");
QueryCursor> answers = personCache.query(qry);
List> personList = answers.getAll();
for(List row : personList) {
String fn = (String)row.get(2);
Re: If a lock is held by another node IgniteCache.isLocalLocked() appears to return incorrect results.
Hi, I filed next issue: https://issues.apache.org/jira/browse/IGNITE-8833 Thank you, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: [ANNOUNCE] Apache Ignite 2.5.0 Released
Hi szj, Could you please redirect your questions to the new thread? Also, don't forget to provide the steps for reproducing and logs. PS. I will check your case with ignitevisorcmd.sh and node restarting. BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: IgniteCheckedException: Error while creating file page store caused by NullPointerException
Exception not coming after running ignite with sudo. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: IgniteCheckedException: Error while creating file page store caused by NullPointerException
Additional logs, caused by AccessDeniedException 2018-06-19 16:27:51 ERROR GridDhtPartitionsExchangeFuture:495 - Failed to activate node components [nodeId=7ff3a67c-ed86-452a-9097-2626a0252a6e, client=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]] class org.apache.ignite.IgniteCheckedException: Error while creating file page store [file=/home/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin]: at org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98) at org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:450) at org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initForCache(FilePageStoreManager.java:411) at org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForCache(FilePageStoreManager.java:217) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:714) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:844) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:596) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:748) Caused by: java.nio.file.AccessDeniedException: /home/bizruntime/ubiquitos/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177) at java.nio.channels.FileChannel.open(FileChannel.java:287) at java.nio.channels.FileChannel.open(FileChannel.java:335) at org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.(RandomAccessFileIO.java:43) at org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIOFactory.create(RandomAccessFileIOFactory.java:42) at org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIOFactory.create(RandomAccessFileIOFactory.java:37) at org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78) ... 9 more 20 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Quick questions on Evictions
So how do I limit cache size if ignite native persistence is enabled using dataRegionCfg.setPersistenceEnabled(true)? I don't want it to keep a lot of data in memory and others may be kept on disk. That is the requirement. Also, I do have on heap cache enabled. But I read in many threads that Ignite stores everything off heap and only references may be kept in java heap. So how do I limit off heap cache usage? I mean I don't want to it to use more than a particular amount of off heap memory? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: If a lock is held by another node IgniteCache.isLocalLocked() appears to return incorrect results.
Hi, It looks like an issue. Let me investigate it and create an issue. BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
IgniteCheckedException: Error while creating file page store caused by NullPointerException
I am using Ignite 2.4 and using 2 server nodes and 1 client node. Due to power failure my nodes shutdown. So, After started two server nodes. I am getting following error. Even, I tried to activate cluster by control.sh --activate. But it's not responding anything. Even same for baseline topology(tried to print baseline topology. its not printing it to). IgniteCheckedException: Error while creating file page store [file=/home/apache-ignite-fabric-2.4.0-bin/work/db/node02-119b5ab9-11ac-456b-8488-6ba8f6d51d69/cache-c091e548-b45a-49b4-b8ec-2cb5e27c7af6_ConversationMessages/part-95.bin]:, done=true, state=SRV, evtLatch=0, remaining=[d62b8f0a-6ddc-4314-90f3-93ca24d44200], super=GridFutureAdapter [ignoreInterrupts=false, state=DONE, res=java.lang.NullPointerException, hash=812167532]] class org.apache.ignite.IgniteCheckedException: null at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7244) at org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259) at org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:207) at org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2347) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyUpdate(GridCacheDatabaseSharedManager.java:2396) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2137) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1341) at org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1129) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1066) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:664) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337) ... 2 more It might caused due to corrupted files after unexpected shutdown. How to solve this issue. Application is running in Production. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Quick questions on Evictions
Hi, DataPageEvictionMode is about algorithm of choosing page to be replaced. EvictionPolicy is what you are looking for. E.g. FifoEvictionPolicy or LruEvictionPolicy. It looks like EvictionPolicies can't be used with persistence as all of them uses non-persistent structures to track cache entries. On Tue, Jun 19, 2018 at 8:30 AM the_palakkaran wrote: > Hi, > > DataPageEvictionMode is deprecated now, right? What should I do to evict my > off heap entries? Also, can I limit off heap memory usage? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
Re: Deleting a ticket from https://issues.apache.org/jira/projects/IGNITE/issues
Hi, Please find the ticket ID https://issues.apache.org/jira/browse/IGNITE-8825. Thank you. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Distributed Database as best choice for persistence
>> May I ask why don't you want to go for Ignite persistence? To operate and scale the storage layer independently and process related to it like Compaction for example. I intent to bundle WebServer (Netty) + Application Server (Netty) + DB Engine (Ignite) + Cache in single deployable jar artifacts for my application Also to have other features like Multi DC, Hot back up etc. which are there in other distributed KV databases. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Deleting a ticket from https://issues.apache.org/jira/projects/IGNITE/issues
What is the ticket number? On Tue, Jun 19, 2018 at 11:06 AM, Raghav wrote: > Hello ptupitsyn, > > Thanks for replying. Do you have the permission to delete a ticket in > https://issues.apache.org/jira/projects/IGNITE/issues? > > Thank you. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Deleting a ticket from https://issues.apache.org/jira/projects/IGNITE/issues
Hello ptupitsyn, Thanks for replying. Do you have the permission to delete a ticket in https://issues.apache.org/jira/projects/IGNITE/issues? Thank you. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Deleting a ticket from https://issues.apache.org/jira/projects/IGNITE/issues
Hi, What is the ticket number? On Mon, Jun 18, 2018 at 5:14 PM, Raghav wrote: > Hi Dkarachentsev, > > Thanks for your comments. I have closed the ticket but the ticket is still > accessible with the URL. It would be helpful if we could delete the JIRA so > that the ticket is not accessible over internet. > > Kindly let us know the team to contact to deleting the ticket. > > Thanks!!! > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
