ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arseny Kovalchuk <arseny.kovalc...@synesis.ru>
Subject Re: [2.4.0] Cluster unrecoverable after node failure
Date Fri, 23 Mar 2018 10:35:31 GMT
Yes it can be set in a configuration file. You can do it like in the
example below (please do not just copy-paste, put your own values for
properties). Check your configuration file and find a bean with
class org.apache.ignite.configuration.IgniteConfiguration, then add a
property tag to that bean.

See *consistentId* property, in this example it is set from environment,
but you can provide any string value there like node-a, node-b, etc.

<bean id="igniteConfig" class=
"org.apache.ignite.configuration.IgniteConfiguration">
<!-- <property name="igniteInstanceName" value="#{
systemEnvironment['IGNITE_HOSTNAME'] }" /> -->
<property name="localHost" value="#{ systemEnvironment['IGNITE_POD_IP'] }"/>
<property name="peerClassLoadingEnabled" value="false" />
<property name="metricsLogFrequency" value="0" />
<property name="clientFailureDetectionTimeout" value="#{
systemEnvironment['IGNITE_FAILURE_DETECTION_TIMEOUT']?: 1 * 60 * 1000 }" />
<property name="failureDetectionTimeout" value="#{
systemEnvironment['IGNITE_FAILURE_DETECTION_TIMEOUT']?: 1 * 60 * 1000 }" />
<property name="workDirectory" value="/ignite-work-directory"/>
<property name="consistentId" value="#{
systemEnvironment['IGNITE_CONSISTENT_ID'] }" />
<!-- set pool sizes because in k8s env
Runtime.getRuntime().availableProcessors() returns incorrect value -->
<property name="systemThreadPoolSize" value="8" />
<property name="publicThreadPoolSize" value="8" />
<property name="queryThreadPoolSize" value="8" />
<property name="serviceThreadPoolSize" value="8" />
<property name="stripedPoolSize" value="8" />
<property name="dataStreamerThreadPoolSize" value="8" />
<property name="asyncCallbackPoolSize" value="8" />
<property name="managementThreadPoolSize" value="4" />
<property name="peerClassLoadingThreadPoolSize" value="4" />
<property name="igfsThreadPoolSize" value="4" />
<property name="utilityCachePoolSize" value="4" />
<property name="connectorConfiguration">
<bean class="org.apache.ignite.configuration.ConnectorConfiguration">
<property name="selectorCount" value="4" />
<property name="threadPoolSize" value="8" />
</bean>
</property>

<property name="gridLogger">
<bean class="org.apache.ignite.logger.slf4j.Slf4jLogger" />
</property>

<property name="dataStorageConfiguration" ref="dataStorageConfiguration" />

<!-- depends on profile! -->
<property name="discoverySpi" ref="discoverySpi" />
<property name="communicationSpi" ref="communicationSpi" />
</bean>


Arseny



​
Arseny Kovalchuk

Senior Software Engineer at Synesis
skype: arseny.kovalchuk
mobile: +375 (29) 666-16-16
​LinkedIn Profile <http://www.linkedin.com/in/arsenykovalchuk/en>​

On 23 March 2018 at 12:45, joseheitor <jose@heitorprojects.com> wrote:

> Hi Arseny,
>
> Can this be set in the configuration file for each node? (like a property?)
>
> Our application is aiming (currently) to use Ignite purely as a
> distributed,
> persistent and cached, fault-tolerant SQL database through the Client JDBC
> driver. It does/must not instantiate (depend on) any Ignite library
> components directly in the application code.
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Mime
View raw message