ratadepally opened a new issue, #11399:
URL: https://github.com/apache/ignite/issues/11399
Hi,
We are new to Ignite and currently working on a use case to run it in
cluster mode with 5 nodes for High Availability.
Below is a sample Cache template configuration with BinaryConfiguration that
we are using for the use case.
**<property name="binaryConfiguration">
<bean class="org.apache.ignite.configuration.BinaryConfiguration">
<property name="nameMapper">
<bean
class="org.apache.ignite.binary.BinaryBasicNameMapper">
<property name="simpleName" value="true"/>
</bean>
</property>
</bean>
</property>
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="myCacheTemplate*"/>
<property name="cacheMode" value="PARTITIONED"/>
<property name="atomicityMode" value="TRANSACTIONAL"/>
<property name="backups" value="2"/>
<property name="rebalanceMode" value="SYNC"/>
<property name="writeSynchronizationMode"
value="FULL_SYNC"/>
<property name="partitionLossPolicy"
value="READ_ONLY_SAFE"/>
<property name="readThrough" value="true"/>
<property name="writeThrough" value="true"/>
<property name="statisticsEnabled" value="true"/>
<property name="cacheStoreFactory">
<bean
class="org.apache.ignite.cache.store.jdbc.CacheJdbcBlobStoreFactory">
<property name="dataSourceBean"
value="postgresDataSource"/>
<property name="createTableQuery"
value="create table if not exists ENTRIES (akey bytea primary key, val bytea)"/>
</bean>
</property>
</bean>
</list>
</property>**
With **CacheJdbcBlobStore** configuration we are required to add the
**KEY_TYPE** and **VALUE_TYPE** model classes on to the server manually and do
a redeployment every time there is a model class change.
In real time we have Highly Transactional data and need Ignite cluster to be
**Highly Available** all the time.
Below are the current steps we are following for this deployment.
1. Whenever there is a model change we are bringing down 1 Node at a time
with current 5 Node cluster and updating the Model Jars manually and restarting
the node as there is no **Hot Reload** option for Ignite. During this process
will there be any impact on the cache backup data which resides on different
nodes?
2. How to avoid a deployment/redeployment for such frequent model changes to
make sure that Ignite remains Highly available?
3. Does Ignite provides any recommendations or suggestions for such
scenarios? Any help will be greatly appreciated.
Thanks in advance
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
