Re: [Meetup] Apache Spark and Ignite for IoT scenarious

[ANJANEYA PRASAD NIDUBROLU]

Hi Denis,

Many thanks for sharing the meetup link. But will this be broadcasted on
youtube or will you share video recordings after meetup is over?
I will not be able attend the session physically but can do virtually.

Thanks,
Anjaneya.
On 7 Sep 2017 04:45, "Denis Magda"  wrote:

> Folks,
>
> Those who are craving for mind food this weekend come over the meetup  -
> Santa Clara, Sept 9, 9.30 AM:
> https://www.meetup.com/datariders/events/242523245/?a=socialmedia
>
> —
> Denis
>

Re: Web Agent 2.1.3 giving message "You are using an older version of the agent."

[Andrey Novikov]

Hello Kenan Dalley,

Compatibility between different versions of web-agent is not supported. 
Please download web-agent that is available to download in an your run
docker image.



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

Re: Ignite is failing while starting Web Application

[manipvl]

Hi,

All the 3 web application connect to the same server. The Discovery port #:
47500 and system communication port #:47100



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

RE: Oddity running multiple server nodes locally

[Raymond Wilson]

And with some help from Google I found JStack. :)

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 1:25 PM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Correction to the information below.

The activator app does not stall on starting a local Ignite instance, it
stalls when calling Ignite.Start()

Apologies for the confusion, not sure how that happened!

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 11:47 AM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Ah - I think I see a gap in the logging configuration, and need to add the
following to the Ignite config:

Given:

private static readonly ILog Log =
LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

then:
  Logger = new IgniteLog4NetLogger(Log)

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 11:29 AM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Hi Val,

I'm not getting any obvious logging. I'm using Log4Net to configure
logging, and I am getting Ignite logging during some operations, but
perhaps I need to modify the logging configuration to pick up additional
information. I have both the Log4Net and Apache.Ignite.Log4Net nugget
packages installed.

Logging is configured like this:


  
  
  
  
  
  
  

  


And in the program code itself logging is initialized lie this:

string logFileName =
System.Diagnostics.Process.GetCurrentProcess().ProcessName + ".log";
log4net.GlobalContext.Properties["LogName"] = logFileName;
log4net.Config.XmlConfigurator.Configure();

I haven't done a (Java?) thread dump before, please let me know how I
should do this to get the information you need.

I do activation like this (a little simplified):

NodeID = Guid.NewGuid().ToString();

Log.InfoFormat("Creating new Ignite node with Role =
{0} & NodeID = {1}", role, NodeID);

IgniteConfiguration cfg = new IgniteConfiguration()
{
GridName = 'Grid',
IgniteInstanceName = 'Grid'
ClientMode = true,

JvmInitialMemoryMb = 512, // Set to minimum
advised memory for Ignite grid JVM of 512Mb
JvmMaxMemoryMb = 4 * 1024, // Set max to 4Gb

UserAttributes = new Dictionary()
{
{ "Role", role },
{ "NodeID", NodeID }
},

DiscoverySpi = new TcpDiscoverySpi()
{
LocalAddress = "127.0.0.1",
LocalPort = 47500
}
};

try
{
IIgnite Grid = Ignition.Start(cfg);<--
Activator hangs here
}
catch (Exception e)
{
Log.InfoFormat("Creation of new Ignite node with
Role = {0} & NodeID = {1} failed with exception {2}", role, NodeID, e);
}
finally
{
Log.InfoFormat("Completed creation of new Ignite
node with Role = {0} & NodeID = {1}", role, NodeID);
}

All the server nodes are created using the same grid name and instance
name.

Thanks,
Raymond.

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: Thursday, September 7, 2017 11:15 AM
To: user@ignite.apache.org
Subject: Re: Oddity running multiple server nodes locally

Raymond,

Can you attach logs and thread dumps? Also can you show how you do the
activation?

-Val



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

RE: Oddity running multiple server nodes locally

[Raymond Wilson]

Correction to the information below.

The activator app does not stall on starting a local Ignite instance, it
stalls when calling Ignite.Start()

Apologies for the confusion, not sure how that happened!

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 11:47 AM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Ah - I think I see a gap in the logging configuration, and need to add the
following to the Ignite config:

Given:

private static readonly ILog Log =
LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

then:
  Logger = new IgniteLog4NetLogger(Log)

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 11:29 AM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Hi Val,

I'm not getting any obvious logging. I'm using Log4Net to configure
logging, and I am getting Ignite logging during some operations, but
perhaps I need to modify the logging configuration to pick up additional
information. I have both the Log4Net and Apache.Ignite.Log4Net nugget
packages installed.

Logging is configured like this:


  
  
  
  
  
  
  

  


And in the program code itself logging is initialized lie this:

string logFileName =
System.Diagnostics.Process.GetCurrentProcess().ProcessName + ".log";
log4net.GlobalContext.Properties["LogName"] = logFileName;
log4net.Config.XmlConfigurator.Configure();

I haven't done a (Java?) thread dump before, please let me know how I
should do this to get the information you need.

I do activation like this (a little simplified):

NodeID = Guid.NewGuid().ToString();

Log.InfoFormat("Creating new Ignite node with Role =
{0} & NodeID = {1}", role, NodeID);

IgniteConfiguration cfg = new IgniteConfiguration()
{
GridName = 'Grid',
IgniteInstanceName = 'Grid'
ClientMode = true,

JvmInitialMemoryMb = 512, // Set to minimum
advised memory for Ignite grid JVM of 512Mb
JvmMaxMemoryMb = 4 * 1024, // Set max to 4Gb

UserAttributes = new Dictionary()
{
{ "Role", role },
{ "NodeID", NodeID }
},

DiscoverySpi = new TcpDiscoverySpi()
{
LocalAddress = "127.0.0.1",
LocalPort = 47500
}
};

try
{
IIgnite Grid = Ignition.Start(cfg);<--
Activator hangs here
}
catch (Exception e)
{
Log.InfoFormat("Creation of new Ignite node with
Role = {0} & NodeID = {1} failed with exception {2}", role, NodeID, e);
}
finally
{
Log.InfoFormat("Completed creation of new Ignite
node with Role = {0} & NodeID = {1}", role, NodeID);
}

All the server nodes are created using the same grid name and instance
name.

Thanks,
Raymond.

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: Thursday, September 7, 2017 11:15 AM
To: user@ignite.apache.org
Subject: Re: Oddity running multiple server nodes locally

Raymond,

Can you attach logs and thread dumps? Also can you show how you do the
activation?

-Val



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

RE: Oddity running multiple server nodes locally

[Raymond Wilson]

Ah - I think I see a gap in the logging configuration, and need to add the
following to the Ignite config:

Given:

private static readonly ILog Log =
LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

then:
  Logger = new IgniteLog4NetLogger(Log)

-Original Message-
From: Raymond Wilson [mailto:raymond_wil...@trimble.com]
Sent: Thursday, September 7, 2017 11:29 AM
To: 'user@ignite.apache.org' 
Subject: RE: Oddity running multiple server nodes locally

Hi Val,

I'm not getting any obvious logging. I'm using Log4Net to configure
logging, and I am getting Ignite logging during some operations, but
perhaps I need to modify the logging configuration to pick up additional
information. I have both the Log4Net and Apache.Ignite.Log4Net nugget
packages installed.

Logging is configured like this:


  
  
  
  
  
  
  

  


And in the program code itself logging is initialized lie this:

string logFileName =
System.Diagnostics.Process.GetCurrentProcess().ProcessName + ".log";
log4net.GlobalContext.Properties["LogName"] = logFileName;
log4net.Config.XmlConfigurator.Configure();

I haven't done a (Java?) thread dump before, please let me know how I
should do this to get the information you need.

I do activation like this (a little simplified):

NodeID = Guid.NewGuid().ToString();

Log.InfoFormat("Creating new Ignite node with Role =
{0} & NodeID = {1}", role, NodeID);

IgniteConfiguration cfg = new IgniteConfiguration()
{
GridName = 'Grid',
IgniteInstanceName = 'Grid'
ClientMode = true,

JvmInitialMemoryMb = 512, // Set to minimum
advised memory for Ignite grid JVM of 512Mb
JvmMaxMemoryMb = 4 * 1024, // Set max to 4Gb

UserAttributes = new Dictionary()
{
{ "Role", role },
{ "NodeID", NodeID }
},

DiscoverySpi = new TcpDiscoverySpi()
{
LocalAddress = "127.0.0.1",
LocalPort = 47500
}
};

try
{
IIgnite Grid = Ignition.Start(cfg);<--
Activator hangs here
}
catch (Exception e)
{
Log.InfoFormat("Creation of new Ignite node with
Role = {0} & NodeID = {1} failed with exception {2}", role, NodeID, e);
}
finally
{
Log.InfoFormat("Completed creation of new Ignite
node with Role = {0} & NodeID = {1}", role, NodeID);
}

All the server nodes are created using the same grid name and instance
name.

Thanks,
Raymond.

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: Thursday, September 7, 2017 11:15 AM
To: user@ignite.apache.org
Subject: Re: Oddity running multiple server nodes locally

Raymond,

Can you attach logs and thread dumps? Also can you show how you do the
activation?

-Val



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

RE: Oddity running multiple server nodes locally

[Raymond Wilson]

Hi Val,

I'm not getting any obvious logging. I'm using Log4Net to configure
logging, and I am getting Ignite logging during some operations, but
perhaps I need to modify the logging configuration to pick up additional
information. I have both the Log4Net and Apache.Ignite.Log4Net nugget
packages installed.

Logging is configured like this:


  
  
  
  
  
  
  

  


And in the program code itself logging is initialized lie this:

string logFileName =
System.Diagnostics.Process.GetCurrentProcess().ProcessName + ".log";
log4net.GlobalContext.Properties["LogName"] = logFileName;
log4net.Config.XmlConfigurator.Configure();

I haven't done a (Java?) thread dump before, please let me know how I
should do this to get the information you need.

I do activation like this (a little simplified):

NodeID = Guid.NewGuid().ToString();

Log.InfoFormat("Creating new Ignite node with Role =
{0} & NodeID = {1}", role, NodeID);

IgniteConfiguration cfg = new IgniteConfiguration()
{
GridName = 'Grid',
IgniteInstanceName = 'Grid'
ClientMode = true,

JvmInitialMemoryMb = 512, // Set to minimum
advised memory for Ignite grid JVM of 512Mb
JvmMaxMemoryMb = 4 * 1024, // Set max to 4Gb

UserAttributes = new Dictionary()
{
{ "Role", role },
{ "NodeID", NodeID }
},

DiscoverySpi = new TcpDiscoverySpi()
{
LocalAddress = "127.0.0.1",
LocalPort = 47500
}
};

try
{
IIgnite Grid = Ignition.Start(cfg);<--
Activator hangs here
}
catch (Exception e)
{
Log.InfoFormat("Creation of new Ignite node with
Role = {0} & NodeID = {1} failed with exception {2}", role, NodeID, e);
}
finally
{
Log.InfoFormat("Completed creation of new Ignite
node with Role = {0} & NodeID = {1}", role, NodeID);
}

All the server nodes are created using the same grid name and instance
name.

Thanks,
Raymond.

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: Thursday, September 7, 2017 11:15 AM
To: user@ignite.apache.org
Subject: Re: Oddity running multiple server nodes locally

Raymond,

Can you attach logs and thread dumps? Also can you show how you do the
activation?

-Val



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

Re: create two client instance in one JVM to connect two ignite cluster

[vkulichenko]

Shawn,

Can you please provide more detail on what you're trying to achieve and what
you tried for that? What exactly is not working?

-Val



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

Re: Cache classes deployment

[vkulichenko]

Hi Egor,

Peer class loading is not working for data model classes. You should either
deploy classes explicitly on all nodes, or use BinaryObject API:
https://apacheignite.readme.io/docs/binary-marshaller#binaryobject-cache-api

-Val



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

[Meetup] Apache Spark and Ignite for IoT scenarious

[Denis Magda]

Folks, 

Those who are craving for mind food this weekend come over the meetup  - Santa 
Clara, Sept 9, 9.30 AM:
https://www.meetup.com/datariders/events/242523245/?a=socialmedia 


—
Denis

Re: Oddity running multiple server nodes locally

[vkulichenko]

Raymond,

Can you attach logs and thread dumps? Also can you show how you do the
activation?

-Val



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

Re: Write-Behind Cache configuration and custom cache store

[vkulichenko]

Rick,

writeThrough property enables cache store integration overall, while
writeBehindEnabled property controls whether store updates are async or not.
So this is correct behavior.

As for transactions, write-behind store updates are always non
transactional. I.e. you will have a transaction in cache, but updates in
this transaction will be written into store independently. Therefore you
don't observe database transaction commit in this scenario. If you need
strong consistency between cache and DB, use sync write-through.

-Val



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

Oddity running multiple server nodes locally

[Raymond Wilson]

I’m using Ignite 2.1 with persistence and have a POC running successfully
using a single  server node.



I now want to simulate running a cluster of server nodes locally. To do
this I’m running multiple (4) instances of my server node via a batch file
in a command shell. I can see from the naming of the persistence folders
that each instance is correctly choosing a different port (and same IP –
LocalHost).



The four nodes do run up and successfully create their local Ignite
instances, all with the same name (GridName and IgniteInstance name are set
to the same value in IgniteConfiguration, in each server node).



I have a separate tool that I use to activate the cluster once it is
running. This works well when I have a single server node running locally,
but when I am running multiple nodes the activation call never returns, and
none of the server nodes ever goes to an active state. The activator
attempts to obtain an Ignite reference using the same name assigned to the
igniter grid and instance names, but this call never returns, where it does
return if there is a single server node running.



I’m assuming there is something simple I’m not doing, though it all seems
like it should work.



Thanks,

Raymond.

Cache classes deployment

[ekomarov]

Hello,

I have an ignite cache with custom classes in keys and values, like
IgniteCache only on one ignite node. I want to read and
write data for this cache on all ignite nodes. I tried to use peer class
loading, but got a ClassNotFoundException on remote ignite nodes. Is it
possible to read and write data from cache without deploying my classes to
all nodes?

Thanks,
Egor.




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

create two client instance in one JVM to connect two ignite cluster

[shawn.du]

Hi,It seems that ignite can't do as the topic describe. I want to do data synchronization manually between two cluster, any suggest?






ThanksShawn

Re: Ignite is failing while starting Web Application

[Mikhail]

Hi,

So all 3 applications start ignite in client mode and connect to the same
ignite server, do them?

Is it correct that ignite server address is 10.17.32.45/10.17.32.45:47100 ?

Could you please run all client and server nodes with -DIGNITE_QUIET=false
flag and provide full logs from all those nodes?

Thanks,
Mikhail.




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

Re: Access Ignite Data

[Mikhail]

Hi Mimmo,

So I think the fastest way is to send compute jobs to all nodes which store
data and in those compute
jobs run scan queries for local partitions and save files to local file.
Also you can scan different partition in parallel to utilize all available
CPUs.
In this case you won't have any contention for data access and utilize all
CPUs in the grid.

if you need to  gather data on one particular node, you can do the same but
without compute job. Just run scan queries for by partitions in parallel to
utilize all CPUs.

Thanks,
Mikhail.



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

Re: integration of Apache ISIS and Ignite

[Mikhail]

Hi, 

Looks like it's known issue, please try the solution from this thread:

http://apache-ignite-users.70518.x6.nabble.com/Can-t-load-log-handler-quot-org-apache-ignite-logger-java-JavaLoggerFileHandler-quot-td4490.html

Thanks,
Mikhail.



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

Re: many users used a temptable

[Mikhail]

Hi Lucky,

Ignite supports DDL:

https://apacheignite.readme.io/docs/distributed-ddl

you can create and drop tables as much as you want.

Thanks,
Mikhail.



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

Access Ignite Data

[mimmo_c]

Hi,

What is the fastest way to fetch all cache data in Ignite 2.0 ?

Thanks,
Mimmo



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

Re: Task management - MapReduce & ForkJoin performance penalty

[Yakov Zhdanov]

Try attaching @ComputeTaskNoResultCache to your task.

Also filed a ticket - https://issues.apache.org/jira/browse/IGNITE-6284

As far as 2 - I meant empty runnables submitted to an JDK thread pool
executor - submission will require to acquire a lock and notify pool
thread. So overhead is very significant compared to an execution of a no-op
runnable. Ignite processes job execution requests coming from remote node
in public pool
(org.apache.ignite.configuration.IgniteConfiguration#getPublicThreadPoolSize)
and submits jobs to this pool mapped from local node.

--Yakov

Web Agent 2.1.3 giving message "You are using an older version of the agent."

[Kenan Dalley]

I've pulled the latest docker image and web-agent (2.1.3) and am running
against 2.1-bin code, but whenever I try to connect, all I get is the
following:

[2017-09-06 07:49:30,891][INFO ][main][AgentLauncher] Starting Apache Ignite
Web Console Agent...

Agent configuration:
User's security tokens: qzLp
URI to Ignite node REST server: http://localhost:8080
URI to Ignite Console server  : http://192.168.99.100:3001
Path to agent property file   : default.properties
Path to JDBC drivers folder   : D:\Documents\Development\Apache
Ignite\ignite-web-agent\ignite-web-agent-2.1.3\jdbc-drivers
Demo mode : enabled

[2017-09-06 07:49:31,494][INFO ][main][AgentLauncher] Connecting to:
http://192.168.99.100:3001
[2017-09-06 07:49:31,562][INFO ][EventThread][AgentLauncher] Connection
established.
[2017-09-06 07:49:31,595][ERROR][EventThread][AgentLauncher] You are using
an older version of the agent. Please reload agent
Press any key to continue . . .



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

Re: ignite compute job continuation documentation

[Evgeniy Ignatiev]

May be a couple of lines can be added to official documentation so the 
users can actually know about the existence of this feature without 
going through examples? Also it is currently unclear for me looking on 
the ComputeFibonacciContinuationExample why holdcc is called before the 
listener is attached to the futures.


Best Regards,

Evgeniy.


On 05.09.2017 21:58, mcherkasov wrote:

Hi Anton,

We have only docs that you mentioned.

Do you have questions about continuation jobs?

Thanks,
Mikhail.



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

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

[Kenan Dalley]

I made that change and the result was the same, so it looks like it's not
creating a new cache with the getOrCreateCache() method.



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

Re: New API docs look for Ignite.NET

[Pavel Tupitsyn]

Looks like everyone is ok with this. I'm going to merge these changes to
master.

Doxygen-related stuff remains there for now just in case, we have a
separate ticket to remove it:
https://issues.apache.org/jira/browse/IGNITE-6267

On Wed, Sep 6, 2017 at 11:16 AM, Vladimir Ozerov 
wrote:

> Looks good to me. Clean layout, fast build - do we need anything else?
>
> On Tue, Sep 5, 2017 at 12:06 PM, Oleg Ostanin 
> wrote:
>
> > Great news, thanks a lot!
> >
> > On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn 
> > wrote:
> >
> >> DocFX takes around 30 seconds on my machine.
> >>
> >> > if you already tried that
> >> Yes, everything is done on my side, see JIRA ticket [4] and preview [5]
> >> above.
> >>
> >> On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov 
> >> wrote:
> >>
> >> > Pavel, thanks!
> >> > It is the great news!
> >> > Looks like DocFX will save 30-40 min.
> >> >
> >> > 2017-09-05 11:16 GMT+03:00 Pavel Tupitsyn :
> >> >
> >> > > Igniters and users,
> >> > >
> >> > > Historically we've been using Doxygen [1] to generate .NET API
> >> > > documentation [2].
> >> > >
> >> > > Recently it became very slow on our code base (more than 30 minutes
> to
> >> > > generate), and I could not find any solution or tweak to fix that.
> >> Other
> >> > > issues include outdated looks and limited customization
> possibilities.
> >> > >
> >> > > I propose to replace it with DocFX [3] [4]:
> >> > > - Popular .NET Foundation project
> >> > > - Good looks and usability out of the box
> >> > > - Easy to set up
> >> > >
> >> > > Our docs will look like this: [5]
> >> > > Let me know if you have any objections or suggestions.
> >> > >
> >> > > Pavel
> >> > >
> >> > >
> >> > > [1] http://www.stack.nl/~dimitri/doxygen/
> >> > > [2] https://ignite.apache.org/releases/latest/dotnetdoc/index.html
> >> > > [3] https://dotnet.github.io/docfx/
> >> > > [4] https://issues.apache.org/jira/browse/IGNITE-6253
> >> > > [5] https://ptupitsyn.github.io/docfx-test/api/index.html
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Ilya Suntsov
> >> >
> >>
> >
> >
>

Re: Authentication

[franck102]

Hi all,

I am reviving this thread because as far as I can tell the initial question
was not answered, and I am hitting the same problem:
"* when a node starts up it needs to fetch the local password and store it
in it's own configuration "

... and I can't figure out how to do that?? The only place where the TCP SPI
reads credentials from when creating its join request is from the
org.apache.ignite.security.cred, which as mentioned cannot be set because
the key name is reserved??

Franck



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

integration of Apache ISIS and Ignite

[Nikhil Dhamapurkar]

Hi ,

I am trying to integrate  apache Ignite as the L2 Cache for apache ISIS. I have 
added Apache ignite JDBC connection to the persistor.properties in isis.

When I am trying to compile my web app I am getting ignite logger exception 
listed in stack trace [1]

I can see earlier mailing list archive saying this is a known issue where java 
logger is getting called and has asked user to  add ignite-log4j, even if I 
have added this in the class path I am still getting the error.

The connection from apache ISIS is failing to ignite which I am able to 
connection from SQL client, since the logger is not working I believe I can be 
missing important information and need to fix it before I can proceed with 
resolving connection Issue from ISIS to ignite (default cache)

Regards
Nikhil


[1]
5:53:35,153  [PersistenceSessionFactory main   INFO ]  did *not* find 
config properties to use JNDI datasource; will use JDBC
Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"
java.lang.ClassNotFoundException: 
org.apache.ignite.logger.java.JavaLoggerFileHandler
java.lang.ClassNotFoundException: 
org.apache.ignite.logger.java.JavaLoggerFileHandler
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.util.logging.LogManager$5.run(LogManager.java:965)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.loadLoggerHandlers(LogManager.java:958)
at 
java.util.logging.LogManager.initializeGlobalHandlers(LogManager.java:1578)
at java.util.logging.LogManager.access$1500(LogManager.java:145)
at 
java.util.logging.LogManager$RootLogger.accessCheckedHandlers(LogManager.java:1667)
at java.util.logging.Logger.getHandlers(Logger.java:1777)
at 
org.apache.ignite.logger.java.JavaLogger.findHandler(JavaLogger.java:399)
at 
org.apache.ignite.logger.java.JavaLogger.configure(JavaLogger.java:229)
at org.apache.ignite.logger.java.JavaLogger.(JavaLogger.java:170)
at org.apache.ignite.logger.java.JavaLogger.(JavaLogger.java:126)
at 
org.apache.ignite.IgniteJdbcDriver.(IgniteJdbcDriver.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)

Write-Behind Cache configuration and custom cache store

[rick_tem]

Hi,

I am using Ignite 2.0.0 with a cache configurations shown below.  First, I
noticed that writeAll() or any write() was not called on my cache store when
writeBehindEnabled=true but writeThrough=false.  Seems like if
writeBehindEnabled set to true, it should override writeThrough, but anyway,
I got around that.  With my writeBehind cache now calling writeAll() in my
cache store I noticed sessionEnd() is not called even when my cache is
TRANSACTIONAL.  Does this mean I have to call commit() on the connection at
the end of writeAll()?  How would I then differentiate a call to writeAll()
from putAll()?  It seems like sessionEnd() should be called when a flush
occurs if I am specifying a TRANSACTIONAL cache.  Is this a bug?  I am not
explicitly using transactions (i.e. try (Transaction tx =
transactions.txStart()) )...When I just use write through caching,
sessionEnd() is called without an explicit transaction and as well behaves
in a JTA environment.

Thanks for any clarification.

Best,
Rick













 



















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

Re: Custom SecurityCredentialsProvider and SecurityCredentials

[franck102]

What is even more confusing is that SecurityCredentialsProvider is in fact
only used in GridClient and GridTcpRouter configurations. If I understans
correctly GridClient is in turn only used by the cmd line client, and by the
deprecated legacy jdbc connection.

So, what is the proper strategy for supplying custom credentials or better a
custom credential provider for a client node?
The only way I see is to get locNode.attributes to contain a
org.apache.ignite.security.cred  key however that can't even be set from
user attributes in the configuration...

Franck



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

Re: Task management - MapReduce & ForkJoin performance penalty

[ihorps]

hi @yakov

Thank you for your feedback.

1. yes, warming up a jvm - this is what I missed at the begging (no doubts
here at all). I can confirm that it gets better in average after few dozens
of run.
2. did you mean than IgniteRunnable/IgniteCallable here (efficiency for
no-op task/job)? I'd like to use Map Reduce framework (especially when
IGNITE-5037 is implemented) such as it gives me almost out-of-the-box a
feature of Task management in terms of collocation execution, failover,
distribution. If I would go with IgniteRunnable/IgniteCallable I'd have to
take over our proprietary code, which we implemented in hazelcast and this
is what I want to avoid.
3. Can confirm that is runs ~ 1sec. faster after JVM is warmed up (4000
jobs, 1 task and to local nodes).

For now I'm satisfied with the "first-try-touch" experience. Looking forward
for IGNITE-5037.

The next topic is to compare memory consumption, such I wrote in previous
comments, running 4000 no-op jobs with help of Map Reduce API I could follow
that at least 2Gb additional memory was used for such run. Still have to
investigate why and how it works in more details.

Thanks!  



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

Re: ignite.active(true) blocking forever

[Yakov Zhdanov]

Then you may have a data loss?

--Yakov

2017-09-06 12:51 GMT+03:00 Вячеслав Коптилин :

> Hi Yakov,
>
> At first sight, it seems that we can use the same approach for this issue,
> but in this particular case, I think, the best way to handle
> OutOfMemoryError is to shutdown the node that could not be activated.
>
> Best regards,
> Slava.
>
> 2017-09-06 11:26 GMT+03:00 Yakov Zhdanov :
>
>> Slava, this looks like the issue with start cache operation throwing
>> exception on some nodes and cache start rollback. I remember you
>> implemented that fix. Can we apply the same machinery to rollback the
>> activation with proper exception?
>>
>> --Yakov
>>
>
>

Re: ignite.active(true) blocking forever

[Вячеслав Коптилин]

Hi Yakov,

At first sight, it seems that we can use the same approach for this issue,
but in this particular case, I think, the best way to handle
OutOfMemoryError is to shutdown the node that could not be activated.

Best regards,
Slava.

2017-09-06 11:26 GMT+03:00 Yakov Zhdanov :

> Slava, this looks like the issue with start cache operation throwing
> exception on some nodes and cache start rollback. I remember you
> implemented that fix. Can we apply the same machinery to rollback the
> activation with proper exception?
>
> --Yakov
>

many users used a temptable

[Lucky]

Hi
I encountered such a problem: 
I have been loaded with some cache data in ignite, and then creates a 
temporary table and write data, 
and associate query with these cached data, 
delete the temporary table after use; 
support such a scene in ignite? 
It is possible for multiple users to use this function at the same time.
Any suggestions?
Thanks .

Re:Re: ignit2.1 start h2 debug console error

[Lucky]

Thanks  a lot!

It's work!





At 2017-09-04 17:15:35, "ilya.kasnacheev"  wrote:
>Hello Lucky,
>
>It should be -DIGNITE_H2_DEBUG_CONSOLE=true
>
>note the "D" after dash, that means "define property"
>and the absense of whitespace before equals sign (and anywhere else) which
>will otherwise split your parameter into two.
>
>Hope it helps,
>Ilya.
>
>
>
>--
>Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Task management - MapReduce & ForkJoin performance penalty

[Yakov Zhdanov]

Guys,

I see the following issues with the benchmark:

1. There is only one iteration. I would put it in a loop and measure at
least hundred of iterations.
2. no-op jobs are not real world example at all =) job requests are
processed in thread pool executor which is not very much effective for such
usecase.
3. Job is an inner class inside NoOpTask. Evgeniy, can you please change it
to a static class and check if it helps here?
4. Also, multinode tests should be run on multiple machines (preferably, 1
node per host).

--Yakov

Re: GROUP_CONCAT function is unsupported

[mhetea]

Hello, 
I saw that the ticket was not fixed. 
Is there a workaround for this issue?
I wouldn't like to iterate over the results and then concatenate them
because the result list can be large. 
Thank you!



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

Re: How to control the quit of Ignite instance manually?

[Denis Mekhanikov]

As per documentation
,
you can implement a LifecycleBean and specify it in IgniteConfiguration.
You can process BEFORE_NODE_STOP or AFTER_NODE_STOP in this implementation.

- Denis

ср, 6 сент. 2017 г. в 10:26, aa...@tophold.com :

> hi All,
>
> We want to the control the quit of the Ignite instance,  so we can do some
> purger and housekeeping job before ignite shutdown.
>
> But seem Ignite add hook to the JVM runtime; so we can always  get
> BEFORE_NODE_STOP before our cleaning up job kick.
>
> Is there anyway we can control exactly time when ignite should quit?
>
> Thanks again for your time!
>
> Regards
> Aaron
> --
> aa...@tophold.com
>

Re: ignite.active(true) blocking forever

[Yakov Zhdanov]

Slava, this looks like the issue with start cache operation throwing
exception on some nodes and cache start rollback. I remember you
implemented that fix. Can we apply the same machinery to rollback the
activation with proper exception?

--Yakov

Re: New API docs look for Ignite.NET

[Vladimir Ozerov]

Looks good to me. Clean layout, fast build - do we need anything else?

On Tue, Sep 5, 2017 at 12:06 PM, Oleg Ostanin  wrote:

> Great news, thanks a lot!
>
> On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn 
> wrote:
>
>> DocFX takes around 30 seconds on my machine.
>>
>> > if you already tried that
>> Yes, everything is done on my side, see JIRA ticket [4] and preview [5]
>> above.
>>
>> On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov 
>> wrote:
>>
>> > Pavel, thanks!
>> > It is the great news!
>> > Looks like DocFX will save 30-40 min.
>> >
>> > 2017-09-05 11:16 GMT+03:00 Pavel Tupitsyn :
>> >
>> > > Igniters and users,
>> > >
>> > > Historically we've been using Doxygen [1] to generate .NET API
>> > > documentation [2].
>> > >
>> > > Recently it became very slow on our code base (more than 30 minutes to
>> > > generate), and I could not find any solution or tweak to fix that.
>> Other
>> > > issues include outdated looks and limited customization possibilities.
>> > >
>> > > I propose to replace it with DocFX [3] [4]:
>> > > - Popular .NET Foundation project
>> > > - Good looks and usability out of the box
>> > > - Easy to set up
>> > >
>> > > Our docs will look like this: [5]
>> > > Let me know if you have any objections or suggestions.
>> > >
>> > > Pavel
>> > >
>> > >
>> > > [1] http://www.stack.nl/~dimitri/doxygen/
>> > > [2] https://ignite.apache.org/releases/latest/dotnetdoc/index.html
>> > > [3] https://dotnet.github.io/docfx/
>> > > [4] https://issues.apache.org/jira/browse/IGNITE-6253
>> > > [5] https://ptupitsyn.github.io/docfx-test/api/index.html
>> > >
>> >
>> >
>> >
>> > --
>> > Ilya Suntsov
>> >
>>
>
>

Re: Message Queue Size

[dkarachentsev]

Hi Rishi,

Message queue limit was disabled in 1.9 release because in async mode it may
cause not obvious cluster stall, when OOMEs a quite rare issue. Currently
planned a new back-pressure mechanism [1], another possible issue with
PRIMARY_SYNC was already resolved [2]. 

Generally it's no need to tune this property, but you always may set it in
TcpCommunicationSpi.setMessageQueueLimit(int).

In Spring xml:









[1] https://issues.apache.org/jira/browse/IGNITE-5056
[2] https://issues.apache.org/jira/browse/IGNITE-2466

Thanks!
-Dmitry.



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

How to control the quit of Ignite instance manually?

[aa...@tophold.com]

hi All, 

We want to the control the quit of the Ignite instance,  so we can do some 
purger and housekeeping job before ignite shutdown. 

But seem Ignite add hook to the JVM runtime; so we can always  get 
BEFORE_NODE_STOP before our cleaning up job kick.

Is there anyway we can control exactly time when ignite should quit?

Thanks again for your time!

Regards
Aaron


aa...@tophold.com

Re: With onHeapCacheEnabled = false, BinaryOnHeapOutputStream is still used, why?

[dkarachentsev]

Hi John,

BinaryHeapOutputStream is the part of binary marshaller, and it's used for
object serialization only. Entry are stored in off-heap paged memory as
expected.

Thanks!
-Dmitry.



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

Re: copyOnRead to false

[steve.hostett...@gmail.com]

HI,I am using 1.9 and according to your explanation neither does it  make sense to me. Thanks anyway for explaining the precise semantics. I will try to change some parameters of the tests to see if I can come up with some meaningful explanation.Thanks againSteve Original Message Subject: Re: copyOnRead to falseFrom: Evgenii Zhuravlev To: user@ignite.apache.orgCC: Hi,I want to clarify about usage copyOnRead=False:As far as I know, It should help in 1.x releases, with the default configuration, when entries stored in onheap and in 2.x releases, with _onHeapCacheEnabled_=true(it's not default). I think we should mention this in the documentation.Also, it shouldn't affect behavior in 2.x without enabled on heap cache, so, It's not clear to me why you get performance degradation.Evgenii2017-09-05 10:36 GMT+03:00 steve.hostettler :Hello,

thanks for the answer. The benchmark is actually our application stressed
with several volumes. Some quite complex to describe. However, for these
benchmarks we are only using one node.

Basically we are loading a set of caches from the database, do a lot of
querying both ScanQuery (on BinaryObjects) and SQLQueries.

Most of what we are doing is read only with lot of computations (at least we
segregated the caches that are r/w)

Based on what you described, I should witness an performance improvment.



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