Hi,
I think that you are able to use only one storage for a cache: 3d Party
Persistence or Native Persistence.
Did you update the class name in xml configuration [1]?
Did you restart all nodes after updating jar-files?
If you did, could you share a small proje
Subash,
This is weird, I'm doing exactly the same and not able to reproduce the
issue. Can you share your whole test so that I can run it as-is?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Val, I am using ignite 2.3
Have a simple java Main method that has following
1. dataStorageConfig.set(dataRegionConfig)
2. ignitconfig.setDataStorageConfig(dataStorageConfig)
3. IgniteConfig.setDiscoverySpi(spi)
4.Ignition.start(igniteConfig)
5. CacheConfiguration cc = buildFromDataRegion(
Hi,
1) You can somehow signal it from your application where you invoke
loadCache method or from CacheStore implementation
2) loadCache is sync method and when it will be finished, all preloading
will be finished on all nodes
3) You can listen to the topology changes and check count of the node
Hi
Network storages like EBS or EMC XTREMIO work really good with Ignite,
however, NFS isn't the best from a performance point of view, it's something
that should be tested.
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Paulus,
Replicate cache is supposed to have relatively small size because it can't
be scale beyond min(nodes.ram), at least it was so before persistence was
implemented.
With a persistence that appears in ignite 2+ it now makes sense.
However, you should send your proposal to dev list instead
Hi,
Could you please send us a reproducer that can be run locally?
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi András,
The described behavior doesn't sound Ok.
Could you please send us a reproducer for this that can be run locally?
Thanks,
Mike.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
we have two nodes server and client
we are using ignite cachestore and native persistence till now worked fine.
But we have changed the cache store package
.i.e previously cache store implementation classes and cachestore factory
classes are in same package
In Existing:
com.organiz
Hello again!
Also, I think, to use SQL you will need to declare either QueryEntities or
Indexed Types, as in
cacheConfig.setIndexedTypes(VisitorKey.class, Test.class) <-- Key, Value
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
You should map VisitorKey's fields with @QuerySqlField too, after which you
will notice the problem that you're having same fields in both key type and
value type.
As far as my understanding goes, fields should not repeat in key type and
value type. Some fields may go to one class or the o
Nobody tried NFS storage with Ignite ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I have a problem to create proper Affinity Key. I have numerous events per
visitor in my cache, so my goal is to set VisitorId to be my affinity key,
which is defined as composite key in the VisitorKey class and later on pass
to the cacheConfiguration as cache Key.
Cache is created, however ca
Hi,
You could try to use igniteCache.putAll for write batches by 1000 entries.
Use following script in PostgresDBStore#writeAll method to put data into
the database:
String sqlString = "INSERT INTO test(val) VALUES (:val1)(:val2)(:val3);";
2018-03-14 11:58 GMT+03:00 :
> Hi,
>
> I try to use Ig
Hi,
I try to use Ignite to integrate with PostgreSQL.
And I use “atop” to monitor the data write to PostgreSQL.
Then observed that the writing speed is 1 MB per second.
This performance is not really good. Below is my configuration and code. Please
help me to improve it.
Thanks.
There is my cache
Hi,
Just as exception says, there is no 'endpointAddress' property
in ClientConnectorConfiguration. Instead there are three properties:
host, port and portRange.
By some reason, there was a mistake in Readme.io. I'm going to fix
it asap.
Best Regards,
Igor
On Wed, Mar 14, 2018 at 9:08 AM, Navee
16 matches
Mail list logo