*USE CASE *- use IgniteAtomicLong for table sequence generation (may not be
correct approach in a distributed environment).
*Ignite Server *(start Ignite as server mode) - apache-ignite-2.8.0.20190215
daily build
*Ignite Service* (start Ignite as client mode) - use Ignite Spring to
initialize the
How do we enable the persistence for this atomicLong? My understanding is
that atomicLong or atomicReference can't be persisted. Even if it can be
persisted, isn't next value reset and started from the initial value.
My issue is that the cached sequence was removed from Spring bean. How do I
r
Hi Denis, I have the same issue when persistenceEnabled = true and when
Ignite is upgrade from 2.8.0 to 2.8.1. The data has been stored in the
disk (single node) running on Ignite 2.8.0. This exception happens for
persistence classes that do not implement java.io.serializable when
upgrading to 2
Hi Denis,
No, I don't change any types of fields. The data is stored in the disk with
Ignite 2.8.0. When I upgraded to 2.8.1, a serialization exception was
raised. Adding java.io.serializable, generating serialVersionUID did not
help. It seems that the data stored in the native persistence db ha
Hi Ilya,
Tried your suggestion, removing the userSeq field from the class. It still
raise the same exception -
org.apache.ignite.IgniteException: Cannot start/stop cache within lock
or transaction.
The error is thrown when trying to get igniteInstance.atomicLong("userSeq",
maxId, true);
T
Hi Denis,
please help...
I'm trying to use Cassandra Persistence Together with Ignite Persistence
(https://apacheignite.readme.io/docs/3rd-party-store#:~:text=3rd%20Party%20Persistence-,Overview,database%20that%20persists%20the%20data.&text=cache.,-integration.).
The Cassandra is used to store t
Hi Denis,
updated - I'm hitting the NPE bug
(https://issues.apache.org/jira/browse/IGNITE-13431) because I'm using
Cassandra as the data store, and key persistence strategy PRIMITIVE in the
original test. When I switched to a composite key, it worked. Not when
this bug gets fixed.
-- this fai
I got this exception for ignite 2.8.0. When the note restarted and the data
is inserted into the cache and Cassandra store. Please note
1) my setup is that Native Persistence is enabled. just one server node, no
client node
2) there is no issue for the very first start (i.e. the native storage
Thanks.
We tried it outside the transaction when the ignite instance restarted with
EventType.EVT_CLIENT_NODE_RECONNECTED. However, it is hang at
igniteInstance.atomicLong().
// when the ignite instance restarted, it hangs here
userSeq = igniteInstance.atomicLong("userSeq", maxId, tr
I'm able to use Cassandra Together with Ignite Persistence (see the example
below) usingIgnite 2.8.1. However I could not change to another keyspace
which has the same tables as the keyspace initially configurfed in the
ignite config file. The data changes are still stored in the old keyspace
ins
Thank you for your answer. I'm able to load the data from Cassandra to
Ignite Cache stores using Cache.loadfull(). This works well for the use
cases where 3rd party persistence store is used first, then Ignite Native
Persistence store is used with 3rd party persistence together later.
Howe
Thanks for your confirmation, Ilya.
I do have a follow-up question for you.
When Ignite Persistence is used together with Cassandra. The caches for
Cassandra table mappings are provided via xml file. The java class for the
mappings is for BOTH Ignite Persistence and Cassandra cache store. Wh
Thanks for your suggestion, Ilya. Can you give me a reference to override
default Cassandra Store implementation? I thought that the changes would be
on Ignite Persistence side because caching data from standalone Cassandra
store (with Ignite Persistence) did read configuration including class
de
Hi Ilya,
Thanks for your guidance and happy new year! Sorry for late catchup.
You are right, Ignite Native Persistence does track the changes in class
definition for "Ignite Native Persistence". But the configuration to load
data from Cache to Cassandra store is stored in xml configuration fil
Thanks for your clarifications, and appreciated your suggestions and
guidance.
My college and I went to ignite-cassandra module, commented two lines,
*/testing purpose/*, in
org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory.getPersistenceSettings(),
see the changes below. Rem
Thanks for your recommendations!
1) The dynamicConfigurationReload is not able to reset once
cacheStoreFactory is cached. It means that cacheStoreFactory does not read
this value unless cacheStoreFactory is first instantiated. Do I miss
something? Which factory should I put dynamicConfigurationR
1) My testing shows that CassandraCacheStoreFactory is read from xml config
once if the cache name does not exist in Ignite Persistence. It appears that
CassandraCacheStoreFactory bean is persisted along with cache name in Ignite
Persistence Store, CassandraCacheStoreFactory will not be re-instanti
Excepted from the latest Ignite doc -
"If the property (eagerTtl) is set to false, expired entries are not removed
immediately. Instead, they are removed when they are requested in a cache
operation by the thread that executes the operation."
Say mycache has two entries, e1, e2 with 5 min crea
Hi All,
I don't see ignite spring data 2.2 maven repo for the recent ignite 2.10.0
release. But I see ignite spring 2.10.0 maven repo. Did I miss anything?
Thanks,
Xinmin
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Ignitians,
I fail to understand what causes and need your help -
1) When k8s sees “Critical system error”, it will restart ignite-admin
server. Restarting is fine because of the critical system error. But what
are the causes of the critical system error?
2) Critical system error may
The cache is replicated
, has two nodes configured.
1) Why does ignite trigger the data rebalancing from Casssandra store?
Shouldn't it load the data cache from one node to another node? In what
case, does Ignite have to go the data store (Cassandra) to load data if the
cache is configured as "
Hi All,
Apache Ignite recommends to collocate data with data, which is a very nice
feature. This works well if you insert data through APIs provided by Ignite
(see the following code I copy from Ignite Doc). However, I don't know how
to handle the following cases
1. the data (company and perso
It seems that this enhancement has not been implemented yet for the following
cases:
trx.start() {
1. update t1 set col1='a' where col2='c';
2. update the same table t1 with cache API.
}
trx.end();
Can someone confirm?
many thanks, Xinmin
--
Sent from: http://apache-ignite-users.70518.x6.na
Thanks for reply. I got the most working thanks to the example
(https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/starschema/CacheStarSchemaExample.java)
provided by Ignite.
Here is my sql for POC (Cassandra DDL scripts)
create table ignitet
Hi Ilya,
Since I'm using Cassandra as data store, it raises the following exceptions
once MVCC is enabled -
class org.apache.ignite.IgniteCheckedException: Grid configuration parameter
invalid: readThrough cannot be used with TRANSACTIONAL_SNAPSHOT atomicity
mode
at
org.apache.ignite.i
Hi Ilya,
It'd better if this was mentioned in Ignite Doc.
It seems very limited if MVCC only supports the Ignite native persistence.
Yes, supporting MVCC in 3rd party persistence is challenging. However, do
we really need MVCC when the data from Cache (where MVCC already enabled) is
ready t
Can some one comments on the following questions in my previous post?
4. fact_purhcase_line, invoice and invoice line via factLineId and InvoiceID
do not work, please see annotation below
public class InvoiceLineKey {
/** Primary key. */
private long id;
/** Foreign key to fact
1. why do we need the storage (whether native or 3rd party)? I need the
storage because 1) down time for production deployment. 2) the data in the
cache may be crashed and All ignite clusters are completed down (sorry)
2. So I need a storage to store the data that have been committed when
trans
Hi All,
Adding new primitive type columns to the existing tables (table has data) in
Cassandra causes Ignite to raise an exception (see below) in Ignite 2.7.0 or
2.8.0 nightly build when loading the data from Cassandra into Ignite Cache
store. This works before Ignite 2.6, and even
apache-ignite
The issue was created in Ignite Jira
(https://issues.apache.org/jira/browse/IGNITE-11523). I don't think that we
need a reproducer. Instead I point out the implementation logic in the java
class, and the reasons. The previous implementation (2.6) was correct, and
the expected behavior.
--
Se
30 matches
Mail list logo
