RE: Missing object when loading from Cassandra with multiple queries

[vkulichenko]

Roger,

If they are not needed, they should be part of value object rather than key
object. When you create a key object to do a cache lookup or other
operation, you should provide exact fields for all values included in it.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Missing-object-when-loading-from-Cassandra-with-multiple-queries-tp15644p15754.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

RE: Missing object when loading from Cassandra with multiple queries

[Roger Fischer (CW)]

Thanks, Val.

The two fields are sufficient as the primary key. The "hour" field is the 
truncated dateTime, and "bucket" is a grouping of the PortIds.

Roger

-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com] 
Sent: Thursday, July 27, 2017 2:56 PM
To: user@ignite.apache.org
Subject: RE: Missing object when loading from Cassandra with multiple queries

Roger,

Since Ignite stores data in binary format, ыщ it basically ignores your 
hashCode and equals implementations. However, I see that in these methods you 
use only two fields out of four which makes me think that you can create two 
keys with same portId and dateTime, but different hour and bucket, and expect 
them to be equal. This definitely can cause issue like you described, you 
should identify key by all fields included in it.

Can this be the case?

-Val



--
View this message in context: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_Missing-2Dobject-2Dwhen-2Dloading-2Dfrom-2DCassandra-2Dwith-2Dmultiple-2Dqueries-2Dtp15644p15748.html=DwIFaQ=IL_XqQWOjubgfqINi2jTzg=1esZO0r0bYS90lcsaLA6N4AFxuNo6lzauhETGwdJQoQ=S46CnMWTAP0BmHV0GtebdoVXMlXsKw6iO653LG_TS2g=68xajupHZjoD9vAWkccGM58rBcNAFuc48S-eZfDuYYE=
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

About Apache Ignite in Japanese

[vkulichenko]

Well, the world has to know about this :) One of our committers, Roman
Shtykh, wrote an article about Ignite's latest features in Japanese
language! Such a bummer I can't read it, but looks awesome:
https://techblog.yahoo.co.jp/oss/ignite_newmemory/

-Val



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

Re: ignite TcpDiscoveryKubernetesIpFinder properties

[Patrick Blaas]

awsome thanks for this. Works like a charm now.

regards,
Patrick

On Thu, Jul 27, 2017 at 11:57 PM, vkulichenko  wrote:

> Sorry, copy-paste problem :)
>
> 
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/ignite-TcpDiscoveryKubernetesIpFinder
> -properties-tp15741p15749.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
met vriendelijke groet / with kind regards,

Patrick Blaas

Re: ignite TcpDiscoveryKubernetesIpFinder properties

[vkulichenko]

Sorry, copy-paste problem :)



-Val



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

[ANNOUNCE] Apache Ignite 2.1.0 Released

[Denis Magda]

The Apache Ignite Community is pleased to announce the release of Apache Ignite 
2.1.0 [1].
https://blogs.apache.org/ignite/entry/apache-ignite-2-1-a

This release incorporates a tremendous feature that was donated to the project 
- Ignite Persistent Store that altogether with the Durable Memory architecture 
empowers your applications with in-memory performance and durability of the 
disk.

The Ignite Persistent Store is a distributed ACID and SQL-compliant disk store 
that transparently integrates with Ignite as an optional disk tier (SSD, Flash, 
3D XPoint). Having the store enabled, you no longer need to keep all the data 
in memory or warm RAM up after the whole cluster restart. The persistent store 
will keep the superset of data and all the SQL indexes on disk making Ignite 
fully operational from disk. 

Considering these and many other changes we redefined the definition of Ignite 
a bit that know sounds:

Ignite is a memory-centric platform
• combining a distributed SQL database
• with a key-value data grid
• that is ACID-compliant
• and horizontally scalable

Learn more about the transition from the in-memory to memory-centric 
architecture from 2.1 announcement blog post: 
https://blogs.apache.org/ignite/entry/apache-ignite-2-1-a

Attend the meetup today in Bay Area, CA to get insights on the new additions: 
https://www.meetup.com/Bay-Area-In-Memory-Computing/events/241381155/

In addition the release includes support for CREATE and DROP table commands, 
adds new Machine Learning algorithms such as K-means clustering and 
regressions, enables peer-class-loading for .NET and provides Compute Grid APIs 
for C++.

The full list of the changes can be found here: 
https://ignite.apache.org/releases/2.1.0/release_notes.html

Please visit this page and check the release out:
https://ignite.apache.org/download.cgi


Regards,
Denis

[1] https://ignite.apache.org

RE: Missing object when loading from Cassandra with multiple queries

[vkulichenko]

Roger,

Since Ignite stores data in binary format, ыщ it basically ignores your
hashCode and equals implementations. However, I see that in these methods
you use only two fields out of four which makes me think that you can create
two keys with same portId and dateTime, but different hour and bucket, and
expect them to be equal. This definitely can cause issue like you described,
you should identify key by all fields included in it.

Can this be the case?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Missing-object-when-loading-from-Cassandra-with-multiple-queries-tp15644p15748.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Apache Ignite Site Changed its Face

[Denis Magda]

Igniters,

In favor of the 2.1 release we’ve reworked and renewed the front page and some 
of the existing pages of the site:
https://ignite.apache.org

The front page reflects the main additions of 2.1, durable memory + persistent 
store, that opened new opportunities for Ignite. Please welcome new Ignite that 
“provides in-memory performance with the durability of disk”:
https://twitter.com/denismagda/status/890683287852601345

—
Denis

Re: ignite TcpDiscoveryKubernetesIpFinder properties

[Patrick Blaas]

Hi Val,

Your response looks exactly what I already defined. What am i missing here ?

On Thu, Jul 27, 2017 at 10:46 PM, vkulichenko  wrote:

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



-- 
met vriendelijke groet / with kind regards,

Patrick Blaas

Re: Failure to deserialize simple model object

[vkulichenko]

Franck,

I see only POM file attached. Can you attach the whole project you're
referring to?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failure-to-deserialize-simple-model-object-tp15440p15745.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite TcpDiscoveryKubernetesIpFinder properties

[vkulichenko]

-Val



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

Re: [Paging] QueryCursor and SqlQuery

[vkulichenko]

For pagination you should use 'OFFSET .. LIMIT ..' syntax. Note that you
should also order the result set (use ORDER BY) in this case, because
otherwise ordering is undefined and you can get weird results.

-Val



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

Re: B+ Tree, Index Pages and Memory Region

[vkulichenko]

This is answered on SO:
https://stackoverflow.com/questions/45337691/b-tree-and-index-page-in-apache-ignite

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/B-Tree-Index-Pages-and-Memory-Region-tp15740p15742.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache performance in multi-threaded environment

[Vladimir Chmakov]

Hi Nikolai,

Thank you for the prompt reply. 
Hopefully I fixed the issues with subscription, thank you pointing at that.
You suggested option #1 for the cache instance usage when it is cached
locally and used by multiple threads. Actually, this is the way we
implemented our PoC and we will keep up with this approach – thank you for
the suggestion. Also your advice renders my second question invalid as the
approach I was asking about seems to be wrong, so the reproducer doesn’t
make much sense. 
We will keep testing with respect to the performance numbers and will advise
if we find something that would alarm us.

Regards, 
Vladimir






--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cache-performance-in-multi-threaded-environment-tp15698p15738.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Streaming data from concurrently from multiple nodes/data streamers - hangs

[Nikolai Tikhonov]

Hi,

Could you please share thread dump from all nodes?

On Thu, Jul 27, 2017 at 6:01 PM, Raja  wrote:

> Is it right to use data streamers from multiple nodes concurrently to
> ingest
> into the same cache?
>
> If I ingest data from a single node and multiple threads it works just
> fine.
> But when I ingests from multiple nodes it hangs (I get Unable to exchange
> partitions error)
>
>
> Any thoughts?
>
> Thank you
> Raja
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Streaming-data-from-concurrently-from-
> multiple-nodes-data-streamers-hangs-tp15735.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Streaming data from concurrently from multiple nodes/data streamers - hangs

[Raja]

Is it right to use data streamers from multiple nodes concurrently to ingest
into the same cache? 

If I ingest data from a single node and multiple threads it works just fine.
But when I ingests from multiple nodes it hangs (I get Unable to exchange
partitions error)


Any thoughts?

Thank you
Raja



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Streaming-data-from-concurrently-from-multiple-nodes-data-streamers-hangs-tp15735.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite Python issue

[Valeriy]

Can someone help or advise?



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

Re: Does it reveal some problems?

[Nikolai Tikhonov]

More details about Page Memory you can found there
https://apacheignite.readme.io/docs/page-memory

On Thu, Jul 27, 2017 at 3:46 PM, Nikolai Tikhonov 
wrote:

> Hi,
>
> Could you share full logs? From this messages I don't see any problem,
> it's just statistic of usage page memory.
>
> On Thu, Jul 27, 2017 at 2:12 PM, Bob Li <2789106...@qq.com> wrote:
>
>> From this worklog(you can find it in IGNITE_HOME/work/log):
>> [19:08:55,734][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
>> FreeList
>> [name=null, buckets=256, dataPages=70068, reusePages=20]
>>
>> Does "grid-timeout-worker" indicate my grid has timeout problem?
>> and  what's meaning of this log?
>> thanks.
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Does-it-reveal-some-problems-tp15724.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>

Re: Does it reveal some problems?

[Nikolai Tikhonov]

Hi,

Could you share full logs? From this messages I don't see any problem, it's
just statistic of usage page memory.

On Thu, Jul 27, 2017 at 2:12 PM, Bob Li <2789106...@qq.com> wrote:

> From this worklog(you can find it in IGNITE_HOME/work/log):
> [19:08:55,734][INFO ][grid-timeout-worker-#23%null%][IgniteKernal]
> FreeList
> [name=null, buckets=256, dataPages=70068, reusePages=20]
>
> Does "grid-timeout-worker" indicate my grid has timeout problem?
> and  what's meaning of this log?
> thanks.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Does-it-reveal-some-problems-tp15724.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: [Paging] QueryCursor and SqlQuery

[Nikolai Tikhonov]

Hi,

Ignite API does not provide pagination out of box. You can achieve it by
your SQL query as in most of DB.

On Thu, Jul 27, 2017 at 4:33 AM, woo charles 
wrote:

> Hi,
> How can I do paging when query from ignite cache?
>
> Can I get records by range? specific page?
>
> If I have 1 rows of records with page size set to 20, how can I get
> the 21-40 (Page 2)?
>
>

Re: Node discovery between IPV4 and IPV6 nodes

[Andrey Mashenkov]

Possibly, you face a bug when IPv6 address is in use [1].

[1] https://issues.apache.org/jira/browse/IGNITE-3011

On Thu, Jul 27, 2017 at 3:02 PM, afedotov 
wrote:

> Hello,
>
> Please properly subscribe to the mailing list so that the community can
> receive email notifications for your messages.
> To subscribe, send an empty email to [hidden email]
>  and follow simple
> instructions in the reply.
>
> Have you tried setting -Djava.net.preferIPv4Stack=true for all the
> participating nodes?
>
> Kind regards,
> Alex.
>
> On Thu, Jul 27, 2017 at 1:52 PM, tbmvenkat [via Apache Ignite Users] <[hidden
> email] > wrote:
>
>> Hello everyone,
>> I am facing issues node discovery issues between nodes on community
>> AMIs.  The issue has been identified to be caused by network setup.  Some
>> of the nodes use IPV4 and some use IPV6.  Any comments on how to overcome
>> the issue. Thanks.
>>
>> Regards
>> Venkatesh
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-ignite-users.70518.x6.nabble.com/Node-discover
>> y-between-IPV4-and-IPV6-nodes-tp15723.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: Node discovery between IPV4 and IPV6
> nodes
> 
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov

Re: using user defined object as key in ignite c++ client

[Igor Sapego]

Hi,

You need to declare matching class in C++ and specialize
BinaryType template for it as described at [1].

You can find which type in C++ matches which type from
Java at [2].

[1] - https://apacheignite-cpp.readme.io/docs/serialization
[2] -
https://apacheignite-cpp.readme.io/docs/cross-platform-interoperability#section-basic-types-compatibility

Best Regards,
Igor

On Thu, Jul 27, 2017 at 2:53 PM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:

> Hi.. I was able to run a sample c++ client program , loading/retrieving
> cache
> from a table in  persistent store. The table has just one int field as
> primary key and for cache I configured this primary key int as the cache
> key. But now I want to use cache for table in persistent store which have
> combination of different fields as primary key. What should I use as a
> cache
> key in this situation? Just like I used POJO to map cache values, should I
> use another POJO for cache keys?If so how should I map cache key POJO to
> c++?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/using-user-defined-object-as-key-in-
> ignite-c-client-tp15727.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Node discovery between IPV4 and IPV6 nodes

[afedotov]

Hello,

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages.
To subscribe, send an empty email to user-subscr...@ignite.apache.org and
follow simple instructions in the reply.

Have you tried setting -Djava.net.preferIPv4Stack=true for all the
participating nodes?

Kind regards,
Alex.

On Thu, Jul 27, 2017 at 1:52 PM, tbmvenkat [via Apache Ignite Users] <
ml+s70518n15723...@n6.nabble.com> wrote:

> Hello everyone,
> I am facing issues node discovery issues between nodes on community AMIs.
> The issue has been identified to be caused by network setup.  Some of the
> nodes use IPV4 and some use IPV6.  Any comments on how to overcome the
> issue. Thanks.
>
> Regards
> Venkatesh
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Node-
> discovery-between-IPV4-and-IPV6-nodes-tp15723.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
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Node-discovery-between-IPV4-and-IPV6-nodes-tp15723p15729.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Zeppelin-0.7.2: java.lang.IllegalArgumentException: Command line can not be null

[slava.koptilin]

Hello,

I see only the following error: Could not extract archive:
'D:\installed\apache-maven-3.5.0\repository\com\github\eirslett\yarn\0.18.1\yarn-0.18.1.\yarn-v0.18.1.tar.gz'
 
and It seems it is not related to Ignite.

I think, it would be better to ask Apache Zeppelin community about that
(us...@zeppelin.apache.org)

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Zeppelin-0-7-2-java-lang-IllegalArgumentException-Command-line-can-not-be-null-tp15680p15726.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

how to append data to IGFS so that data gets saved to Hive partitioned table?

[csumi]

I have a Hive partitioned table as below:

create table stocks (stock string, time timestamp, price float) PARTITIONED
BY (years bigint, months bigint, days bigint) ROW FORMAT DELIMITED FIELDS
TERMINATED BY ',';

Data is getting saved in HDFS through IGFS when I pass comma separated
string to the fs.append method but when I query on Hive there is no row
coming.

If I remove the partition while creating the table, I am able to fetch rows
from hive.

What could be wrong here? How can we save data to a partitioned table
through IGFS?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/how-to-append-data-to-IGFS-so-that-data-gets-saved-to-Hive-partitioned-table-tp15725.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Does it reveal some problems?

[Bob Li]

>From this worklog(you can find it in IGNITE_HOME/work/log):
[19:08:55,734][INFO ][grid-timeout-worker-#23%null%][IgniteKernal] FreeList
[name=null, buckets=256, dataPages=70068, reusePages=20] 

Does "grid-timeout-worker" indicate my grid has timeout problem?
and  what's meaning of this log?
thanks.




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Does-it-reveal-some-problems-tp15724.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Zeppelin-0.7.2: java.lang.IllegalArgumentException: Command line can not be null

[Bob Li]

thanks.

I downloaded incubator-zeppelin 's codes, ran "mvn install
-Dignite-version=2.0.0 -DskipTests",
encountered the following errors:

[INFO] Installing Yarn version v0.18.1
[WARNING] Failed to delete existing Yarn installation.
[INFO] Unpacking
D:\installed\apache-maven-3.5.0\repository\com\github\eirslett\yarn\0.18.1\yarn-0.18.1.\yarn-v0.18.1.tar.gz
into D:\oss\incubator-zeppelin\zepp
elin-web\node\yarn
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Zeppelin ... SUCCESS [08:28
min]
[INFO] Zeppelin: Interpreter .. SUCCESS [ 19.046
s]
[INFO] Zeppelin: Zengine .. SUCCESS [ 15.368
s]
[INFO] Zeppelin: Display system apis .. SUCCESS [  5.746
s]
[INFO] Zeppelin: Spark dependencies ... SUCCESS [01:50
min]
[INFO] Zeppelin: Groovy interpreter ... SUCCESS [  7.989
s]
[INFO] Zeppelin: Spark  SUCCESS [ 13.077
s]
[INFO] Zeppelin: Markdown interpreter . SUCCESS [  3.769
s]
[INFO] Zeppelin: Angular interpreter .. SUCCESS [  3.710
s]
[INFO] Zeppelin: Shell interpreter  SUCCESS [  3.921
s]
[INFO] Zeppelin: Livy interpreter . SUCCESS [  9.666
s]
[INFO] Zeppelin: HBase interpreter  SUCCESS [  8.000
s]
[INFO] Zeppelin: Apache Pig Interpreter ... SUCCESS [  8.971
s]
[INFO] Zeppelin: JDBC interpreter . SUCCESS [  4.558
s]
[INFO] Zeppelin: File System Interpreters . SUCCESS [  4.318
s]
[INFO] Zeppelin: Flink  SUCCESS [  6.369
s]
[INFO] Zeppelin: Apache Ignite interpreter  SUCCESS [  3.694
s]
[INFO] Zeppelin: Kylin interpreter  SUCCESS [  3.390
s]
[INFO] Zeppelin: Python interpreter ... SUCCESS [ 43.532
s]
[INFO] Zeppelin: Lens interpreter . SUCCESS [  6.363
s]
[INFO] Zeppelin: Apache Cassandra interpreter . SUCCESS [ 13.985
s]
[INFO] Zeppelin: Elasticsearch interpreter  SUCCESS [  6.491
s]
[INFO] Zeppelin: BigQuery interpreter . SUCCESS [  3.791
s]
[INFO] Zeppelin: Alluxio interpreter .. SUCCESS [  5.309
s]
[INFO] Zeppelin: Scio . SUCCESS [ 38.286
s]
[INFO] Zeppelin: web Application .. FAILURE [  4.433
s]
[INFO] Zeppelin: Server ... SKIPPED
[INFO] Zeppelin: Jupyter Support .. SKIPPED
[INFO] Zeppelin: Packaging distribution ... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 14:23 min
[INFO] Finished at: 2017-07-27T18:30:26+08:00
[INFO] Final Memory: 154M/1060M
[INFO]

[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.3:install-node-and-yarn (install
node and yarn) on project zeppelin-web: Could not ex
tract the Yarn archive: Could not extract archive:
'D:\installed\apache-maven-3.5.0\repository\com\github\eirslett\yarn\0.18.1\yarn-0.18.1.\yarn-v0.18.1.tar.gz'
: EOFException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.github.eirslett:frontend-maven-plugin:1.3:install-node-and-yarn
(install node
 and yarn) on project zeppelin-web: Could not extract the Yarn archive:
Could not extract archive:
'D:\installed\apache-maven-3.5.0\repository\com\github\eirsle
tt\yarn\0.18.1\yarn-0.18.1.\yarn-v0.18.1.tar.gz'
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at 

答复: Is it possible to make use of SSD in a Ignite cluster?

[罗 辉]

Thank you ,I got it.


发件人: Michael Cherkasov 
发送时间: 2017年7月27日 16:54:52
收件人: user@ignite.apache.org
主题: Re: Is it possible to make use of SSD in a Ignite cluster?

Hi San Luo.

>1.Is there a way to use SSD when my cluster memory is running out to cache the 
>data?
Ignite 2.1 can do this for you:
https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store
it will be release this week.
>2.Is there a parameter that control intermediate result storage directory, 
>like the one "spark.local.dir" in apache spark?
Check PersistentStoreConfiguration there's a parameter for this where you can 
define dir to store data.
>3.Is there a parameter or a policy that Ignite can evict some data from memory 
>to SSD based on LRU when the memory is running out?
https://apacheignite.readme.io/v2.1/docs/evictions

Thanks,
Mikhail.

2017-07-27 11:12 GMT+03:00 罗 辉 >:

Hello guys:

   My cluster has some SSDs, and I want to make use of them in my Ignite 
applications.

1.Is there a way to use SSD when my cluster memory is running out to cache the 
data?

2.Is there a parameter that control intermediate result storage directory, like 
the one "spark.local.dir" in apache spark?

3.Is there a parameter or a policy that Ignite can evict some data from memory 
to SSD based on LRU when the memory is running out?


Any relative ideas is appreciated.

thanks
San.Luo

Re: Is it possible to make use of SSD in a Ignite cluster?

[Michael Cherkasov]

Hi San Luo.

>1.Is there a way to use SSD when my cluster memory is running out to cache
the data?
Ignite 2.1 can do this for you:
https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store
it will be release this week.
>2.Is there a parameter that control intermediate result storage directory,
like the one "spark.local.dir" in apache spark?
Check PersistentStoreConfiguration there's a parameter for this where you
can define dir to store data.
>3.Is there a parameter or a policy that Ignite can evict some data from
memory to SSD based on LRU when the memory is running out?
https://apacheignite.readme.io/v2.1/docs/evictions

Thanks,
Mikhail.

2017-07-27 11:12 GMT+03:00 罗 辉 :

> Hello guys:
>
>My cluster has some SSDs, and I want to make use of them in my
> Ignite applications.
>
> 1.Is there a way to use SSD when my cluster memory is running out to cache
> the data?
>
> 2.Is there a parameter that control intermediate result storage directory,
> like the one "spark.local.dir" in apache spark?
>
> 3.Is there a parameter or a policy that Ignite can evict some data from
> memory to SSD based on LRU when the memory is running out?
>
>
> Any relative ideas is appreciated.
>
> thanks
> San.Luo
>
>
>

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[afedotov]

Ankit thanks for the info.
I'll try to reproduce it on my side and get back to you.

Kind regards,
Alex.

On Thu, Jul 27, 2017 at 10:05 AM, Ankit Singhai [via Apache Ignite Users] <
ml+s70518n15716...@n6.nabble.com> wrote:

> Hi Alex,
> Yes it is reproducible every time.
> Linux Version:-
> Linux 3.10.0-514.26.1.el7.x86_64 #1 SMP Wed Jun 28 20:34:34 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
>
> Java Version:-
> java version "1.7.0_45"
> Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
> Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>
> I have already posted grid & cache config xmls. POJO is also available
> please use that.
>
> Regards,
> Ankit Singhai
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Caused-by-
> org-h2-jdbc-JdbcSQLException-General-error-java-lang-
> IllegalMonitorStateException-Attemptet-tp15684p15716.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
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15719.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite client not seeing cache created by server

[Maureen Lawless]

Brilliant, thanks a lot Mikhail.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-not-seeing-cache-created-by-server-tp15070p15718.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Is it possible to make use of SSD in a Ignite cluster?

[罗 辉]

Hello guys:

   My cluster has some SSDs, and I want to make use of them in my Ignite 
applications.

1.Is there a way to use SSD when my cluster memory is running out to cache the 
data?

2.Is there a parameter that control intermediate result storage directory, like 
the one "spark.local.dir" in apache spark?

3.Is there a parameter or a policy that Ignite can evict some data from memory 
to SSD based on LRU when the memory is running out?


Any relative ideas is appreciated.

thanks
San.Luo

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Hi Alex,
Yes it is reproducible every time.
Linux Version:-
Linux 3.10.0-514.26.1.el7.x86_64 #1 SMP Wed Jun 28 20:34:34 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux

Java Version:-
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

I have already posted grid & cache config xmls. POJO is also available
please use that.

Regards,
Ankit Singhai



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15716.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.