Re: Event Listeners

[vkulichenko]

Sam,

To avoid deserialization you can set CacheConfiguration#copyOnRead to false.

As for clear(), there is no notification for it. Who triggers it? Can the
client that calls clear(), then execute whatever needs to be executed as a
post-action? You can use compute APIs for this, for example.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14511.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Does the "Query Consistency" feature use MVCC?

[Jeff]

Thanks for the quick reply, Val.  To clarify the specific criteria, the
"query consistency" guarantee specifically refers to transactions started
(txStart) as either READ_REPEATABLE or SERIALIZABLE, and uses the put() and
get() APIs; correct?

On Fri, Jul 7, 2017 at 3:13 PM vkulichenko [via Apache Ignite Users] <
ml+s70518n14507...@n6.nabble.com> wrote:

> Hi Jeff,
>
> Transactional consistency and MVCC is (and always will be) available only
> for transactional caches. But for queries MVCC is not supported at all yet.
> Queries are not enlisted in transactions and therefore you can get dirty
> reads. Full support will be added by the end of the year (hopefully).
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-ignite-users.70518.x6.nabble.com/Does-the-Query-Consistency-feature-use-MVCC-tp14497p14507.html
> To unsubscribe from Does the "Query Consistency" feature use MVCC?, click
> here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Does-the-Query-Consistency-feature-use-MVCC-tp14497p14510.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Event Listeners

[javastuff....@gmail.com]

No. Near cache is one of the usecase, because of serializing/deserialize can
not use Ignite Near cache, it's a big overhead and negating benefits of near
cache altogether. 

In other usecases we need to notify all changes to cached data. In a
specific scenario, we have to remove all entries and same need to be
notified to all nodes.

Thansk,
-Sam





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14508.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: frequet disconnection in ignite cluster

[ignite_user2016]

Hello Val,

I have asked for such changes would keep you informed.

PS - our world is very slow so any changes would take 1-2 week of time.

Thanks..

On Fri, Jul 7, 2017 at 2:06 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n1450...@n6.nabble.com> wrote:

> Rishi,
>
> Does the issue go away if you stop triggering monitoring every 5 minutes.
> Such frequency is very small, it should not cause any issues of course.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/frequet-
> disconnection-in-ignite-cluster-tp14411p14505.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-ignite-cluster-tp14411p14506.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: frequet disconnection in ignite cluster

[vkulichenko]

Rishi,

Does the issue go away if you stop triggering monitoring every 5 minutes.
Such frequency is very small, it should not cause any issues of course.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-ignite-cluster-tp14411p14505.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Event Listeners

[vkulichenko]

Sam,

It sounds like you can set CacheConfiguration#invalidate property to true.
This will force Ignite to invalidate near cache entry on update rather that
syncing it with a new value. Is this what you're looking for?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14503.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Loading similar data to specific instance and not all instances

[vkulichenko]

Hi,

Can you please tell what is a business use case behind this? What exactly
are you trying to achieve with Ignite?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Loading-similar-data-to-specific-instance-and-not-all-instances-tp14387p14502.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Info

[vkulichenko]

Hi,


Riccardo Iacomini wrote
>- Will a local file system persistence strategy be available in future
>releases of Ignite?

The new disk storage will be available in 2.1.


Riccardo Iacomini wrote
>- Using the write-behind mode, will operations on the cache still be
>mapped 1 on 1 on the underlying persistence system, in my specific
> case,
>Cassandra?
> 
> Expanding on this, multiple operations on the same cache key will be all
> executed (in batch) when the write is triggered, or only the last version
> will be written?

Nothing changes if you use Cassandra or any other arbitrary store, this
functionality stays the same. New disk storage is not related to this.
Answering you particular question: it's controlled by
CacheConfiguration#writeBehindCoalescing property which is available in both
1.x and 2.x.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Info-tp14473p14501.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Info

[vkulichenko]

Hi,





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Info-tp14473p14499.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Connecting to remote host from client gives error

[vkulichenko]

It's something in your network. If you can't telnet to this address, Ignite
will obviously not able to connect either.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p14498.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Unable to start the ignite.sh in verbose mode

[vkulichenko]

Where is the error?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-the-ignite-sh-in-verbose-mode-tp14477p14496.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Does the "Query Consistency" feature use MVCC?

[Jeff]

Howdy!

I've read through the docs at https://apacheignite.readme.io but couldn't
find a definitive answer (even started diving into the source, but figured
I'd try here before going further).  The following is listed as a feature on
the Apache Ignite Datagrid website:

"Ignite provides full query consistency. Updates that happened after the
query execution started do not affect the query result."

>From the docs and JIRA ticket
(https://issues.apache.org/jira/browse/IGNITE-3478), it appears that SQL
queries do not yet support MVCC in relation to DataGrid Transactions (e.g.
If writing A and B in a transaction, able to get new A value but old B
value).

So, for getAll(), ScanQuery, etc. how is this supported?  Is it only when
the cache is set to TRANSACTIONAL?  I tried a quick test which modifies an
object of an ATOMIC cache during the SQL cursor iteration (and small page
size), but the previous value was returned.  Though I'm not sure if there is
an optimization/minimum value on the page size.

Fundamentally, my question is under what conditions (atomicity mode, query
type, etc.) is the query consistency guaranteed and how does Ignite ensure
this (e.g. MVCC, local cache for ongoing queries, etc.)

Thanks,
Jeff





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Does-the-Query-Consistency-feature-use-MVCC-tp14497.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 1.6.0 suspected memory leak from DynamicCacheDescriptor

[ignite_user2016]

Hello Val..

Thanks, will try out and let you know ...

On Fri, Jul 7, 2017 at 12:25 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n1449...@n6.nabble.com> wrote:

> Hi Rishi,
>
> ignite.cluster().nodes() will give the list of nodes and full information
> about topology. Will this work for you?
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14492.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14495.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Async Service proxy

[vkulichenko]

Artem,

The whole point of service proxy is to allow remote execution via API that
*you* created. Therefore, if this API returns some result, this can be done
only synchronously. In case there is no result, you can trigger async
execution within the service itself and return right away. Another option is
to use Compute Grid APIs directly.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Async-Service-proxy-tp14478p14494.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NodeFilter for cache and GridDhtPartitionsExchangeFuture (Failed to wait for partition release future)

[vkulichenko]

Vladimir wrote
> It is just a test. In real project, of course, there are many nodes
> holding the cache. Node A represents a part of cluster.

You can lose the whole cluster group as well. My point is that getting in
cache during initialization doesn't make it safe, because cache can
disappear in runtime and you have to handle such scenario anyway.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NodeFilter-for-cache-and-GridDhtPartitionsExchangeFuture-Failed-to-wait-for-partition-release-future-tp14179p14493.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 1.6.0 suspected memory leak from DynamicCacheDescriptor

[vkulichenko]

Hi Rishi,

ignite.cluster().nodes() will give the list of nodes and full information
about topology. Will this work for you?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14492.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 1.6.0 suspected memory leak from DynamicCacheDescriptor

[ignite_user2016]

Hello Val,

Do you have any example on it ? would like to see how can we leverage that
piece of code for monitoring ?

Thanks for all your help..


On Thu, Jul 6, 2017 at 5:46 PM, vkulichenko [via Apache Ignite Users] <
ml+s70518n14430...@n6.nabble.com> wrote:

> Tom,
>
> It sounds like these jobs are triggered pretty frequently. So why not
> create a small application that will create an embedded client once and
> also have an internal timer or cron based scheduler to execute jobs
> periodically. You can do the topology check within this application as
> well, instead of using Visor.
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14430.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14491.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: frequet disconnection in ignite cluster

[ignite_user2016]

Hello ..

Thanks for sharing the thread..

we have 4 core, 8 GB RAM mostly Ignite is used for 2nd level cache.

We have set our JVM to 1G RAM.

Then, wondering how would we monitor ignite without impacting the system ?

Thanks ...

On Thu, Jul 6, 2017 at 9:54 PM, tysli2016 [via Apache Ignite Users] <
ml+s70518n14442...@n6.nabble.com> wrote:

> Hi Rishi,
>
> seems it's not a good idea to connect ignite repeatedly, I observed a
> similar memory issue.
> would you mind to share your server configurations (cores, memory)?
>
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-
> 6-0-suspected-memory-leak-from-DynamicCacheDescriptor-td9443i20.html
>
> http://apache-ignite-users.70518.x6.nabble.com/OOME-on-2-
> node-cluster-with-visor-running-repeatedly-Ignite-1-9-tt12409.html
>
> Tom
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/frequet-
> disconnection-in-ignite-cluster-tp14411p14442.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>



-- 
Rishi Yagnik




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-ignite-cluster-tp14411p14490.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NodeFilter for cache and GridDhtPartitionsExchangeFuture (Failed to wait for partition release future)

[Vladimir]

>>> What is the exact scenario when cache is not available? If this means
absence of node A, then you can lose after initialization of B,

It is just a test. In real project, of course, there are many nodes holding
the cache. Node A represents a part of cluster.


>>> I would recommend to use Ignite#getOrCreateCache method 

Yes, on the nodes keeping and serving the cache. "Client" nodes don't
provide the cache configuration. They can only use cache(). I moved the
cache acquring in a handler of ContextRefreshedEvent. Looks enough for now.


>>> In addition, it sounds like node B can be a client which eliminates a
>>> requirement to have a node filter.

No. It's a server node for another purposes. We don't want to spread some
caches across whole cluster bit only on dedicated nodes. Often they are the
ones which need faster access to the cache.


>>> This sounds weird, I think there is some other factor that we're
>>> missing. Can you create a simple GitHub project that reproduces this
>>> behavior and share it with us? 

Ok. Once I get time I'll create a special topic.

Thanks



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NodeFilter-for-cache-and-GridDhtPartitionsExchangeFuture-Failed-to-wait-for-partition-release-future-tp14179p14489.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Information

[Mimmo Celano]

Thank you,

Sorry but I can not understand how to implement it. Could you please show
me an example of its use? I just started to use Ignite.

Thanks

2017-07-07 0:03 GMT+02:00 vkulichenko :

> Hi,
>
> See CacheConfiguration#nodeFilter property. It's just a predicate that
> filters out nodes, cache will be deployed only on those for which filter
> returns true. The easiest way would be to set custom attributes via
> IgniteConfiguration#userAttributes and filter out using
> AttributeNodeFilter
> which is provided out of the box.
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-Information-tp14330p14423.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: yardstick-ignite:ERROR: Driver process has not started on dserver1 during 10.0 seconds.

[Andrey Gura]

Hi,

are there any errors in driver and server logs?

Also please note, that you should have passwordless ssh access to localhost.

On Fri, Jul 7, 2017 at 3:29 PM, 罗 辉  wrote:
> Hello there
>
>I am new to Yarkstick, when I was running benckmark-run-all.sh with the
> attached property file, I usually see below error:
>
> ERROR: Driver process has not started on dserver1 during 10.0 seconds.
> Type "--help" for usage.
> <20:26:05> Driver is started on dserver1 with id=0
> <20:26:05> Driver is stopped on dserver1
> <20:26:06> Server is stopped on dserver2
> <20:26:06> Server is stopped on dserver3
> <20:26:06> Server is stopped on dserver4
> <20:26:06> Server is stopped on dserver5
>
> what is the reason this error takes place?
> thanks for any idea.
>

Re: How to set timeout for client node

[Andrey Gura]

Hi Gracelin,

I'm a bit confused. This particular ClassCastException can happen only
in user code because, as I can see, result set processing is already
in progress. So I don't understand where is relation between
connection timeout and hanging. You should correctly handle this
exception and just close your result set.

On Fri, Jul 7, 2017 at 2:20 PM, Gracelin Priya  wrote:
> Hello there,
>
>
>
> Test tool  which populates the gridgain cluster cache , had an error and it
> hanged @ the below point. It is not getting terminated automatically. It had
> to be killed for the client session to exit it.
>
>
>
> Exception in thread "main" java.lang.ClassCastException: java.lang.Short
> cannot be cast to java.lang.Integer
>
> at
> org.apache.ignite.internal.jdbc2.JdbcResultSet.getInt(JdbcResultSet.java:229)
>
>
>
>
>
> Is there any setting in gridgain xml/java which I can set so that the client
> connection should get disconnected after say 3 seconds if any error is seen.
>
>
>
> Any help on this is appreciated.
>
>
>
> Regards,
>
> Priya
>
>

Re: Dymanically add QueryField on Cache Entity and perform DateTime filter.

[Pavel Tupitsyn]

This can be tested with a nightly build right now:
https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds

> Install-Package Apache.Ignite -Pre -Source
https://www.myget.org/F/apache-ignite-net-nightly

On Fri, Jul 7, 2017 at 4:26 PM, Pavel Tupitsyn  wrote:

> Addition:
>
> In upcoming 2.1 version there is a BinaryReflectiveSerializer.F
> orceTimestamp property, which makes it write any DateTime as a Timestamp.
> So instead of a custom serializer, you can do this:
>
> BinaryConfiguration = new BinaryConfiguration
> {
> TypeConfigurations = new[] { new
> BinaryTypeConfiguration(typeof(ABC)) {
> Serializer = new BinaryReflectiveSerializer {ForceTimestamp = true} }}
> }
>
> On Wed, Jul 5, 2017 at 11:44 AM, ptupitsyn  wrote:
>
>> Hi,
>>
>> Please properly subscribe to the mailing list so that the community can
>> receive email notifications for your messages. To subscribe, send empty
>> email to user-subscr...@ignite.apache.org and follow simple instructions
>> in
>> the reply.
>>
>> I have reproduced the problem, it is caused by the fact that DateTime is
>> serialized in .NET-specific format by default, and this does not work in
>> SQL, see "DateTime and SQL" section:
>> https://apacheignite-net.readme.io/docs/sql-queries#section-
>> java-type-name-mapping
>>
>> To enforce SQL-compatible TimeStamp format:
>> 1) Mark the field with [QuerySqlField]. Looks like this is not an option
>> for
>> you, though, since reflection is used
>>
>> 2) Implement IBinarizable:
>>
>> public class ABC : IBinarizable
>> {
>> public int Id { get; set; }
>> public string Name { get; set; }
>> public DateTime StartTime { get; set; }
>>
>> public void WriteBinary(IBinaryWriter writer)
>> {
>> writer.WriteInt("Id", Id);
>> writer.WriteString("Name", Name);
>> writer.WriteTimestamp("StartTime", StartTime);
>> }
>>
>> public void ReadBinary(IBinaryReader reader)
>> {
>> Id = reader.ReadInt("Id");
>> Name = reader.ReadString("Name");
>> StartTime = reader.ReadTimestamp("StartTim
>> e").GetValueOrDefault();
>> }
>> }
>>
>> 3) Implement IBinarySerializer:
>>
>> public class AbcSerializer : IBinarySerializer
>> {
>> public void WriteBinary(object o, IBinaryWriter writer)
>> {
>> var abc = (ABC)o;
>>
>> writer.WriteInt("Id", abc.Id);
>> writer.WriteString("Name", abc.Name);
>> writer.WriteTimestamp("StartTime", abc.StartTime);
>> }
>>
>> public void ReadBinary(object o, IBinaryReader reader)
>> {
>> var abc = (ABC)o;
>>
>> abc.Id = reader.ReadInt("Id");
>> abc.Name = reader.ReadString("Name");
>> abc.StartTime = reader.ReadTimestamp("StartTim
>> e").GetValueOrDefault();
>> }
>> }
>>
>> and register it in config:
>> BinaryConfiguration = new BinaryConfiguration
>> {
>> TypeConfigurations = new[] { new
>> BinaryTypeConfiguration(typeof(ABC)) {
>> Serializer = new AbcSerializer() }}
>> }
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Dymanically-add-QueryField-on-Cache-
>> Entity-and-perform-DateTime-filter-tp14318p14319.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>

Re: Dymanically add QueryField on Cache Entity and perform DateTime filter.

[Pavel Tupitsyn]

Addition:

In upcoming 2.1 version there is a BinaryReflectiveSerializer.
ForceTimestamp property, which makes it write any DateTime as a Timestamp.
So instead of a custom serializer, you can do this:

BinaryConfiguration = new BinaryConfiguration
{
TypeConfigurations = new[] { new
BinaryTypeConfiguration(typeof(ABC)) {
Serializer = new BinaryReflectiveSerializer {ForceTimestamp = true} }}
}

On Wed, Jul 5, 2017 at 11:44 AM, ptupitsyn  wrote:

> Hi,
>
> Please properly subscribe to the mailing list so that the community can
> receive email notifications for your messages. To subscribe, send empty
> email to user-subscr...@ignite.apache.org and follow simple instructions
> in
> the reply.
>
> I have reproduced the problem, it is caused by the fact that DateTime is
> serialized in .NET-specific format by default, and this does not work in
> SQL, see "DateTime and SQL" section:
> https://apacheignite-net.readme.io/docs/sql-queries#
> section-java-type-name-mapping
>
> To enforce SQL-compatible TimeStamp format:
> 1) Mark the field with [QuerySqlField]. Looks like this is not an option
> for
> you, though, since reflection is used
>
> 2) Implement IBinarizable:
>
> public class ABC : IBinarizable
> {
> public int Id { get; set; }
> public string Name { get; set; }
> public DateTime StartTime { get; set; }
>
> public void WriteBinary(IBinaryWriter writer)
> {
> writer.WriteInt("Id", Id);
> writer.WriteString("Name", Name);
> writer.WriteTimestamp("StartTime", StartTime);
> }
>
> public void ReadBinary(IBinaryReader reader)
> {
> Id = reader.ReadInt("Id");
> Name = reader.ReadString("Name");
> StartTime = reader.ReadTimestamp("
> StartTime").GetValueOrDefault();
> }
> }
>
> 3) Implement IBinarySerializer:
>
> public class AbcSerializer : IBinarySerializer
> {
> public void WriteBinary(object o, IBinaryWriter writer)
> {
> var abc = (ABC)o;
>
> writer.WriteInt("Id", abc.Id);
> writer.WriteString("Name", abc.Name);
> writer.WriteTimestamp("StartTime", abc.StartTime);
> }
>
> public void ReadBinary(object o, IBinaryReader reader)
> {
> var abc = (ABC)o;
>
> abc.Id = reader.ReadInt("Id");
> abc.Name = reader.ReadString("Name");
> abc.StartTime = reader.ReadTimestamp("
> StartTime").GetValueOrDefault();
> }
> }
>
> and register it in config:
> BinaryConfiguration = new BinaryConfiguration
> {
> TypeConfigurations = new[] { new
> BinaryTypeConfiguration(typeof(ABC)) {
> Serializer = new AbcSerializer() }}
> }
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Dymanically-add-QueryField-on-
> Cache-Entity-and-perform-DateTime-filter-tp14318p14319.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

yardstick-ignite:ERROR: Driver process has not started on dserver1 during 10.0 seconds.

[罗 辉]

Hello there

   I am new to Yarkstick, when I was running benckmark-run-all.sh with the 
attached property file, I usually see below error:


ERROR: Driver process has not started on dserver1 during 10.0 seconds.
Type "--help" for usage.
<20:26:05> Driver is started on dserver1 with id=0
<20:26:05> Driver is stopped on dserver1
<20:26:06> Server is stopped on dserver2
<20:26:06> Server is stopped on dserver3
<20:26:06> Server is stopped on dserver4
<20:26:06> Server is stopped on dserver5

what is the reason this error takes place?
thanks for any idea.



test.properties
Description: test.properties

Ignite Visor - Help

[Gracelin Priya]

Hi,


1.   When starting ignitevisorcmd.sh, is there a option to provide the 
configuration file in the command prompt when starting.


2.   When ignitevisorcmd is started and open command is given it is not 
listing the configuration files which are kept outside IGNITE_HOME. Should all 
the xmls be copied in $IGNITE_HOME/config folder  to be listed or is there any 
way to get them also listed?



3.   Twenty entries are populated in employee cache. When listed in visor 
it is showing total as 40.  Heap size 20 and off-heap size 20. Can someone 
please explain? Employee cache is partitioned cache without any backup 
configured.


visor> cache -a
Time of the snapshot: 07/07/17, 17:49:22
+==+
|Name(@)|Mode | Nodes | Entries (Heap / Off-heap)  |   Hits
|  Misses   |   Reads   |  Writes   |
+==+
| Employee(@c0) | PARTITIONED | 1 | min: 40 (20 / 20)  | min: 0
| min: 0| min: 0| min: 0|
|   | |   | avg: 40.00 (20.00 / 20.00) | avg: 0.00 
| avg: 0.00 | avg: 0.00 | avg: 0.00 |
|   | |   | max: 40 (20 / 20)  | max: 0
| max: 0| max: 0| max: 0|
+--+

Cache 'Employee(@c0)':
+---+
| Name(@) | Employee(@c0)   |
| Nodes   | 1   |
| Total size Min/Avg/Max  | 40 / 40.00 / 40 |
|   Heap size Min/Avg/Max | 20 / 20.00 / 20 |
|   Off-heap size Min/Avg/Max | 20 / 20.00 / 20 |
+---+

Nodes for: Employee(@c0)
+=+
|  Node ID8(@), IP  | CPUs | Heap Used | CPU Load |   Up Time|  
   Size | Hi/Mi/Rd/Wr |
+=+
| 25F9F385(@n0), 10.2.0.160 | 32   | 3.10 %| 0.23 %   | 01:03:30:527 | 
Total: 40| Hi: 0   |
|   |  |   |  |  |   
Heap: 20   | Mi: 0   |
|   |  |   |  |  |   
Off-Heap: 20   | Rd: 0   |
|   |  |   |  |  |   
Off-Heap Memory: 0 | Wr: 0   |
+-+
'Hi' - Number of cache hits.
'Mi' - Number of cache misses.
'Rd' - number of cache reads.
'Wr' - Number of cache writes.

Thanks,
Priya

Re: slow performance when using order by clause

[Andrey Mashenkov]

Hi Neeraj,

Try to change join order and enable option
SqlFieldsQuery.enforceJoinOrder(true).
Sometimes, changing join order can significantly improve performance.

On Fri, Jul 7, 2017 at 9:20 AM, neerajbhatt 
wrote:

> explain plan without order by
>
>
> FROM ITEMCACHE.ITEM T__Z0
> /* ITEMCACHE.ITEM_RATING_IDX: RATING = ?1 */
> /* WHERE (T__Z0.RATING = ?1)
> AND ((T__Z0.DOWNLOADS = ?3)
> AND (T__Z0.REVIEWS = ?2))
> */
> INNER JOIN IGPCACHE.RANK R__Z1
> /* IGPCACHE.RANK_UNIQUESKUID_IDX: UNIQUESKUID = T__Z0.UNIQUESKUID */
> ON 1=1
> WHERE (T__Z0.DOWNLOADS = ?3)
> AND ((T__Z0.REVIEWS = ?2)
> AND ((T__Z0.RATING = ?1)
> AND (T__Z0.UNIQUESKUID = R__Z1.UNIQUESKUID)))
> LIMIT 10
> SELECT
> __C0_0 AS _VAL
> FROM PUBLIC.__T0
> /* IGPCACHE.merge_scan */
> LIMIT 10
>
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/slow-performance-when-using-order-
> by-clause-tp14389p14470.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov

How to set timeout for client node

[Gracelin Priya]

Hello there,

Test tool  which populates the gridgain cluster cache , had an error and it 
hanged @ the below point. It is not getting terminated automatically. It had to 
be killed for the client session to exit it.

Exception in thread "main" java.lang.ClassCastException: java.lang.Short cannot 
be cast to java.lang.Integer
at 
org.apache.ignite.internal.jdbc2.JdbcResultSet.getInt(JdbcResultSet.java:229)


Is there any setting in gridgain xml/java which I can set so that the client 
connection should get disconnected after say 3 seconds if any error is seen.

Any help on this is appreciated.

Regards,
Priya

Async Service proxy

[Artёm Basov]

Hi guys!

Is there any ways to keep asynchronous nature of ignite Service proxy
implementation?

The main reason for us to use Services over plain Compute is that we need to
spread logic in separate JVM or else we would have to do tedious refactoring
in order to avoid dll hell (we use JNI extensively).

It looks like under the hood it uses IgniteFuture but"blocks for us". Is
there are particular reason for blocking on future.get() ?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Async-Service-proxy-tp14478.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Unable to start the ignite.sh in verbose mode

[sanaraya]

Hi ,
Please help me on the below error while starting the ignite.sh in verbose
mode

>>>__  
>>>   /  _/ ___/ |/ /  _/_  __/ __/
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/
>>>
>>> ver. 2.0.0#20170703-sha1:7f41436f
>>> 2017 Copyright(C) Apache Software Foundation
>>>
>>> Ignite documentation: http://ignite.apache.org

[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Config URL:
file:/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/config/default-config.xml
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Daemon mode: off
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] OS: Linux 4.4.0-22-generic
amd64
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] OS user: root
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] PID: 9316
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Language runtime: Java
Platform API Specification ver. 1.8
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] VM information: OpenJDK
Runtime Environment 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11 Oracle
Corporation OpenJDK 64-Bit Server VM 25.131-b11
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] VM total memory: 0.96GB
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Remote Management [restart:
on, REST: on, JMX (remote: on, port: 49148, auth: off, ssl: off)]
[07-07-2017 16:00:24][INFO ][main][IgniteKernal]
IGNITE_HOME=/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] VM arguments: [-Xms1g,
-Xmx1g, -XX:+AggressiveOpts, -XX:MaxMetaspaceSize=256m, -ea,
-DIGNITE_QUIET=true,
-DIGNITE_SUCCESS_FILE=/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/work/ignite_success_c6323e15-c6da-4491-a96c-dec4ca76a546,
-Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49148,
-Dcom.sun.management.jmxremote.authenticate=false,
-Dcom.sun.management.jmxremote.ssl=false, -DIGNITE_UPDATE_NOTIFIER=false,
-DIGNITE_HOME=/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src,
-DIGNITE_PROG_NAME=./ignite.sh]
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] System cache's MemoryPolicy
size is configured to 40 MB. Use MemoryConfiguration.systemCacheMemorySize
property to change the setting.
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Configured caches [in
'default' memoryPolicy: ['ignite-sys-cache', 'ignite-hadoop-mr-sys-cache',
'ignite-atomics-sys-cache']]
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] 3-rd party licenses can be
found at: /root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/libs/licenses
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor] Configured
plugins:
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]   ^--
TestPlatformPlugin 1.0
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]   ^-- -
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]   ^--
TestReconnectPlugin 1.0
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]   ^--
[07-07-2017 16:00:24][INFO ][main][IgnitePluginProcessor]
[07-07-2017 16:00:24][INFO ][main][TcpCommunicationSpi] Successfully bound
communication NIO server to TCP port [port=47100, locHost=0.0.0.0/0.0.0.0,
selectorsCnt=4, selectorSpins=0, pairedConn=false]
[07-Jul-2017 16:00:24][WARN ][main][TcpCommunicationSpi] Message queue limit
is set to 0 which may lead to potential OOMEs when running cache operations
in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender
and receiver sides.
[07-Jul-2017 16:00:24][WARN ][main][NoopCheckpointSpi] Checkpoints are
disabled (to enable configure any GridCheckpointSpi implementation)
[07-Jul-2017 16:00:24][WARN ][main][GridCollisionManager] Collision
resolution is disabled (all jobs will be activated upon arrival).
[07-07-2017 16:00:24][INFO ][main][IgniteKernal] Security status
[authentication=off, tls/ssl=off]
[07-Jul-2017 16:00:24][WARN ][main][IgniteCacheDatabaseSharedManager] No
user-defined default MemoryPolicy found; system default of 1GB size will be
used.
[07-07-2017 16:00:24][INFO ][main][GridTcpRestProtocol] Command protocol
successfully started [name=TCP binary, host=0.0.0.0/0.0.0.0, port=11211]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/modules/rest-http/target/libs/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/modules/visor-plugins/target/libs/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/root/ApacheIgnite_2.0/apache-ignite-2.0.0-src/modules/zookeeper/target/libs/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[07-07-2017 16:00:25][INFO ][main][GridJettyRestProtocol] Command protocol
successfully started [name=Jetty REST, host=/0.0.0.0, port=8081]
[07-Jul-2017 

Re: Poor cross cache join SQL performance (v2.0.0)

[Alexander Fedotov]

Hi,

It would be great to take a look on a corresponding JFR.

Kind regards,
Alex


6 июля 2017 г. 11:55 AM пользователь "afedotov" <
alexander.fedot...@gmail.com> написал:

Could you please share the reproducer?

Kind regards,
Alex

6 июля 2017 г. 11:18 AM пользователь "iostream [via Apache Ignite
Users]" <[hidden
email] > написал:

> Hi Alex,
>
> Yes Value2.class was already added to indextypes.
>
> I am only reading the value which is why copyOnRead is set to "false".
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Poor-cross-
> cache-join-SQL-performance-v2-0-0-tp14373p14382.html
> To start a new topic under Apache Ignite Users, email [hidden email]
> 
> To unsubscribe from Apache Ignite Users, click here.
> NAML
> 
>

--
View this message in context: Re: Poor cross cache join SQL performance
(v2.0.0)

Sent from the Apache Ignite Users mailing list archive
 at Nabble.com.

Re: Connecting to remote host from client gives error

[abhishek dutta gupta]

Failed to initialize connection (this can happen due to short time network
problems and can be ignored if does not
affect node discovery)
[sock=Socket[addr=/10.133.71.210,port=32934,localport=47500]]
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:5587)
at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


While I am trying to do telnet host port it gives the above error? I am also
unable to connect to this through client:

System.out.println("Test Ignite!!");
String cacheId = "partitioned";
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
TcpDiscoveryMulticastIpFinder tcMp = new
TcpDiscoveryMulticastIpFinder();
tcMp.setAddresses(Arrays.asList("10.133.71.210",
"10.133.71.210:47500..47501"));
spi.setIpFinder(tcMp);

   // final String
PATH="/Users/shamim/Development/java/datafabrics/apache-ignite-fabric-1.5.0.final-bin/examples/config/example-cache.xml";
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClientMode(true);
cfg.setDiscoverySpi(spi);
// Start ignite
Ignite ignite = Ignition.start(cfg);

// get or create cache
IgniteCache cache =
ignite.getOrCreateCache("myCacheName");
for(int i = 1; i < 100; i++){
cache.put(i, Integer.toString(i));
}
for(int i =1; i<100;i++){
System.out.println("Cache get:"+ cache.get(i));
}
// statistics
System.out.println("Cache Size:"+
cache.metrics(ignite.cluster()).getSize());
ignite.close(); 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p14475.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Connecting to remote host from client gives error

[abhishek dutta gupta]

Failed to initialize connection (this can happen due to short time network
problems and can be ignored if does not 
affect node discovery)
[sock=Socket[addr=/10.133.71.210,port=32934,localport=47500]]
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:5587)
at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


While I am trying to do telnet host port it gives the above error? I am also
unable to connect to this through client:

System.out.println("Test Ignite!!");
String cacheId = "partitioned";
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
TcpDiscoveryMulticastIpFinder tcMp = new
TcpDiscoveryMulticastIpFinder();
tcMp.setAddresses(Arrays.asList("10.133.71.210",
"10.133.71.210:47500..47501"));
spi.setIpFinder(tcMp);

   // final String
PATH="/Users/shamim/Development/java/datafabrics/apache-ignite-fabric-1.5.0.final-bin/examples/config/example-cache.xml";
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setClientMode(true);
cfg.setDiscoverySpi(spi);
// Start ignite
Ignite ignite = Ignition.start(cfg);

// get or create cache
IgniteCache cache =
ignite.getOrCreateCache("myCacheName");
for(int i = 1; i < 100; i++){
cache.put(i, Integer.toString(i));
}
for(int i =1; i<100;i++){
System.out.println("Cache get:"+ cache.get(i));
}
// statistics
System.out.println("Cache Size:"+
cache.metrics(ignite.cluster()).getSize());
ignite.close();



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p14474.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignite Info

[Riccardo Iacomini]

Hello,
I would like to ask a few questions:

   - Will a local file system persistence strategy be available in future
   releases of Ignite?

   - Using the write-behind mode, will operations on the cache still be
   mapped 1 on 1 on the underlying persistence system, in my specific case,
   Cassandra?

   Expanding on this, multiple operations on the same cache key will be all
   executed (in batch) when the write is triggered, or only the last version
   will be written?


Best

Riccardo Iacomini


*RDSLab*

Re: Loading similar data to specific instance and not all instances

[Aiden]

Hello all,

I'm totally a newbie here, so just bear with me. I followed through this
link:
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/affinity/AffinityKeyMapper.java

  

I tried to apply the same procedure as prescribed. Unfortunately due to some
error from my side i'm just not able to create this affinity key mapping.

I'm forwarding my BEAN Class and my server.xml(generated using ignite web
console).

Persons.java
  
RemoteIgniteCluster-server.xml

  

Age
*
50
60
70
80
90
100
10
20
30
40
110


As u can see, Age is 1 column in the database table that i'm trying to load
to the ignite cache partition. Every value in Age ends with 0. I have two
ignite instances A, B. When i'm loading the above table to ignite partition.
It should have to load to either A or B completely and NOT BOTH. 

I understand for this, AffinityKeyMapper can be used. But i'm not being able
to understand in what way. 

Can somebody please take time to tell me what all changes i have to do in my
in my bean class and my server.xml to bring about this change. I'd
appreciate it a lot.

Thanks in advance..



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Loading-similar-data-to-specific-instance-and-not-all-instances-tp14387p14471.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: slow performance when using order by clause

[neerajbhatt]

explain plan without order by


FROM ITEMCACHE.ITEM T__Z0
/* ITEMCACHE.ITEM_RATING_IDX: RATING = ?1 */
/* WHERE (T__Z0.RATING = ?1)
AND ((T__Z0.DOWNLOADS = ?3)
AND (T__Z0.REVIEWS = ?2))
*/
INNER JOIN IGPCACHE.RANK R__Z1
/* IGPCACHE.RANK_UNIQUESKUID_IDX: UNIQUESKUID = T__Z0.UNIQUESKUID */
ON 1=1
WHERE (T__Z0.DOWNLOADS = ?3)
AND ((T__Z0.REVIEWS = ?2)
AND ((T__Z0.RATING = ?1)
AND (T__Z0.UNIQUESKUID = R__Z1.UNIQUESKUID)))
LIMIT 10
SELECT
__C0_0 AS _VAL
FROM PUBLIC.__T0
/* IGPCACHE.merge_scan */
LIMIT 10






--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/slow-performance-when-using-order-by-clause-tp14389p14470.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.