Re: distributed-ddl extended-parameters section showing 404 page not found

[dkarachentsev]

Hi,

Where did you find it? It might be a broken link.

Thanks!
-Dmitry



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

distributed-ddl extended-parameters section showing 404 page not found

[Huang Meilong]

hi,


do you know what are the extended parameters for distributed ddl, this page can 
not be found.


https://apacheignite-sql.readme.io/docs/distributed-ddl#section-extended-parameters


Thanks

Re: Thin client vs client node performance in Spark

[akurbanov]

Hi,

Spark integration was implemented before java thin client was released and
thick client performs better than thin one in general. Is your question
related to existence of benchmarks for thin vs thick clients in Spark
integration or just a comparison of these two options?

Thin clients' functionality is limited compared to thick client, also it
generally should be a bit slower as it is communicates not with whole
cluster, but only with a single node and is not partition-aware. This
introduces additional network costs which may affect performance compared to
thick client in the simplest and ideal conditions where network transfer is
a major part of workload.

However this performance decrease may be completely irrelevant depending on
use case and workload, so you should always measure peformance and do
benchmarks for a specific use case and make a decision which option suits
your needs more.



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

Re: SQl Fields Query Using Java date

[akurbanov]

Hi,

Do you have full stacktrace or a minimal reproducer of the issue? There
should be a reason that your object is not being correctly serialized, I've
just tried a simple example with java.util.Date and it works just fine, PFA
sample Java code snippet.


IgniteDateFieldExample.java

  



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

Re: Eviction Policy on Dirty data

[monstereo]

yes, using cachestore and write through

dkarachentsev wrote
> Hi,
> 
> Could you please explain how do you update database? Do you use CacheStore
> with writeThrough or manually save?
> 
> Anyway, you can update data with custom eviction policy:
> cache.withExpiryPolicy(policy) [1]
> 
> [1]
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#withExpiryPolicy-javax.cache.expiry.ExpiryPolicy-
> 
> Thanks!
> -Dmitry
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/





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

Re: No response from ignite job tracker

[engrdean]

Thanks Ilya.  The reason I used that address is because the value in the
example config provided with the ignite-hadoop package is:


mapreduce.jobtracker.address
localhost:11211


I tried changing it to just "local" which I know is the default, but I get
the following error:

2018-08-14 14:47:13,714 INFO  [main] mapreduce.Cluster
(Cluster.java:initialize(113)) - Failed to use
org.apache.ignite.hadoop.mapreduce.IgniteHadoopClientProtocolProvider due to
error:
java.io.IOException: Local execution mode is not supported, please point
mapreduce.jobtracker.address to real Ignite nodes.

I also tried changing it to just my server name with no port reference like:


mapreduce.jobtracker.address
myserver.com


and leaving it the value in the example ignite-hadoop configs:


mapreduce.jobtracker.address
localhost:11211


In both of those cases, it shows the url as N/A:

2018-08-14 15:09:24,285 INFO  [main] mapreduce.Job (Job.java:submit(1294)) -
The url to track the job: N/A

The description for mapreduce.jobtracker.address in the hadoop documentation
is:

"The host and port that the MapReduce job tracker runs at. If "local", then
jobs are run in-process as a single map and reduce task."

What port does ignite use for this if it isn't 11211?



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

Thin client vs client node performance in Spark

[eugene miretsky]

Hello,

What are the tradeoffs of using the thin client vs client node? Are there
any benchmarks?

The Spark client is using the latter (client node) - is that for
performance reasons or just legacy?

Cheers,
Eugene

Re: Node with BaselineTopology cannot join mixed clusterrunningincompatibility mode

[Stanislav Lukyanov]

FYI the issue https://issues.apache.org/jira/browse/IGNITE-8774 is now fixed,
the fix will be available in Ignite 2.7.



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

RE: Ignite client and server on yarn with cache read through

[Stanislav Lukyanov]

Seems to be answered in a nearby thread:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-yarn-cache-store-class-not-found-tt23016.html

Stan

From: debashissinha
Sent: 28 июля 2018 г. 13:01
To: user@ignite.apache.org
Subject: Ignite client and server on yarn with cache read through

Hi ,

I have a use case where by I have to deploy ignite as a yarn application and
access the same from a client .

The requirement is to implement cache read through based on hive database .  

I have implemented the cache read though and started ignite from client
mode. 

I have deployed  a downloaded yarn jar on yarn and on configured peer class
loading there.

On my client ignite application also peer class loading is also enabled. 
However whenever I am calling a cache.get on client node it is giving me a
class not found exception on the deployed server node on yarn. Here the
class in question is CacheStore class which is used for read through.
Based on my previous discussion in this forum I was advised that ignite will
not do any peer class loading for any cache configuration class or any
CacheStore class from client to server but it is mean for only domain
objects and that it has to be present in server node to do that.

I am trying to understand how should I enable this on the yarn jar that I am
deploying on yarn .

Firstly do I build a yarn jar and keep this cache store class in it . If
that is the case then how is this yarn jar built from scratch . I have read
the documentation it says how to deploy the yarn jar with cluster.properties
on yarn. But I was searching for a way to know how this yarn jar is built . 
I am also interested to know if this approach at all works . Whereby I built
a ignite yarn jar and keep my cachestore class in it and when i call form my
client application it should work .

The next approach i thought may be to create normal yarn jar using maven and
put the ignite yarn dependency though maven and build it on spring boot and
then deploy it .However in this approach I will not be able to specify
cluster info via cluster.properties and it will be a normal java spring boot
application running on yarn which starts the ignite. 

I  badly need a solution for this as we have to implement ignite on hive.
Your advice in this regard will be of great help to me .

Thanks in advance
Debashis Sinha




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

Re: values retrieved from the cache are wrapped with JdkDynamicAopProxy while using springboot and JCache

[ipavlukhin]

Hi daya,

Sorry for delay. I hope I will have a minute tomorrow to check this case.


On 13.08.2018 15:04, daya airody wrote:

HI Ivan,

I have uploaded a simple spring application reproducing the issue at below
link:

https://github.com/daya-airody/ignite-caching

When I use ConcurrentMapCache to cache results from spring JPA native query,
I am able to retrieve it correctly. However, once I enable ignite and
JCache, I run into proxy issues. Looks like I am hitting some serialization
problem,

Please review my code and help me troubleshoot this issue.


thanks in advance,

--daya--



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

Re: SQl Fields Query Using Java date

[siva]

Thank You for  reply


What are the classes for Date that you are using and what API are you using 
to execute queries? Also please post stacktrace that you observe. 

What are the classes for Date?
using java.util

Model Class
---
Class Employee 
{ 

String name; 
String address; 
  
@QuerySqlField(index = true) 
Date joinDate; 
} 

cache Configuration:


Ignite ignite = Ignition.ignite();
CacheConfiguration cacheCfg = new
CacheConfiguration<>(cacheName);
cacheCfg.setCacheMode(CacheMode.REPLICATED); // Default.

cacheCfg.setIndexedTypes(String.class, Employee.class);
cacheCfg.setAtomicityMode(atomic);
// client node will wait for write or commit on all 
particpating nodes

cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);

 IgniteCache cache =  
ignite.getOrCreateCache(cacheCfg);
 cache.put(key.trim(), employee); //getting Exception here
 



Exception while putting into cache

javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to serialize object [typeName=com.cva.model.Employee]


what API are you using  to execute queries?

using SqlFieldsQuery api 

query will be dynamic
it will be like select * from Employee,select * from Employee where name =
'cva',select * from Employee where joinDate = 10/6/2015 and 10/6/2016,
SqlFieldsQuery sql = new SqlFieldsQuery(query);
QueryCursor> cursor = cache.query(sql);




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

Re: Performance degradation in embed mode

[Ilya Kasnacheev]

Hello!

It looks like you have debug enabled when running inside Apache Tomcat.

Turning DEBUG on will make Ignite spend a lot of time and RAM building
debug messages. Please make sure to turn DEBUG off, at least for
org.apache.ignite packages.

Regards,


-- 
Ilya Kasnacheev

2018-08-14 11:45 GMT+03:00 Dmitriy :

> Hello Ilya,
>
> Thank you for the replay.
> So, I did ran the test after context initialization, but  the problem is
> persists.
>
> dump during test execution
>  t1980/threaddump_during.txt>
>
> dump after running the test
>  t1980/threaddump_after.txt>
>
> wbr,
>
> Dmitriy
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Some problems when using Ignite

[Ilya Kasnacheev]

Hello!

BinaryObject should be solving your issues. Can you please show how the
problem manifets if you don't restart cluster?

Regards,

-- 
Ilya Kasnacheev

2018-08-14 13:54 GMT+03:00 zym周煜敏 :

> Hi,
>
>
>
> Our company is now on a trial survey on Ignite. We found that if we want
> to alter the table schema or add a new table or even add an index when we
> use the Ignite SQL, we should change our code of the data injection,
> compile again, and then restart our ignite cluster to validate all the
> changes. We have tried BinaryObject, but it still needs pre-setting of the
> table schema and cluster restart. Are there any workarounds since it’s
> expensive to restart an industial cluster which may cause data loss? If
> not, will the latter version of Ignite support the dynamic changing of the
> table schema?
>
>
>
> Best Regards,
>
> Brian Zhou
>
> [image: new logo]
>
>
>

Re: SQl Fields Query Using Java date

[akurbanov]

Hi,

What are the classes for Date that you are using and what API are you using
to execute queries? Also please post stacktrace that you observe.

You might check some tests to see how it works in Ignite, for example:
IgniteCacheUpdateSqlQuerySelfTest.java

  
IgniteCacheInsertSqlQuerySelfTest.java

  



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

Re: Some problems when using Ignite

[dkarachentsev]

Hi,

Dynamic schema chages is available only via SQL/JDBC [1]. 
BTW caches created via SQL could be accessed from java API if you add
SQL_PUBLIC_ to table. For example: ignite.cache(SQL_PUBLIC_TABLENAME).

[1] https://apacheignite-sql.readme.io/docs/ddl

Thanks!
-Dmitry



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

Re: Eviction Policy on Dirty data

[dkarachentsev]

Hi,

Could you please explain how do you update database? Do you use CacheStore
with writeThrough or manually save?

Anyway, you can update data with custom eviction policy:
cache.withExpiryPolicy(policy) [1]

[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#withExpiryPolicy-javax.cache.expiry.ExpiryPolicy-

Thanks!
-Dmitry



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

SQl Fields Query Using Java date

[siva]

Hi,

How to  query Ignite based on date type (uisng sql fields query)?Is it
ignite support,if so do we need to add any configuration?

I was trying to put java object that contains a Date field, its throwing an
serialization Exception.

Class Employee
{

  String name;
  String address;
  
  @QuerySqlField(index = true)
  Date joinDate;
}





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

Eviction Policy on Dirty data

[monstereo]

Let's say, I have cache in ignite.
And one data is dirty(I mean, i have to upload correspond database for this
data)
Before updating, let's say I added one element to the cache and eviction
policy occured(and dirty data will be removed).

is there any mechanism to prevent eviction of dirty data before updating
correspond database?
or
this situation never becomes?



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

Some problems when using Ignite

[zym周煜敏]

Hi,

Our company is now on a trial survey on Ignite. We found that if we want to 
alter the table schema or add a new table or even add an index when we use the 
Ignite SQL, we should change our code of the data injection, compile again, and 
then restart our ignite cluster to validate all the changes. We have tried 
BinaryObject, but it still needs pre-setting of the table schema and cluster 
restart. Are there any workarounds since it’s expensive to restart an industial 
cluster which may cause data loss? If not, will the latter version of Ignite 
support the dynamic changing of the table schema?

Best Regards,
Brian Zhou
[new logo]

Re: how ignite c++ node set baselinetopology

[aealexsandrov]

Hi,

C++ API doesn't contain the methods to update the baseline. So, in this
case, you can use Java API for it:

Add the code that will listen to the EVT_NODE_JOINED event

private final IgniteEx ignite;

ignite.events().localListen(event -> {
DiscoveryEvent e = (DiscoveryEvent)event;

final long topVer = e.topologyVersion();

ignite.cluster().setBaselineTopology(topVer);

return true;
}, EventType.EVT_NODE_JOINED);

The whole example you can see here:

https://apacheignite.readme.io/docs/baseline-topology#section-triggering-rebalancing-programmatically

BR,
Andrei



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

Re: C++ client Exception occurred: Unexpected header during deserialization: 9

[aealexsandrov]

Hi,

Looks like something wrong with you serialization scheme. In case if you are
going to store some C++ object you should implement the READ and WRITE
methods like here:

https://apacheignite-cpp.readme.io/docs/serialization#section-macros

Could you please provide the cache configuration and implementation (.h,
.cpp) of your classes that will be used as key, value or part of the key,
value object? Also, provide their serialization schemes.

BR,
Andrei



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

Re: Performance degradation in embed mode

[Dmitriy]

Hello Ilya,

Thank you for the replay.
So, I did ran the test after context initialization, but  the problem is
persists.

dump during test execution

  

dump after running the test

  

wbr,

Dmitriy




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

Re: Possible issue with Web Console

[Vasiliy Sisko]

Hello @sv

Thank you for informing an error. I have reproduced it and created an issue
for fix. https://issues.apache.org/jira/browse/IGNITE-9262. 
Fix of that problem is expected in Ignite 2.7



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

client security (rest, .net\java clients, jdbc)

[wt]

we will be using a combination of .net and java client apps as well as jdbc
and rest. I know we need to implement our own security plugin but how can
this be applied to each access type (.net\java clients, rest,jdbc).

would i need to create different security plugins for each and if so are
they all based on the same API i.e
org.apache.ignite.internal.processors.security.*



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

Re: WebConsole does not see cluster

[Alexey Kuznetsov]

Hi,  KJQ!

You will need ignite-rest-http module in class path for those nodes that
you are planning to use as gateways for Web Console.
Having only one node will means that if this single node goes down - you
will lose connection to cluster from Web Console.

You may have several agents running and configured to communicate with
different nodes.
See  node-uri option in Web Agent "README.txt"

Or starting from Ignite 2.7 (already in master, but was not released yet)
you may specify several cluster nodes URIs as comma separated string.

>- I see in "caches" my cache.  Should I see my configurations in
> configurations as well or is that only for created ones?
It is not clear for me what did you mean.
Can you attach a screenshot with example?



On Tue, Aug 14, 2018 at 1:32 AM KJQ  wrote:

> So, I finally got this working.
>
> I ended up:
> - Copying the rest-http module into my main Ignite node (the only one who's
> IP i am using for discovery right now).
>
> - I shell into the running "ignite" instance and run the web agent from
> there (not outside the containers)
>
> Questions:
>
> - I see in "caches" my cache.  Should I see my configurations in
> configurations as well or is that only for created ones?
>
> - Where do I need the agent and rest api?  It seems like having it in the
> one node will suffice.  Do I need to have both on every node?
>
>
>
> -
> KJQ
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
> --
> Alexey Kuznetsov
> 
>