Hello!

Looks overall correct.

Regards,
-- 
Ilya Kasnacheev


чт, 14 янв. 2021 г. в 11:43, xmw45688 <xw...@procurant.com>:

> 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-instantiated.
> So I need to pre-decide dynamicConfigurationReload value. Modifying
> dynamicConfigurationReload value later won't take effect at dynamically.
>
> <bean class="org.apache.ignite.configuration.CacheConfiguration">
>                 <property name="name" value="Uom"/>
>                 <property name="atomicityMode" value="TRANSACTIONAL"/>
>                 <property name="cacheMode" value="REPLICATED"/>
>                 <property name="readThrough" value="true"/>
>                 <property name="writeThrough" value="false"/>
>                 <property name="sqlSchema" value="catalog"/>
>
>                 <property name="cacheStoreFactory">
>                         <bean
> class="org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory">
>                                 <property name="dynamicConfigurationReload"
> value ="true" />
>                                 <property name="dataSource"
> ref="cassandra"/>
>                                 <property name="persistenceSettingsBean"
> value="catalog_uom_persistence_settings"></property>
>                         </bean>
>                 </property>
> </bean>
>
> 2) Yes, the similar implementation is applied to data source.  Thanks for
> remaindering.
>
> 3) given dynamicConfigurationReload is only loaded once at very first time
> of creating cache, I'm thinking we don't use dynamicConfigurationReload,
> instead implement the following
> 3.1) read data source from the xml config file each time an Ignite server
> starts, if data source is not null, use the latest one, else use the
> existing one.
> 3.2) read persistenceSettingsBean from xml config file each time an Ignite
> server starts, if persistence settings are not null, use the latest one,
> else using the existing one.
> 3.3) obviously, this is aggressive.  But how many times do we start/restart
> an Ignite instance.  The performance impacts are minimal.
>
> if you think it's okay, I start implementing and testing.
> Let me know if you have any other suggestions/recommendations.
>
> Appreciated your help.
> Xinmin
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to