Re: Failed to wait for initial partition map exchange

[Justin Ji]

Ilya - 

Thank for your reply.

Is there any configuration can help us reduce the WAL time in 2.6.0.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Unsubscribe

[Viraj Rathod]

Unsubscribe

On Sat, 19 Jan 2019 at 9:33 AM, romil kothawade 
wrote:

-- 
Regards,
Viraj Rathod

unsubscribe

[romil kothawade]

Re: Creating Dataset classNotFound exception

[mahesh76private]

also, in this function, if tableCache is a sql tableCache, will
IgniteBiFunction is correctly executed 

try {
  dataSet = DatasetFactory.createSimpleDataset(ignite, tableCache,
extractor);
} catch (Exception e) {
  e.printStackTrace();
}



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[mahesh76private]

For the moment, I moved my class to server - libs folder
The test program didnt run successfully, but does these errors mean, I am
missing something on server side and would that be fatal

[03:18:28,156][WARNING][pub-#74][BLAS] Failed to load implementation from:
com.github.fommil.netlib.NativeSystemBLAS
[03:18:28,156][WARNING][pub-#74][BLAS] Failed to load implementation from:
com.github.fommil.netlib.NativeRefBLAS



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

part 3 - dead in the water now - notes and questions on configuration and installation of web console for ignite

[Scott Cote]

Part 3 of notes and questions about web console for ignite

Restarted attempt inside BDD 
(https://apacheignite-tools.readme.io/docs/build-and-deploy) of the section 
titled:

Run Ignite Web Console In Development Mode

https://apacheignite-tools.readme.io/docs/build-and-deploy#section-run-ignite-web-console-in-development-mode

=
Items
=

  1.  I downgraded mongodb to 3.4.18  (removed the mongod service corresponding 
to 4.0 and added 3.4.x to the path instead.  Restarted)
  2.  Reran npm install with new mongodb in place.
  3.  Attemped to start npm in the backend.
 *   - observed mongoose connect to the mongod server (console response on 
the mongod terminal)
 *   Saw the "start of the npm" bomb out   I provide in this email both 
console output (from npm) as well as the log file listed in the output

So how do I proceed?

About my environment:

Java
C:\cygwin64\home\scote\ignite\modules\web-console\backend>java -version
java version "1.8.0_192"
Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode)

Ignite r
src of 2.7

Mongo
3.4.18

Npm
Node-v11.6.0-x64.msi

Thanks in advance.

SCott




=
Console output
=
C:\cygwin64\home\scote\ignite\modules\web-console\backend>npm start

> ignite-web-console@2.7.0 start 
> C:\cygwin64\home\scote\ignite\modules\web-console\backend
> node ./index.js

fireUp# INFO  Registered module at 'app\agentSocket.js' as implementation for 
interface 'agent-socket'.
fireUp# INFO  Registered module at 'app\agentsHandler.js' as implementation for 
interface 'agents-handler'.
fireUp# INFO  Registered module at 'app\apiServer.js' as implementation for 
interface 'api-server'.
fireUp# INFO  Registered module at 'app\browsersHandler.js' as implementation 
for interface 'browsers-handler'.
fireUp# INFO  Registered module at 'app\configure.js' as implementation for 
interface 'configure'.
fireUp# INFO  Registered module at 'app\mongo.js' as implementation for 
interface 'mongo'.
fireUp# INFO  Registered module at 'app\mongoose.js' as implementation for 
interface 'mongoose'.
fireUp# INFO  Registered module at 'app\nconf.js' as implementation for 
interface 'nconf'.
fireUp# INFO  Registered module at 'app\routes.js' as implementation for 
interface 'routes'.
fireUp# INFO  Registered module at 'app\schemas.js' as implementation for 
interface 'schemas'.
fireUp# INFO  Registered module at 'app\settings.js' as implementation for 
interface 'settings'.
fireUp# INFO  Registered module at 'errors\index.js' as implementation for 
interface 'errors'.
fireUp# INFO  Registered module at 'middlewares\api.js' as implementation for 
interface 'middlewares:api'.
fireUp# INFO  Registered module at 'middlewares\demo.js' as implementation for 
interface 'middlewares:demo'.
fireUp# INFO  Registered module at 'middlewares\host.js' as implementation for 
interface 'middlewares:host'.
fireUp# INFO  Registered module at 'middlewares\user.js' as implementation for 
interface 'middlewares:user'.
fireUp# INFO  Registered module at 'routes\activities.js' as implementation for 
interface 'routes/activities'.
fireUp# INFO  Registered module at 'routes\admin.js' as implementation for 
interface 'routes/admin'.
fireUp# INFO  Registered module at 'routes\caches.js' as implementation for 
interface 'routes/caches'.
fireUp# INFO  Registered module at 'routes\clusters.js' as implementation for 
interface 'routes/clusters'.
fireUp# INFO  Registered module at 'routes\configuration.js' as implementation 
for interface 'routes/configurations'.
fireUp# INFO  Registered module at 'routes\demo.js' as implementation for 
interface 'routes/demo'.
fireUp# INFO  Registered module at 'routes\domains.js' as implementation for 
interface 'routes/domains'.
fireUp# INFO  Registered module at 'routes\downloads.js' as implementation for 
interface 'routes/downloads'.
fireUp# INFO  Registered module at 'routes\igfss.js' as implementation for 
interface 'routes/igfss'.
fireUp# INFO  Registered module at 'routes\notebooks.js' as implementation for 
interface 'routes/notebooks'.
fireUp# INFO  Registered module at 'routes\profile.js' as implementation for 
interface 'routes/profiles'.
fireUp# INFO  Registered module at 'routes\public.js' as implementation for 
interface 'routes/public'.
fireUp# INFO  Registered module at 'services\Utils.js' as implementation for 
interface 'services/utils'.
fireUp# INFO  Registered module at 'services\activities.js' as implementation 
for interface 'services/activities'.
fireUp# INFO  Registered module at 'services\auth.js' as implementation for 
interface 'services/auth'.
fireUp# INFO  Registered module at 'services\caches.js' as implementation for 
interface 'services/caches'.
fireUp# INFO  Registered module at 'services\clusters.js' as implementation for 
interface 'services/clusters'.
fireUp# INFO  Registered module at 'services\configurations.js' as 
implementation for interface 'services/configurations'.
fireUp# IN

Re: Difference Between Client and Server Ignite Configurations

[Ilya Kasnacheev]

Hello!

You can surely start with such configuration, then maybe your client and
server configurations will diverge as development goes by.

Regards,
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 18:07, nitin dharrao :

> Hello following is my Ignite Configuration for Client App. However the same
> configuration also exists for Server Apache Ignite Node except one line (
> igniteConfiguration.setClientMode(true);)...
>
> Is this correct? My idea is to create an instance running on GCP kubernetes
> and my Business App which has the following configuration would basically
> be
> creating the cache on GCP Kubernetes cluster.
>
> Both Ignite and business app will be deployed on GCP Kubernetes. Please let
> me know if following what I should have for Ignite Configuration in my
> Business App.
>
>
> @Bean
> public Ignite igniteInstance(@Qualifier("igniteConfiguration") final
> IgniteConfiguration igniteConfiguration) {
> logger.info(".IGNITE IS STARTING..
> ");
> return Ignition.start(igniteConfiguration);
> }
>
> @Bean("igniteConfiguration")
> public IgniteConfiguration igniteConfiguration(
> @Value("${ignite.instance.name}") String instanceName,
> @Qualifier("cacheConfiguration") CacheConfiguration TapBillingCachedData> cacheConfiguration
> ) {
> logger.info("Creating IGNITE-CONFIGURATION Bean for instance
> {%s}",
> instanceName);
>
> final IgniteConfiguration igniteConfiguration = new
> IgniteConfiguration();
> igniteConfiguration.setGridLogger(new Slf4jLogger());
> igniteConfiguration.setIgniteInstanceName(instanceName); // Setting
> some custom name for the node.
> igniteConfiguration.setPeerClassLoadingEnabled(true); // Enabling
> peer-class loading feature.
> igniteConfiguration.setCacheConfiguration(cacheConfiguration);
> igniteConfiguration.setClientMode(true);
> return igniteConfiguration;
> }
>
>
> @Profile("!local")
> @Bean("tcpDiscoverySpi")
> public TcpDiscoverySpi tcpDiscoverySpi(
> @Value("${google.cloud.project.namespace}")
> String google_cloud_project_namespace,
> @Value("${google.cloud.service.name}")
> String google_cloud_service_name,
> @Qualifier("igniteConfiguration") final IgniteConfiguration
> igniteConfiguration
> ) {
> logger.info("Creating TCP-DISCOVERY-SPI bean");
> final TcpDiscoverySpi spi = new TcpDiscoverySpi();
> final TcpDiscoveryKubernetesIpFinder ipFinder = new
> TcpDiscoveryKubernetesIpFinder();
> logger.info("NAME SPACE IS -> " + google_cloud_project_namespace);
> ipFinder.setNamespace(google_cloud_project_namespace);
> //ipFinder.setServiceName(google_cloud_service_name);
> spi.setIpFinder(ipFinder);
> igniteConfiguration.setDiscoverySpi(spi);
> return spi;
> }
>
>
> @Bean("cacheConfiguration")
> public CacheConfiguration
> cacheConfiguration(
> @Value("${ignite.cache.name}") String cacheName
> ){
> final CacheConfiguration ccfg = new CacheConfiguration(cacheName);
> ccfg.setIndexedTypes(String.class, TapBillingCachedData.class);
> return ccfg;
> }
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Thin client and Ignite Repository

[Ilya Kasnacheev]

Hello!

I don't think IgniteRepository will support IgniteClient.

IgniteClient is not a drop-in replacement for Ignite thick node and
therefore all integrations usually expect regular Ignite.

Regards.
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 20:27, nitin dharrao :

> https://apacheignite.readme.io/v2.7/docs/java-thin-client
>
> I followed the above link to connect to remote Apache Ignite server Node.
> However, am receiving the following error. The simple reason for this error
> is it needs to execute config file that has @EnableIgniteRepositories.
> However, my controller has  @Autowired
> private TapBillingRepository repository; which takes the precedence and
> so the following error.
>
> I am though not sure if IgniteClient will enable the repositories.
>
> @Bean
> public IgniteClient igniteClient(
> @Value("${ignite.remote.url}") String urlAddress
> ) {
> logger.info("Ignite Remote URL is {%s}", urlAddress);
> final ClientConfiguration cfg = new
> ClientConfiguration().setAddresses(urlAddress);
> return Ignition.startClient(cfg);
> }
>
>
> --- Error am receiving as shown below -
>
> Exception encountered during context initialization - cancelling refresh
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name 'tapBillingIgniteCacheImpl': Unsatisfied
> dependency expressed through field 'logger'; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'igniteConfig': Unsatisfied dependency expressed
> through field 'repository'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean
> with name 'tapBillingRepository': Invocation of init method failed; nested
> exception is class org.apache.ignite.IgniteException: Failed to initialize
> Ignite repository factory. Ignite instance or IgniteConfiguration or a path
> to Ignite's spring XML configuration must be defined in the application
> configuration
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Creating Dataset classNotFound exception

[Ilya Kasnacheev]

Hello!

I'm not sure that Peer Class Loading will load main-class.

So make sure that your IgniteBiFunction is a static class. Lambdas are
notorious for not being static, carrying whole outer class with them when
they are serialized. So yes, you should.

Regards,
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 19:55, mahesh76private :

> I have enabled peer class loading all my clients and servers.
> Should I be pulling IgniteBiFunction into a separate class and try?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Search on a composite key

[Ilya Kasnacheev]

Hello!

SQL can filter (and query) fields from both keys and values and there
should be examples on readme.io.

Just make sure you have a secondary index on this field.

Regards,
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 19:08, ihorps :

> hi Mikhail
>
> Thank you for your response.
>
> Yes, I've read the documentation (provided in your link) before I posted
> the
> message here but somehow I understood that there are two ways to search on
> composite key:
> 1. Scan Queries - does the job but doesn't look efficient enough such as it
> we have to iterate through all keys to match some condition on that
> composed
> key
> 2. SQL Queries (https://apacheignite-sql.readme.io/docs/java-sql-api) -
> does
> the job but example here contains only search on value object. And if I
> need
> to search through keys I need to put a reference to a key for there value
> objects (this is what I want to avoid for now). Something like it was
> described here -
>
> http://apache-ignite-users.70518.x6.nabble.com/Composite-key-as-Ignite-key-and-its-should-be-queryable-td24313.html.
>
>
> So I thought if there is an option in Apache Ignite where I can run on a
> cache some predicate for its composite keys, which on their own could be
> indexed on some property to gain a performance against linear iteration
> through all of them.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Cache updates slow on Linux Vs Windows

[Ilya Kasnacheev]

Hello!

I was running this case on Linux and it took 2 seconds (no PME messages).

It was not my intent to compare Windows vs Linux performance, there are
just known issues for Apache Ignite discovery on Windows where it takes
much longer to scan ports. However, I think the bottom of it is just slow
I/O. Ignite has to write a lot of data even for empty caches (1024
partitions, a few files for each) so it can take prolonged time with slow
I/O.

Regards.
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 13:39, ihorps :

> hi all
>
> I don't have exact example but I remember that I was running once my
> prototype ignite app on Windows (all other cases were running under Ubuntu)
> and I recognized that it was "slightly" faster.
> I did give too much attention to it by thinking that was just my personal
> feel and I could be mistaken. But seems to be I'm not alone here...
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

part 2 - notes and questions on configuration and installation of web console for ignite

[Scott Cote]

Part 2 of notes and questions about web console for ignite
=
Items
=

Item 1.  Found more npm issues while performing "Run Ignite Web Console In 
Development Mode" of BDD referenced in Part 1

Item 2. <<>>>  It seems that the latest version of community 
mongodb is NOT supported by Ignite.  Maybe a mongoose problem (see item from 
part 1 about upgrading mongoose)???

In the meantime, I'll downgrade mongodb to 3.4.x 

=
Details
=

Detail 1 -> 1

c:\cygwin64\home\scote\ignite\modules\web-console\backend>npm install 
--no-optional
added 31 packages from 292 contributors and audited 6667 packages in 4.948s
found 10 vulnerabilities (6 low, 3 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

c:\cygwin64\home\scote\ignite\modules\web-console\backend>

c:\cygwin64\home\scote\ignite\modules\web-console\backend>npm audit fix
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 
(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 
fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: 
{"os":"win32","arch":"x64"})

up to date in 4.475s
fixed 0 of 10 vulnerabilities in 6667 scanned packages
  3 vulnerabilities required manual review and could not be updated
  3 package updates for 7 vulns involved breaking changes
  (use `npm audit fix --force` to install breaking changes; or refer to `npm 
audit` for steps to fix these manually)

c:\cygwin64\home\scote\ignite\modules\web-console\backend>

Detail 2 -> 2

c:\cygwin64\home\scote\ignite\modules\web-console\backend>npm start

> ignite-web-console@2.7.0 start 
> c:\cygwin64\home\scote\ignite\modules\web-console\backend
> node ./index.js

fireUp# INFO  Registered module at 'app\agentSocket.js' as implementation for 
interface 'agent-socket'.
fireUp# INFO  Registered module at 'app\agentsHandler.js' as implementation for 
interface 'agents-handler'.
fireUp# INFO  Registered module at 'app\apiServer.js' as implementation for 
interface 'api-server'.
fireUp# INFO  Registered module at 'app\browsersHandler.js' as implementation 
for interface 'browsers-handler'.
fireUp# INFO  Registered module at 'app\configure.js' as implementation for 
interface 'configure'.
fireUp# INFO  Registered module at 'app\mongo.js' as implementation for 
interface 'mongo'.
fireUp# INFO  Registered module at 'app\mongoose.js' as implementation for 
interface 'mongoose'.
fireUp# INFO  Registered module at 'app\nconf.js' as implementation for 
interface 'nconf'.
fireUp# INFO  Registered module at 'app\routes.js' as implementation for 
interface 'routes'.
fireUp# INFO  Registered module at 'app\schemas.js' as implementation for 
interface 'schemas'.
fireUp# INFO  Registered module at 'app\settings.js' as implementation for 
interface 'settings'.
fireUp# INFO  Registered module at 'errors\index.js' as implementation for 
interface 'errors'.
fireUp# INFO  Registered module at 'middlewares\api.js' as implementation for 
interface 'middlewares:api'.
fireUp# INFO  Registered module at 'middlewares\demo.js' as implementation for 
interface 'middlewares:demo'.
fireUp# INFO  Registered module at 'middlewares\host.js' as implementation for 
interface 'middlewares:host'.
fireUp# INFO  Registered module at 'middlewares\user.js' as implementation for 
interface 'middlewares:user'.
fireUp# INFO  Registered module at 'routes\activities.js' as implementation for 
interface 'routes/activities'.
fireUp# INFO  Registered module at 'routes\admin.js' as implementation for 
interface 'routes/admin'.
fireUp# INFO  Registered module at 'routes\caches.js' as implementation for 
interface 'routes/caches'.
fireUp# INFO  Registered module at 'routes\clusters.js' as implementation for 
interface 'routes/clusters'.
fireUp# INFO  Registered module at 'routes\configuration.js' as implementation 
for interface 'routes/configurations'.
fireUp# INFO  Registered module at 'routes\demo.js' as implementation for 
interface 'routes/demo'.
fireUp# INFO  Registered module at 'routes\domains.js' as implementation for 
interface 'routes/domains'.
fireUp# INFO  Registered module at 'routes\downloads.js' as implementation for 
interface 'routes/downloads'.
fireUp# INFO  Registered module at 'routes\igfss.js' as implementation for 
interface 'routes/igfss'.
fireUp# INFO  Registered module at 'routes\notebooks.js' as implementation for 
interface 'routes/notebooks'.
fireUp# INFO  Registered module at 'routes\profile.js' as implementation for 
interface 'routes/profiles'.
fireUp# INFO  Registered module at 'routes\public.js' as implementation for 
interface 'routes/public'.
fireUp# INFO  Registered module at 'services\Utils.js' as implementation for 
interface 'services/utils'.
fireUp# INFO  Registered module at 'services\activities.js' as implementation 
for interface 'services/activities'.
fireUp# INFO  Registered module at 'services\auth.js' as implementation for 
interface 'services/auth'.
fireUp# INFO  Registered module at 'services\ca

notes and questions on configuration and installation of web console for ignite

[Scott Cote]

Am going through the manual installation and implementation of the Ignite Web 
Console.
This is Part 1 of a series of notes that I’m making….

Throughout this set of items (questions and notes), I’m referencing the “Build 
and Deploy“ document (BDD) 
https://apacheignite-tools.readme.io/docs/build-and-deploy
=
Items
=

Item 1:
In the prerequisites section of BDD, we are instructed to run npm from 
$IGNITE_HOME.   Is this the ignite home of the exploded source tree, or the 
ignite home of the unzipped/extracted binary (released) instances ( - for 
example, I downloaded a binary and unzipped it/exploded the tar/gz).

Currently, I’m running npm from the exploded source tree and NOT my exploded 
binary – which is what my env variable $IGNITE_HOME points to.


Item 2:
The machine that I need to deploy the web console into is sitting behind a very 
grandiose firewall/av setup.  Using GIT/Maven/NPM to pull in dependencies for a 
build on that machine is not supportable.   I am able to build somewhere else 
….  Want to package the outcome and deploy it to the super secure machine.   
Maybe create a docker container….   Is there a docker container with web 
console already configured?   If not, and if I’m allowed, how do I contribute a 
docker container of this setup?  I think I can sell to my management that more 
eyeballs on a crafted docker container – generic without any of our proprietary 
work – would be good over all.  We would all benefit.

Item 3:
While running the npm installer for the backend (prerequisites of BDD), I 
noticed desupport notices from:

  *   Mockgoose
  *   Simple-bufferstream
  *   Babel
  *   Minimatch
  *   Circular-json
  *   Cryptiles
  *   Boom
  *   Hoek
  *
I will include the npm output below as Detail 1 -> 3  (notation: 1 refers to 
the first detail – 1, and 3 refers to this item of concern)

Item 4:
Npm audit revealed a couple of critical warnings (among others).   So that I 
can address my security team accurately (considering this IS an open source 
project)  Are the sources of the warnings (listed in Detail 2 -> 4) on an 
immediate roadmap to be corrected in the next release of Ignite.

Can I fix in my install by running “npm audit fix” ?  I’m not a nodejs guy, so 
I don’t know if the “fix” could be backported to the source and then given back 
to ignite community.  I will run npm fix, just don’t know if I can give outcome 
back.

Item 5:
Ran the audit fix for backend of BDD. See 3 -> 5 for the outcome on the screen.

Item 6:
While running the npm installer for the frontend (prerequisites of BDD), I 
noticed desupport and problem notices from:

  *   samsam
  *   text-encoding
  *   circular-json
  *   browserslist
  *   node-uuid
  *   hoek
  *   cryptiles
  *   boom
  *   socks
  *   mailcomposer
  *   buildmail
  *   uws

I will include the npm output below as Detail 4 -> 6

Item 7:
Again - Npm audit revealed a couple of critical warnings (among others).   So 
that I can address my security team accurately (considering this IS an open 
source project)  Are the sources of the warnings (listed in Detail 5 -> 7) on 
an immediate roadmap to be corrected in the next release of Ignite.

Can I fix in my install by running “npm audit fix” ?  I’m not a nodejs guy, so 
I don’t know if the “fix” could be backported to the source and then given back 
to ignite community.  I will run npm fix, just don’t know if I can give outcome 
back.


Item 8:
Ran the audit fix for backend of BDD. See 6 -> 8 for the outcome on the screen.


===
Details
===
Detail 1-> 3

c:\cygwin64\home\scote\ignite\modules\web-console\backend>npm install 
--no-optional
npm WARN deprecated mockgoose@6.0.8: Mockgoose is no longer actively 
maintained, consider using mongodb-memory-server
npm WARN deprecated scmp@1.0.2: scmp v2 uses improved core crypto comparison 
since Node v6.6.0
npm WARN deprecated simple-bufferstream@1.0.0: no longer maintained
npm WARN deprecated babel-preset-latest@6.24.1: We're super 😸  excited that 
you're trying to use ES2017+ syntax, but instead of making more yearly presets 
😭 , Babel now has a better preset that we recommend you use instead: npm 
install babel-preset-env --save-dev. preset-env without options will compile 
ES2015+ down to ES5 just like using all the presets together and thus is more 
future proof. It also allows you to target specific browsers so that Babel can 
do less work and you can ship native ES2015+ to user 😎 ! We are also in the 
process of releasing v7, so please give 
http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out 
in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter 
@babeljs for news on Babel, join slack.babeljs.io for discussion/development 
and help support the project at opencollective.com/babel
npm WARN deprecated babel-preset-es2017@6.24.1: 🙌  Thanks for using Babel: we 
recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated babel-preset-es201

Thin client and Ignite Repository

[nitin dharrao]

https://apacheignite.readme.io/v2.7/docs/java-thin-client

I followed the above link to connect to remote Apache Ignite server Node.
However, am receiving the following error. The simple reason for this error
is it needs to execute config file that has @EnableIgniteRepositories.
However, my controller has  @Autowired
private TapBillingRepository repository; which takes the precedence and
so the following error. 

I am though not sure if IgniteClient will enable the repositories.

@Bean
public IgniteClient igniteClient(
@Value("${ignite.remote.url}") String urlAddress
) {
logger.info("Ignite Remote URL is {%s}", urlAddress);
final ClientConfiguration cfg = new
ClientConfiguration().setAddresses(urlAddress);
return Ignition.startClient(cfg);
}


--- Error am receiving as shown below -

Exception encountered during context initialization - cancelling refresh
attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'tapBillingIgniteCacheImpl': Unsatisfied
dependency expressed through field 'logger'; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name 'igniteConfig': Unsatisfied dependency expressed
through field 'repository'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'tapBillingRepository': Invocation of init method failed; nested
exception is class org.apache.ignite.IgniteException: Failed to initialize
Ignite repository factory. Ignite instance or IgniteConfiguration or a path
to Ignite's spring XML configuration must be defined in the application
configuration



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[mahesh76private]

I have enabled peer class loading all my clients and servers. 
Should I be pulling IgniteBiFunction into a separate class and try?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Search on a composite key

[ihorps]

hi Mikhail

Thank you for your response. 

Yes, I've read the documentation (provided in your link) before I posted the
message here but somehow I understood that there are two ways to search on
composite key:
1. Scan Queries - does the job but doesn't look efficient enough such as it
we have to iterate through all keys to match some condition on that composed
key
2. SQL Queries (https://apacheignite-sql.readme.io/docs/java-sql-api) - does
the job but example here contains only search on value object. And if I need
to search through keys I need to put a reference to a key for there value
objects (this is what I want to avoid for now). Something like it was
described here -
http://apache-ignite-users.70518.x6.nabble.com/Composite-key-as-Ignite-key-and-its-should-be-queryable-td24313.html.
 

So I thought if there is an option in Apache Ignite where I can run on a
cache some predicate for its composite keys, which on their own could be
indexed on some property to gain a performance against linear iteration
through all of them.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite in GCP cloud

[nitin dharrao]

Thank you Mikhail.

How the following configuration would look like in Kubernetes cluster?
ClientConfiguration cfg = new
ClientConfiguration().setAddresses("127.0.0.1:10800");

GCP Kube Cluster will have two PODs which are not public IPs. We can create
Kubernetes Load Balancer to manage the traffic on those PODs. Do I have to
provide Ignite Load Balancer (Service) URL in the above configuration?





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Search on a composite key

[Mikhail]

Hi 

Please read this doc:
https://apacheignite.readme.io/docs/cache-queries
this section describes exactly what you want.

Thanks,
Mike.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite_backup_restore_query

[Mikhail]

I think you didn't copy the work directory, it can configured by
IgniteConfiguration, by default it locates in $IGNITE_HOME/work





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite in GCP cloud

[Mikhail]

>1. 

you can use docker file from ignite kubernetus module:
https://github.com/apache/ignite/blob/7b9cd0711b2ab16b8635cdaa588bfb3c03915f3c/modules/kubernetes/config/Dockerfile

it's open source, all artifacs are in the module, so you it to build and
host image locally.
>2.

You use too old documentation, please use this one:
https://apacheignite.readme.io/v2.7/docs/kubernetes-deployment
 it has easy step by set instruction for GCE.

>3.

no, Ignition.setClientMode(true) says to create client node instead of the
server, however, it will be a thick client. Please refer to the following
doc, to create thin client properly:

https://apacheignite.readme.io/v2.7/docs/java-thin-client

Thanks,
Mike.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Difference Between Client and Server Ignite Configurations

[nitin dharrao]

Hello following is my Ignite Configuration for Client App. However the same
configuration also exists for Server Apache Ignite Node except one line (
igniteConfiguration.setClientMode(true);)... 

Is this correct? My idea is to create an instance running on GCP kubernetes
and my Business App which has the following configuration would basically be
creating the cache on GCP Kubernetes cluster. 

Both Ignite and business app will be deployed on GCP Kubernetes. Please let
me know if following what I should have for Ignite Configuration in my
Business App. 


@Bean
public Ignite igniteInstance(@Qualifier("igniteConfiguration") final
IgniteConfiguration igniteConfiguration) {
logger.info(".IGNITE IS STARTING..
");
return Ignition.start(igniteConfiguration);
}

@Bean("igniteConfiguration")
public IgniteConfiguration igniteConfiguration(
@Value("${ignite.instance.name}") String instanceName,
@Qualifier("cacheConfiguration") CacheConfiguration cacheConfiguration
) {
logger.info("Creating IGNITE-CONFIGURATION Bean for instance {%s}",
instanceName);

final IgniteConfiguration igniteConfiguration = new
IgniteConfiguration();
igniteConfiguration.setGridLogger(new Slf4jLogger());
igniteConfiguration.setIgniteInstanceName(instanceName); // Setting
some custom name for the node.
igniteConfiguration.setPeerClassLoadingEnabled(true); // Enabling
peer-class loading feature.
igniteConfiguration.setCacheConfiguration(cacheConfiguration);
igniteConfiguration.setClientMode(true);
return igniteConfiguration;
}


@Profile("!local")
@Bean("tcpDiscoverySpi")
public TcpDiscoverySpi tcpDiscoverySpi(
@Value("${google.cloud.project.namespace}")
String google_cloud_project_namespace,
@Value("${google.cloud.service.name}")
String google_cloud_service_name,
@Qualifier("igniteConfiguration") final IgniteConfiguration
igniteConfiguration
) {
logger.info("Creating TCP-DISCOVERY-SPI bean");
final TcpDiscoverySpi spi = new TcpDiscoverySpi();
final TcpDiscoveryKubernetesIpFinder ipFinder = new
TcpDiscoveryKubernetesIpFinder();
logger.info("NAME SPACE IS -> " + google_cloud_project_namespace);
ipFinder.setNamespace(google_cloud_project_namespace);
//ipFinder.setServiceName(google_cloud_service_name);
spi.setIpFinder(ipFinder);
igniteConfiguration.setDiscoverySpi(spi);
return spi;
}


@Bean("cacheConfiguration")
public CacheConfiguration
cacheConfiguration(
@Value("${ignite.cache.name}") String cacheName
){
final CacheConfiguration ccfg = new CacheConfiguration(cacheName);
ccfg.setIndexedTypes(String.class, TapBillingCachedData.class);
return ccfg;
}




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: building and running from source

[Mikhail]

Hi Scott,

I think you need this doc: 
https://github.com/apache/ignite/blob/33ad0ad84a25a0d65ba408accfb1429cb96ff840/DEVNOTES.txt

Let me know if it isn't sufficient to make the full build, we will fix it.

thanks,
Mike.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transactional cache in Atomic mode

[Mikhail]

>1)

Batching always works better, however, I would benchmark single update vs
batch update to prove this.

>Would ignite itself make the implicit transaction /only if/ the explicit
JAVA API for transaction has not been called? 

Right, if there's no definition for the transaction, there will be an
implicit transaction, otherwise, explicit one will be used.

>2)
ignite uses entry lock level, so in your case, there should be no crossing
between transactions, so I don't see the reason why transaction should fail.
Do you think you can share reproducer or at least full logs with
stacktraces?

Thanks,
Mike.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Data streamer has been closed.

[Ilya Kasnacheev]

Hello!

I can observe this problem with this reproducer on 2.7. I will try to
investigate more and file a ticket.

Regards,+
-- 
Ilya Kasnacheev


чт, 17 янв. 2019 г. в 16:14, yangjiajun <1371549...@qq.com>:

> Hello.
>
> Please try this loop:
> for(int i=0;i<10;i++){
> System.out.println(i);
> initData();
> overwriteData();
> }
>
> And here is my config file:
> example-default12.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default12.xml>
>
>
> It is harder to reproduce this issue in 2.7 than 2.6.But the exception does
> appear.
>
>
> ilya.kasnacheev wrote
> > Hello!
> >
> > I have ran your code several times and not encountered this problem. Can
> > you make a new reproducer which will show it (semi)reliably?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 17 янв. 2019 г. в 05:18, yangjiajun <
>
> > 1371549332@
>
> >>:
> >
> >> Hello.
> >>
> >> Thanks for reply.Unfortunately,I still get the exception after running
> my
> >> test on 2.7  for several times.
> >>
> >>
> >> ilya.kasnacheev wrote
> >> > Hello!
> >> >
> >> > I can reproduce this problem, but then again, it does not seem to
> >> > reproduce
> >> > on 2.7. Have you considered upgrading?
> >> >
> >> > Regards,
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > ср, 16 янв. 2019 г. в 14:14, yangjiajun <
> >>
> >> > 1371549332@
> >>
> >> >>:
> >> >
> >> >> Hello.
> >> >>
> >> >> I do  test on a ignite 2.6 node with persistence enabled and get an
> >> >> exception:
> >> >>
> >> >>  Exception in thread "main" java.sql.BatchUpdateException: class
> >> >> org.apache.ignite.IgniteCheckedException: Data streamer has been
> >> closed.
> >> >> at
> >> >>
> >> >>
> >>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1017)
> >> >> at java.lang.Thread.run(Unknown Source)
> >> >>
> >> >> Here is my test code:
> >> >>
> >> >> import java.sql.Connection;
> >> >> import java.sql.DriverManager;
> >> >> import java.sql.PreparedStatement;
> >> >> import java.sql.SQLException;
> >> >> import java.util.Properties;
> >> >>
> >> >> /**
> >> >>  * test insert data in streaming mode
> >> >>  * */
> >> >> public class InsertStreamingMode {
> >> >>
> >> >> private static Connection conn;
> >> >>
> >> >> public static void main(String[] args) throws Exception {
> >> >>
> >> >> initialize();
> >> >>
> >> >> close();
> >> >> }
> >> >>
> >> >> public static void close() throws Exception {
> >> >> conn.close();
> >> >> }
> >> >>
> >> >> public static void initialize() throws Exception {
> >> >>
> >> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> >> >> final String dbUrl =
> >> >>
> >> >>
> >>
> "jdbc:ignite:thin://ip:port;lazy=true;skipReducerOnUpdate=true;replicatedOnly=true";
> >> >> final Properties props = new Properties();
> >> >> conn = DriverManager.getConnection(dbUrl, props);
> >> >> initData();
> >> >> overwriteData();
> >> >> }
> >> >>
> >> >> private static void initData() throws SQLException{
> >> >>
> >> >> long start=System.currentTimeMillis();
> >> >> conn.prepareStatement("SET STREAMING ON
> >> ALLOW_OVERWRITE
> >> >> ON").execute();
> >> >>
> >> >> String sql="insert INTO  city1(id,name,name1)
> >> >> VALUES(?,?,?)";
> >> >> PreparedStatement ps=conn.prepareStatement(sql);
> >> >> for(int i=0;i<160;i++){
> >> >> String s1=String.valueOf(Math.random());
> >> >> String s2=String.valueOf(Math.random());
> >> >> ps.setInt(1, i);
> >> >> ps.setString(2, s1);
> >> >> ps.setString(3, s2);
> >> >> ps.execute();
> >> >> }
> >> >> conn.prepareStatement("set streaming off").execute();
> >> >> long end=System.currentTimeMillis();
> >> >> System.out.println(end-start);
> >> >> }
> >> >>
> >> >> private static void overwriteData() throws SQLException{
> >> >>
> >> >> long start=System.currentTimeMillis();
> >> >> conn.prepareStatement("SET STREAMING ON
> >> ALLOW_OVERWRITE
> >> >> ON").execute();
> >> >>
> >> >> String sql="insert INTO  city1(id,name,name1)
> >> >> VALUES(?,?,?)";
> >> >> PreparedStatement ps=conn.prepareStatement(sql);
> >> >> for(int i=0;i<160;i++){
> >> >> String s1="test";
> >> >> String s2="test";
> >> >> ps.setInt(1, i);
> >> >> ps.setString(2, s1);
> >> >> ps.se

Search on a composite key

[ihorps]

hi all

Could somebody advise me how to query properly from Ignite cache based on
composite key condition?

Let's say I have a key class:

public class Key {
 private int countryId;
 private Date dateKey;
...
}

and a Value class:

public class Value {
 private int value1;
 private boolean value2;
...
}

so I do something like:

Key key = new Key(...);
Value value = new Value(...);
igniteCache.put(key, value);
...

And at the and I'd like to get all values now from this cache where
"dateKey" filed of all keys is under some conditions (for instance "dateKey"
= "2018-12-31")?

Thank you in advance!

Best regards,
Ihor P.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Creating Dataset classNotFound exception

[Mikhail]

Hi Mahesh,

The defined anonymous class( IgniteBiFunction) will be executed on the
server side, so it should be deployed there first, you can do this manually,
by extracting the class to distinct class, compile to jar and add to libs
folder on the server side.
Or you need to enable peer class loading:
https://apacheignite.readme.io/docs/zero-deployment

Thanks,
Mike.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: sql fields visibility without sql indexing

[Stanislav Lukyanov]

There are implicit indexes needed to make SQL work – one on primary key, one on 
affinity key.
They are also stored in index.bin, so it’s expected to see it growing.

Stan

From: Yuriy
Sent: 18 января 2019 г. 13:37
To: user@ignite.apache.org
Subject: sql fields visibility without sql indexing

Hi.

I want to see sql fields without sql indexing.
I use @QuerySqlField() annotation and invoke setIndexedTypes cache
configuration method.

But I watching that index.bin file is growing up.

I dot not use sql index. I need to see sql fields only. 
Why this file is growing up?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache updates slow on Linux Vs Windows

[ihorps]

hi all

I don't have exact example but I remember that I was running once my
prototype ignite app on Windows (all other cases were running under Ubuntu)
and I recognized that it was "slightly" faster.
I did give too much attention to it by thinking that was just my personal
feel and I could be mistaken. But seems to be I'm not alone here...



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

sql fields visibility without sql indexing

[Yuriy]

Hi.

I want to see sql fields without sql indexing.
I use @QuerySqlField() annotation and invoke setIndexedTypes cache
configuration method.

But I watching that index.bin file is growing up.

I dot not use sql index. I need to see sql fields only. 
Why this file is growing up?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache updates slow on Linux Vs Windows

[Павлухин Иван]

I suppose that Windows is faster in particular case. Am I wrong?

пн, 14 янв. 2019 г. в 18:00, ilya.kasnacheev :
>
> Hello!
>
> Did you figure out anything? I went through your log but did not have any
> exact ideas. Is it possible that Windows node is slowed down by very active
> I/O?
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/



-- 
Best regards,
Ivan Pavlukhin

Re: Failed to wait for initial partition map exchange

[Justin Ji]

I also have this problem with ignite 2.6.0. 
Spend more than 350 seconds to restart a ignite node. 

Here is the system usage during partition map exchange: 

The CPU is at a low level and memory is enough. 

Here is the logs, we can find that applying WAL changes takes a long time,
about 375664ms. 

>>>__   
>>>   /  _/ ___/ |/ /  _/_  __/ __/ 
>>>  _/ // (7 7// /  / / / _/ 
>>> /___/\___/_/|_/___/ /_/ /___/ 
>>> 
>>> ver. 2.6.0#20180710-sha1:669feacc 
>>> 2018 Copyright(C) Apache Software Foundation 
>>> 
>>> Ignite documentation: http://ignite.apache.org

2019-01-18 09:17:27:979 [main] INFO  o.a.i.i.IgniteKernal%ignite-server:478
- Config URL: file:/opt/ignite/config/ignite-config-benchmark-cn.xml 
2019-01-18 09:17:27:996 [main] INFO  o.a.i.i.IgniteKernal%ignite-server:478
- IgniteConfiguration [igniteInstanceName=ignite-server, pubPoolSize=8,
svcPoolSize=8, callbackPoolSize=8, stripedPoolSize=8, sysPoolSize=16,
mgmtPoolSize=4, igfsPoolSize=8, dataStreamerPoolSize=8,
utilityCachePoolSize=8, utilityCacheKeepAliveTime=6, p2pPoolSize=2,
qryPoolSize=16, igniteHome=/opt/ignite/apache-ignite-fabric,
igniteWorkDir=/opt/ignite/apache-ignite-fabric/work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@6f94fa3e,
nodeId=67815159-8a6d-4c3a-b626-a82e5bea1a65,
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@72ade7e3,
marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
discoSpi=ZookeeperDiscoverySpi [zkRootPath=/ignite/discovery,
zkConnectionString=10.0.230.12:2181,10.0.223.106:2181,10.0.247.246:2181,
joinTimeout=1, sesTimeout=3, clientReconnectDisabled=false,
internalLsnr=null,
stats=org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryStatistics@560348e6],
segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true,
allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi
[connectGate=null, connPlc=null, enableForcibleNodeKill=false,
enableTroubleshootingLog=false,
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@1df8b5b8,
locAddr=null, locHost=null, locPort=47174, locPortRange=100, shmemPort=-1,
directBuf=true, directSndBuf=false, idleConnTimeout=60,
connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
sockRcvBuf=32768, msgQueueLimit=1024, slowClientQueueLimit=0, nioSrvr=null,
shmemSrv=null, usePairedConnections=false, connectionsPerNode=1,
tcpNoDelay=true, filterReachableAddresses=false, ackSndThreshold=32,
unackedMsgsBufSize=0, sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1,
boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0, addrRslvr=null,
ctxInitLatch=java.util.concurrent.CountDownLatch@23202fce[Count = 1],
stopping=false,
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@7b993c65],
evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@37911f88,
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@4ea5b703,
addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=4,
txCfg=org.apache.ignite.configuration.TransactionConfiguration@2a7ed1f,
cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED,
p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100,
timeSrvPortRange=100, failureDetectionTimeout=1,
clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null,
connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@3fa247d1,
odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration
[seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null,
grpName=null], classLdr=null, sslCtxFactory=null, platformCfg=null,
binaryCfg=null, memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration
[sysRegionInitSize=41943040, sysCacheMaxSize=104857600, pageSize=0,
concLvl=0, dfltDataRegConf=DataRegionConfiguration [name=default,
maxSize=3119855206, initSize=268435456, swapPath=null,
pageEvictionMode=DISABLED, evictionThreshold=0.9, emptyPagesPoolSize=100,
metricsEnabled=false, metricsSubIntervalCount=5,
metricsRateTimeInterval=6, persistenceEnabled=false,
checkpointPageBufSize=0], storagePath=/data/ignite/persistence,
checkpointFreq=36, lockWaitTime=1, checkpointThreads=4,
checkpointWriteOrder=SEQUENTIAL, walHistSize=10, walSegments=10,
walSegmentSize=67108864, walPath=/ignite-wal/ignite/wal,
walArchivePath=/ignite-wal/ignite/wal/archive, metricsEnabled=false,
walMode=BACKGROUND, walTlbSize=131072, walBuffSize=0, walFlushFreq=2000,
walFsyncDelay=1000, walRecordIterBuffSize=67108864,
alwaysWriteFullPages=false,
fileIOFactory=org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory@4f4c4b1a,
metricsSubIntervalCnt=5, metricsRateTimeInterval=6,
walAutoArchiveAfterInactivity=-1, writeThrottlingEnabled=true,
walCompactionEnabled=false], activeOnStart=true, autoActi

Re: Failed to wait for initial partition map exchange

[Justin Ji]

I also have this problem with ignite 2.6.0.
Spend more than 350 seconds to restart a ignite node.

Here is the system usage during partition map exchange:
 
The CPU is at a low level and memory is enough.

Here is the logs, we can find that applying WAL changes takes a long time,
about 375664ms.

>>>__  
>>>   /  _/ ___/ |/ /  _/_  __/ __/
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 2.6.0#20180710-sha1:669feacc
>>> 2018 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org

2019-01-18 09:17:27:979 [main] INFO  o.a.i.i.IgniteKernal%ignite-server:478
- Config URL: file:/opt/ignite/config/ignite-config-benchmark-cn.xml
2019-01-18 09:17:27:996 [main] INFO  o.a.i.i.IgniteKernal%ignite-server:478
- IgniteConfiguration [igniteInstanceName=ignite-server, pubPoolSize=8,
svcPoolSize=8, callbackPoolSize=8, stripedPoolSize=8, sysPoolSize=16,
mgmtPoolSize=4, igfsPoolSize=8, dataStreamerPoolSize=8,
utilityCachePoolSize=8, utilityCacheKeepAliveTime=6, p2pPoolSize=2,
qryPoolSize=16, igniteHome=/opt/ignite/apache-ignite-fabric,
igniteWorkDir=/opt/ignite/apache-ignite-fabric/work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@6f94fa3e,
nodeId=67815159-8a6d-4c3a-b626-a82e5bea1a65,
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@72ade7e3,
marshLocJobs=false, daemon=false, p2pEnabled=false, netTimeout=5000,
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=1,
metricsUpdateFreq=2000, metricsExpTime=9223372036854775807,
discoSpi=ZookeeperDiscoverySpi [zkRootPath=/ignite/discovery,
zkConnectionString=10.0.230.12:2181,10.0.223.106:2181,10.0.247.246:2181,
joinTimeout=1, sesTimeout=3, clientReconnectDisabled=false,
internalLsnr=null,
stats=org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryStatistics@560348e6],
segPlc=STOP, segResolveAttempts=2, waitForSegOnStart=true,
allResolversPassReq=true, segChkFreq=1, commSpi=TcpCommunicationSpi
[connectGate=null, connPlc=null, enableForcibleNodeKill=false,
enableTroubleshootingLog=false,
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@1df8b5b8,
locAddr=null, locHost=null, locPort=47174, locPortRange=100, shmemPort=-1,
directBuf=true, directSndBuf=false, idleConnTimeout=60,
connTimeout=5000, maxConnTimeout=60, reconCnt=10, sockSndBuf=32768,
sockRcvBuf=32768, msgQueueLimit=1024, slowClientQueueLimit=0, nioSrvr=null,
shmemSrv=null, usePairedConnections=false, connectionsPerNode=1,
tcpNoDelay=true, filterReachableAddresses=false, ackSndThreshold=32,
unackedMsgsBufSize=0, sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1,
boundTcpShmemPort=-1, selectorsCnt=4, selectorSpins=0, addrRslvr=null,
ctxInitLatch=java.util.concurrent.CountDownLatch@23202fce[Count = 1],
stopping=false,
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationMetricsListener@7b993c65],
evtSpi=org.apache.ignite.spi.eventstorage.NoopEventStorageSpi@37911f88,
colSpi=NoopCollisionSpi [], deploySpi=LocalDeploymentSpi [lsnr=null],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@4ea5b703,
addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=4,
txCfg=org.apache.ignite.configuration.TransactionConfiguration@2a7ed1f,
cacheSanityCheckEnabled=true, discoStartupDelay=6, deployMode=SHARED,
p2pMissedCacheSize=100, locHost=null, timeSrvPortBase=31100,
timeSrvPortRange=100, failureDetectionTimeout=1,
clientFailureDetectionTimeout=3, metricsLogFreq=6, hadoopCfg=null,
connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@3fa247d1,
odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration
[seqReserveSize=1000, cacheMode=PARTITIONED, backups=1, aff=null,
grpName=null], classLdr=null, sslCtxFactory=null, platformCfg=null,
binaryCfg=null, memCfg=null, pstCfg=null, dsCfg=DataStorageConfiguration
[sysRegionInitSize=41943040, sysCacheMaxSize=104857600, pageSize=0,
concLvl=0, dfltDataRegConf=DataRegionConfiguration [name=default,
maxSize=3119855206, initSize=268435456, swapPath=null,
pageEvictionMode=DISABLED, evictionThreshold=0.9, emptyPagesPoolSize=100,
metricsEnabled=false, metricsSubIntervalCount=5,
metricsRateTimeInterval=6, persistenceEnabled=false,
checkpointPageBufSize=0], storagePath=/data/ignite/persistence,
checkpointFreq=36, lockWaitTime=1, checkpointThreads=4,
checkpointWriteOrder=SEQUENTIAL, walHistSize=10, walSegments=10,
walSegmentSize=67108864, walPath=/ignite-wal/ignite/wal,
walArchivePath=/ignite-wal/ignite/wal/archive, metricsEnabled=false,
walMode=BACKGROUND, walTlbSize=131072, walBuffSize=0, walFlushFreq=2000,
walFsyncDelay=1000, walRecordIterBuffSize=67108864,
alwaysWriteFullPages=false,
fileIOFactory=org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory@4f4c4b1a,
metricsSubIntervalCnt=5, metricsRateTimeInterval=6,
walAutoArchiveAfterInactivity=-1, writeThrottlingEnabled=true,
walCo

Re: server ignite.sh always shutdown

[Ilya Kasnacheev]

Hello!

Can you provide logs?

Regards,
-- 
Ilya Kasnacheev


чт, 17 янв. 2019 г. в 08:41, hulitao198758 :

> Ignite. Sh start multi-node server side is very unstable, often appear
> process termination situation, I now is running on a server three cluster
> nodes, three servers make up three cluster environment, often a server node
> will hang, I do not know what situation
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Consistency

[Ilya Kasnacheev]

Hello!

By default, cache operations will only read data from primary node (unless
readFromBackup is set to true).

This means that cache is consistent even with PRIMARY_SYNC.

Regards,
-- 
Ilya Kasnacheev


пт, 18 янв. 2019 г. в 03:39, Cindy Xing :

> In the ignite doc (
> https://apacheignite.readme.io/docs/primary-and-backup-copies), it
> mentioned that the cache will be immediate consistent independent of the
> sync mode chosen. Can someone help explain how? *Cache Data Consistency
> Note that regardless of write synchronization mode, cache data will always
> remain fully consistent across all participating nodes when using
> transactions. * Thanks Cindy
> --
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>