date:20160328

Re: Hibernate loadcache error?

2016-03-28 Thread Ravi Puri

Already tried everything.I didnt think u understnd it.

Do me a favour can u provide the working prjct related to hibernate
integrated with ignite at ravikumarpur...@gmail.com .

NOTE: PLEASE DO NOT SEND THE below LINK . PROVIDE ME THE WORKING THING as it
does not work with dynamic web project as java application


https://github.com/apache/ignite/tree/master/examples/src/main/java-lgpl/org/apache/ignite/examples/datagrid/store/hibernate




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

Ignite Cache and Compute Performance

2016-03-28 Thread abarbaro

Hello Ignite Community

I'm trying to evaluate the performance of Ignite Cache and Distributed
Computing. To do so, I have set up a very simple example that is a
simplification of the real-life examples for which we plan to use Ignite.
To my surprise, the results show that Ignite is a significantly slower than
I expected, and I would like to get some help with configuration and/or
tuning to improve performance.

Here's the example: We have a warehouse that has 10,000,000 Inventory
Items. Each Item has a product Id, a quantity, and a price. The sample
computation is to calculate the Total Value of the inventory, which is
SUM(i, Item[i].quantity * Item[i].price) (i.e. the sum of the value of each
item). The real-life is large-scale would have billions of entries per
cache and more complex calculations.

For the test, I have a single cache, with 10,000,000 entries, using pretty
much Ignite's standard configuration with a few tweaks. For only 10,000,000
items, I would have expected this calculation to perform in a matter of few
hundreds of milliseconds; however, the results for Ignite are almost 2 order
of magnitude slower are much slower (5,000 - 12,000 millis). I have also a
test that shows that when running this on the same JVM and using HashMap as
the cache, the computation takes 92 millis.

Also, the amount of memory overhead is very significant: the 10,000,000
require almost 4 GB of heap on the Ignite node (single-node cluster), versus
1GB of heap when running within a JVM and using HashMap.

Can you provide any guidance as to how to improve the performance of Ignite
Cache + Compute for this simple case? I'm attaching the code, and the
corresponding configuration and settings. I understand that there will be
some overhead when using a distributed data grid as opposed to a HashMap on
the same JVM, so I don't expect to get the same performance, but I would
like to get as close as possible.

Thanks so much in advance!

*JVM Settings*
JVM_OPTS=-Xms2048m -Xmx2048m -server -XX:+AggressiveOpts
-XX:MaxPermSize=256m
set JVM_OPTS=%JVM_OPTS% -DIGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE=1000
set JVM_OPTS=%JVM_OPTS% -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m
set JVM_OPTS=%JVM_OPTS% -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024
-XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60

*Attachements*

default-config.xml

Ignite_Performance_Analysis_Results.txt

inventory_cache_compute.jar

CacheComputeTest.java

InventoryItem.java

InventoryValueCompute.java

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

Re: Error in cache.loadCache(null,ENTRY_COUNT);

2016-03-28 Thread vkulichenko

This seems to be a duplicate of this thread:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-loadcache-error-td3534.html

Let's continue discussion there.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-in-cache-loadCache-null-ENTRY-COUNT-tp3701p3721.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Hibernate loadcache error?

2016-03-28 Thread vkulichenko

Ravi,

The trace clearly shows that loadCache() method is called, so I'm not sure I
understand what you just said. Please let me know if I'm wrong.

According to trace, there is some kind of a classpath issue not caused by
Ignite. Most likely you have two versions of Hibernate at the same time,
take a look at this SO thread for example:
http://stackoverflow.com/questions/8799121/java-lang-nosuchmethoderror-org-hibernate-sessionfactory-opensessionlorg-hibe

-Val



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

Re: Ignite Cache - High Memory Overhead caused by GridCircularBuffer$Item instances

2016-03-28 Thread abarbaro

Ok, I have done more research and I think I understand the effect of these
two parameters.  I think my original question is resolved.


Also, I have found that this parameter has a huge performance impact as
well:


...
 
...


When eagerTtl is true (default), Ignite will start a thread per cache to try
to delete entries as quick as possible.  I was running tests with 1,000
caches and the number of threads was overwhelming the nodes.

Thanks for all your help!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-High-Memory-Overhead-caused-by-GridCircularBuffer-Item-instances-tp3682p3719.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Host Arrays in C++ API

2016-03-28 Thread Vladimir Ozerov

Hi Arthi,

I think first of all we should understand how much time is spent on query
itself and how much time is spent on deserialization. Yoo already provided
XML configuration. Could you please also provide your CPP classes, your
code to query Ignite and SQL query itself?

Vladimir

On Mon, Mar 28, 2016 at 7:59 PM, arthi 
wrote:

> Hi Igor,
>
> The result set has 907171 rows. I am running a 4 node cluster. The query
> hits three caches with rows 30024916,20196,4892601. The results are columns
> from SHOP_ITEM_BITMAP_CACHE.
>
> Here is the config -
> 
>  value="SHOP_ITEM_BITMAP_CACHE" />
>  value="ATOMIC"/>
> 
>  value="ONHEAP_TIERED"/>
>  value="0"/>
>  value="false"/>
>  value="PARTITIONED" />
> 
> 
> class="org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction">
>  name="partitions" value="128"/>
> 
> 
> 
>  class="javax.cache.configuration.FactoryBuilder$SingletonFactory">
>   
> 
> class="com.nielsen.poc.aggregation.ignite.datagrid.store.ShopItemBitmapStore">
> 
>   
> 
> 
>  value="true" />
> 
> 
>  class="org.apache.ignite.cache.QueryEntity">
>  name="keyType" value="java.lang.Long" />
>  name="valueType"
> value="com.nielsen.poc.aggregation.ignite.datagrid.model.ShopItemBitmap" />
>  name="fields">
>
> 
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
> 
> 
>  name="indexes">
>
> 
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
> 
> 
> 
> 
> 
> 
>
>  class="org.apache.ignite.configuration.CacheConfiguration">
>  value="MARKET_POD_ACV_CACHE" />
>  value="ATOMIC"/>
>  value="0"/>
>  value="ONHEAP_TIERED"/>
>  value="0"/>
>
>  value="false"/>
>  value="REPLICATED" />
> 
>  class="javax.cache.configuration.FactoryBuilder$SingletonFactory">
>   
> 
> class="com.nielsen.poc.aggregation.ignite.datagrid.store.MarketPodAcvStore">
> 
>   
> 
> 
>  value="true" />
> 
> 
>  class="org.apache.ignite.cache.QueryEntity">
>  name="keyType" value="java.lang.Long" />
>  name="valueType"
> value="com.nielsen.poc.aggregation.ignite.datagrid.model.MarketPodAcv" />
>  name="fields">
>
> 
>
>   
>
>   
>
>   
>
>   
>
> 
> 
>

Re: Host Arrays in C++ API

2016-03-28 Thread arthi

Here is the query -

String sql = "SELECT sid_per_id, sid_mah_id, sid_itm_id, sid_prm_id,
sid_cha_code, sid_service, sid_itm_dist "
+ " FROM \"" + SHOP_ITEM_BITMAP_CACHE + 
"\".ShopItemBitmap as bitmap "
+ " JOIN \"" + PROD_HIER_CACHE + "\".ProdHier 
as prod   ON
prod.GHD_LEV_6 = bitmap.SID_ITM_ID  and prod.GHD_HIE_ID = 0  and
prod.ghd_lev_2_desc = 'WINE' " 
+ " JOIN \"" + MRKT_POD_ACV_CACHE + 
"\".MarketPodAcv as mktON
mkt.CHLD_MRKT_KEY = bitmap.SID_MAH_ID and mkt.MRKT_KEY = 4378038  AND  
mkt.prd_id = 712  "
+ " WHERE bitmap.SID_PER_ID = 712   ";  



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

Re: Host Arrays in C++ API

2016-03-28 Thread arthi

Thanks Igor.

I use SQL queries, and the result sets could grow to million rows. 
we tried GetAll too, but, its also runs for 25 secs or more.

Is there a better way to derive the results? Please advice.

Thanks,
Arthi



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

ignite not support expression: EXISTS?

2016-03-28 Thread minisoft_rm

dear experts, I knew ignite supports ANSI 99 SQL. but seemed not support
expression: EXISTS... really?
Our company sw uses this keyword lots of times.

My testing sql is:"
select * from products as a where  exists(select * from productslp as b
where a.pk=b.itempk and a.pcode='100124');
"
and ignite throw exception like below:

Caused by: class org.apache.ignite.IgniteException: Unsupported expression:
EXISTS(
SELECT
B._KEY,
B._VAL,
B.ITEMPK,
B.ITEMTYPEPK,
B.LANGPK,
B.PNAME,
B.PDESCRIPTION,
B.PMANUFACTURERTYPEDESCRIPTION,
B.PSEGMENT,
B.PARTICLESTATUS,
B.PSUMMARY,
B.PSTYLE,
B.PSIZE,
B.PCOLOR
FROM "b2c_accCache".PRODUCTSLP B
/* "b2c_accCache"."PRIMARY": ITEMPK = A.PK */
WHERE (A.PCODE = '100124')
AND (A.PK = B.ITEMPK)) [type=ConditionExists]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:806)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:647)
... 1 more
Caused by: class org.apache.ignite.IgniteCheckedException: Unsupported
expression: EXISTS(
SELECT
B._KEY,
B._VAL,
B.ITEMPK,
B.ITEMTYPEPK,
B.LANGPK,
B.PNAME,
B.PDESCRIPTION,
B.PMANUFACTURERTYPEDESCRIPTION,
B.PSEGMENT,
B.PARTICLESTATUS,
B.PSUMMARY,
B.PSTYLE,
B.PSIZE,
B.PCOLOR
FROM "b2c_accCache".PRODUCTSLP B
/* "b2c_accCache"."PRIMARY": ITEMPK = A.PK */
WHERE (A.PCODE = '100124')
AND (A.PK = B.ITEMPK)) [type=ConditionExists]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1782)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:799)
... 2 more
Caused by: class org.apache.ignite.IgniteException: Unsupported expression:
EXISTS(
SELECT
B._KEY,
B._VAL,
B.ITEMPK,
B.ITEMTYPEPK,
B.LANGPK,
B.PNAME,
B.PDESCRIPTION,
B.PMANUFACTURERTYPEDESCRIPTION,
B.PSEGMENT,
B.PARTICLESTATUS,
B.PSUMMARY,
B.PSTYLE,
B.PSIZE,
B.PCOLOR
FROM "b2c_accCache".PRODUCTSLP B
/* "b2c_accCache"."PRIMARY": ITEMPK = A.PK */
WHERE (A.PCODE = '100124')
AND (A.PK = B.ITEMPK)) [type=ConditionExists]
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseExpression0(GridSqlQueryParser.java:648)
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseExpression(GridSqlQueryParser.java:421)
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parse(GridSqlQueryParser.java:301)
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parse(GridSqlQueryParser.java:372)
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parse(GridSqlQueryParser.java:244)
at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:153)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1055)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:801)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:799)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1764)
... 3 more



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

Re: Error Starting Node from .net

2016-03-28 Thread Murthy Kakarlamudi

That resolved the error. Thanks much.

On Mon, Mar 28, 2016 at 4:08 AM, Vladimir Ozerov 
wrote:

> Hi,
>
> In Ignite 1.5 binary protocol for .NET doesn't support one optimization
> called "compact footers" which is supported by Java. This optimization will
> be added in Ignite 1.6. For now please add the following property to
> configuration of our Java node:
>
> 
> 
> 
> 
> 
> 
> 
>
> Vladimir.
>
> On Mon, Mar 28, 2016 at 3:21 AM, Murthy Kakarlamudi 
> wrote:
>
>> Hi,
>>In my application, I am starting the node from command line. One the
>> client nodes uses java to load the data and the other client node in .net
>> uses sql to query the cache. I am getting the below error running .net
>> client node:
>>
>> GC server mode is not enabled, this could lead to less than optimal
>> performance on multi-core machines (to enable see
>> http://msdn.microsoft.com/en-us/library/ms229357(v=vs.110).aspx).
>> Mar 27, 2016 8:03:56 PM
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader
>> loadBeanDefinitions
>> INFO: Loading XML bean definitions from URL
>> [file:/C:/Data/Professional/java/ignite/software/apache-ignite-fabric-1.5.0.final-bin/platforms/dotnet/examples/config/ignite.xml]
>> Mar 27, 2016 8:03:57 PM
>> org.springframework.context.support.AbstractApplicationContext
>> prepareRefresh
>> INFO: Refreshing
>> org.springframework.context.support.GenericApplicationContext@7907ec20:
>> startup date [Sun Mar 27 20:03:57 EDT 2016]; root of context hierarchy
>> [20:03:57]__  
>> [20:03:57]   /  _/ ___/ |/ /  _/_  __/ __/
>> [20:03:57]  _/ // (7 7// /  / / / _/
>> [20:03:57] /___/\___/_/|_/___/ /_/ /___/
>> [20:03:57]
>> [20:03:57] ver. 1.5.0-final#20151229-sha1:f1f8cda2
>> [20:03:57] 2015 Copyright(C) Apache Software Foundation
>> [20:03:57]
>> [20:03:57] Ignite documentation: http://ignite.apache.org
>> [20:03:57]
>> [20:03:57] Quiet mode.
>> [20:03:57]   ^-- Logging to file
>> 'C:\Data\Professional\java\ignite\software\apache-ignite-fabric-1.5.0.final-bin\work\log\ignite-1966dd40.0.log'
>> [20:03:57]   ^-- To see **FULL** console log here add
>> -DIGNITE_QUIET=false or "-v" to ignite.{sh|bat}
>> [20:03:57]
>> [20:03:57] OS: Windows 10 10.0 amd64
>> [20:03:57] VM information: Java(TM) SE Runtime Environment 1.8.0_65-b17
>> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.65-b01
>> [20:03:59] Configured plugins:
>> [20:03:59]   ^-- None
>> [20:03:59]
>> [20:04:00] Security status [authentication=off, tls/ssl=off]
>> [20:04:04,710][SEVERE][main][IgniteKernal] Failed to start manager:
>> GridManagerAdapter [enabled=true,
>> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
>> class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
>> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
>> reconCnt=10, maxAckTimeout=60, forceSrvMode=false,
>> clientReconnectDisabled=false]
>> at
>> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
>> at
>> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
>> at
>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
>> at
>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
>> at org.apache.ignite.Ignition.start(Ignition.java:322)
>> at
>> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:36)
>> at
>> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:72)
>> Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
>> binary marshaller "compactFooter" property differs from the same property
>> on remote node (make sure all nodes in topology have the same value of
>> "compactFooter" property) [locMarshallerCompactFooter=false,
>> rmtMarshallerCompactFooter=true,
>> locNodeAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
>> /192.168.0.7, /2001:0:5ef5:79fd:2c57:a4e:bb9b:11d9], locPort=0,
>> rmtNodeAddr=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
>> /192.168.0.7, /2001:0:5ef5:79fd:2c57:a4e:bb9b:11d9],
>> locNodeId=1966dd40-4c81-4f5c-a97c-f7a9dd0a9c15,
>> rmtNodeId=e89a03d0-4984-4c7e-9d21-c2225a05886e]
>> at
>> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1647)
>> at
>>

Re: Ignite terminology

2016-03-28 Thread alexGalushka

Vladimir,

Thank you so much for your answer, things are starting making a bit more
sense now, but I still confuse about the the
Ignition.ignite("Grid_Instance_Name") javadoc:

"Note that Java VM can run multiple grid instances and every *grid instance
(and its node)* can belong to a different grid."

You said that "grid instance" == "ignite node", should the javadoc be
corrected to "grid instance (aka node)"?

Following your terminology, the "gridName" in the IgniteConfiguration it's
indeed "gridInstanceName" (or to be more accurate, "nodeName"), the comments
in the IgniteConfiguration say:

/** Optional grid name. */
private String gridName;

Should it be 

/** Optional node name. */
private String gridInstanceName; (or nodeName)  ?


I'm also confused on what Ignition.ignite("MY_GRID_*INSTANCE*_NAME")
returns, it return the Ignite instance, which is the "Main entry-point for
all Ignite APIs", in order to get the particular node, you have to address
it by UUID:

Ignition.ignite("APPLIANCE").cluster().node("some_UUID") ? 

Can you please clarify?

I also have follow up questions on the cluster naming, but I'll hold on for
those in order to avoid confusion and.

--Alexander





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

Re: SqlQuery Error

2016-03-28 Thread 16616...@qq.com

hi yakov,

Thank you very much for you reply.
Now I can execute sql query and fields query correctly.

But I still can not execute sql query by rest api. For example:

http://localhost:8080/ignite?cmd=qryfldexe=TestTable1Cache=select+id+from++testtable1

no data response.

http://localhost:8080/ignite?cmd=qryexe=TestTable1=10=TestTable1Cache=2=id%3d%3f

{"error":"class org.apache.ignite.IgniteException: Failed to find SQL table
for type: TestTable1","response":null,"sessionToken":"","successStatus":1}

Any advice?  Thanks.

Tony






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

Host Arrays in C++ API

2016-03-28 Thread arthi

Hi Ignite Gurus,

I am currently using ignite to cache data on a cluster, and I have a C++
client that reads the data from the cache using SQL. The API allows
execution of the queries in milli secs, but, there is a delay when we loop
through the results (we are currently looping one by one using getNext()). 

Is there a way I can use something similar to Host Arrays
https://docs.oracle.com/cd/B10501_01/appdev.920/a97269/pc_08arr.htm#468
basically, I want to copy the result set into continous memory in one shot
and use that array for further processing.

Pls help.

Thanks,
Arthi





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

Re: HDFS as persistent store for data grid

2016-03-28 Thread Denis Magda

I would also add that despite of the fact that Ignite doesn't provide 
HDFS based persistent store implementation/example out of the box, it 
doesn't mean that you can't use HDFS as a persistent store.

Absolutely you can.

What is your use case?

--
Denis

On 3/28/2016 11:11 AM, Vladimir Ozerov wrote:

Hi Kushai,

Ignite does not have integration with HDFS in terms of cache 
persistent store. Instead, Ignite comes with IGFS - in-memory file 
system - which is able to cache data from HDFS and thus speed-up 
Hadoop jobs. See this document for more info: 
https://apacheignite-fs.readme.io/docs/in-memory-file-system


Vladimir.

On Mon, Mar 28, 2016 at 8:23 AM, Kushal Kumaran > wrote:


Hi,

The page at https://ignite.apache.org/features/datagrid.html mentions
that "Ignite can automatically integrate with external databases -
RDBMS, NoSQL, and HDFS."  But I'm unable to find any documentation on
how do do this with HDFS.  I looked through the linked
documentation for
Persistent Store at
https://apacheignite.readme.io/docs/persistent-store, but it only
mentions JDBC connectivity.  Looking through the source, I was
unable to
find a non-JDBC implementation of CacheStore.

Is there a way to use HDFS as the persistent store for datagrid?

--
regards,
kushal

Re: SqlQuery Error

2016-03-28 Thread Yakov Zhdanov

There is an issue in your query entity configuration.

After I changed it (see below) sql query and fields query started to work.

fields.put("id", "java.lang.String");
fields.put("attribute1", "java.lang.String");
fields.put("attribute2", "java.lang.String");
fields.put("attribute3", "java.lang.String");

Query - SqlQuery sql = new SqlQuery(Testtable1.class,
"id=?").setArgs("9");

Can you please check if it works for you?

--Yakov

2016-03-24 12:31 GMT+03:00 16616...@qq.com <16616...@qq.com>:

> You can download my src file here. 
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/SqlQuery-Error-tp3658p3662.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Error in cache.loadCache(null,ENTRY_COUNT);

2016-03-28 Thread Ravi Puri

Error at cache.loadCache(null,100_000)


Caused by: class org.apache.ignite.compute.ComputeUserUndeclaredException:
Failed to execute job due to unexpected runtime exception
[jobId=a2275acb351-93f69876-63cd-4130-b8b6-b82956f489f1,
ses=GridJobSessionImpl [ses=GridTaskSessionImpl
[taskName=org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure,
dep=GridDeployment [ts=1459158883086, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@35489ea3,
clsLdrId=82275acb351-93f69876-63cd-4130-b8b6-b82956f489f1, userVer=0,
loc=true,
sampleClsName=org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure,
pendingUndeploy=false, undeployed=false, usage=2],
taskClsName=org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure,
sesId=72275acb351-93f69876-63cd-4130-b8b6-b82956f489f1,
startTime=1459158883076, endTime=9223372036854775807,
taskNodeId=93f69876-63cd-4130-b8b6-b82956f489f1,
clsLdr=sun.misc.Launcher$AppClassLoader@35489ea3, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false,
subjId=93f69876-63cd-4130-b8b6-b82956f489f1, mapFut=IgniteFuture
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1459158883097,
endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
jobId=a2275acb351-93f69876-63cd-4130-b8b6-b82956f489f1]]
at
org.apache.ignite.internal.processors.job.GridJobWorker.handleThrowable(GridJobWorker.java:607)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:551)
... 5 more
Caused by: java.lang.NoSuchMethodError:
org.hibernate.SessionFactory.openSession()Lorg/hibernate/Session;
at
org.apache.ignite.cache.store.hibernate.CacheHibernateStoreSessionListener.onSessionStart(CacheHibernateStoreSessionListener.java:178)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionInit0(GridCacheStoreManagerAdapter.java:818)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:479)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:515)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localLoadCache(IgniteCacheProxy.java:387)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5716)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5663)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
... 5 more
[15:24:43,122][ERROR][ignite-#7%pub-null%][GridJobWorker] Runtime error
caught during grid runnable execution: GridJobWorker
[createTime=1459158883097, startTime=1459158883107,
finishTime=1459158883107, taskNode=TcpDiscoveryNode
[id=93f69876-63cd-4130-b8b6-b82956f489f1, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1,
172.17.122.216], sockAddrs=[01HW611909.India.TCS.com/172.17.122.216:47500,
/0:0:0:0:0:0:0:1:47500, /127.0.0.1:47500, /172.17.122.216:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1459158872853,
loc=true, ver=1.5.0#20151202-sha1:062d440c, isClient=false], internal=false,
marsh=o.a.i.marshaller.optimized.OptimizedMarshaller@1680cf6a,
ses=GridJobSessionImpl [ses=GridTaskSessionImpl
[taskName=o.a.i.i.processors.cache.GridCacheAdapter$LoadCacheClosure,
dep=GridDeployment [ts=1459158883086, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@35489ea3,
clsLdrId=82275acb351-93f69876-63cd-4130-b8b6-b82956f489f1, userVer=0,
loc=true,
sampleClsName=o.a.i.i.processors.cache.GridCacheAdapter$LoadCacheClosure,
pendingUndeploy=false, undeployed=false, usage=0],
taskClsName=o.a.i.i.processors.cache.GridCacheAdapter$LoadCacheClosure,
sesId=72275acb351-93f69876-63cd-4130-b8b6-b82956f489f1,
startTime=1459158883076, endTime=9223372036854775807,
taskNodeId=93f69876-63cd-4130-b8b6-b82956f489f1,
clsLdr=sun.misc.Launcher$AppClassLoader@35489ea3, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false,
subjId=93f69876-63cd-4130-b8b6-b82956f489f1, mapFut=IgniteFuture
[orig=GridFutureAdapter [resFlag=0, res=null, startTime=1459158883097,
endTime=0, ignoreInterrupts=false, lsnr=null, state=INIT]]],
jobId=a2275acb351-93f69876-63cd-4130-b8b6-b82956f489f1],
jobCtx=GridJobContextImpl
[jobId=a2275acb351-93f69876-63cd-4130-b8b6-b82956f489f1, timeoutObj=null,
attrs={}], dep=GridDeployment [ts=1459158883086, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@35489ea3,
clsLdrId=82275acb351-93f69876-63cd-4130-b8b6-b82956f489f1, userVer=0,

Re: HDFS as persistent store for data grid

2016-03-28 Thread Vladimir Ozerov

Hi Kushai,

Ignite does not have integration with HDFS in terms of cache persistent
store. Instead, Ignite comes with IGFS - in-memory file system - which is
able to cache data from HDFS and thus speed-up Hadoop jobs. See this
document for more info:
https://apacheignite-fs.readme.io/docs/in-memory-file-system

Vladimir.

On Mon, Mar 28, 2016 at 8:23 AM, Kushal Kumaran 
wrote:

> Hi,
>
> The page at https://ignite.apache.org/features/datagrid.html mentions
> that "Ignite can automatically integrate with external databases -
> RDBMS, NoSQL, and HDFS."  But I'm unable to find any documentation on
> how do do this with HDFS.  I looked through the linked documentation for
> Persistent Store at
> https://apacheignite.readme.io/docs/persistent-store, but it only
> mentions JDBC connectivity.  Looking through the source, I was unable to
> find a non-JDBC implementation of CacheStore.
>
> Is there a way to use HDFS as the persistent store for datagrid?
>
> --
> regards,
> kushal
>

Re: Error Starting Node from .net

2016-03-28 Thread Vladimir Ozerov

Hi,

In Ignite 1.5 binary protocol for .NET doesn't support one optimization
called "compact footers" which is supported by Java. This optimization will
be added in Ignite 1.6. For now please add the following property to
configuration of our Java node:









Vladimir.

On Mon, Mar 28, 2016 at 3:21 AM, Murthy Kakarlamudi 
wrote:

> Hi,
>In my application, I am starting the node from command line. One the
> client nodes uses java to load the data and the other client node in .net
> uses sql to query the cache. I am getting the below error running .net
> client node:
>
> GC server mode is not enabled, this could lead to less than optimal
> performance on multi-core machines (to enable see
> http://msdn.microsoft.com/en-us/library/ms229357(v=vs.110).aspx).
> Mar 27, 2016 8:03:56 PM
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader
> loadBeanDefinitions
> INFO: Loading XML bean definitions from URL
> [file:/C:/Data/Professional/java/ignite/software/apache-ignite-fabric-1.5.0.final-bin/platforms/dotnet/examples/config/ignite.xml]
> Mar 27, 2016 8:03:57 PM
> org.springframework.context.support.AbstractApplicationContext
> prepareRefresh
> INFO: Refreshing
> org.springframework.context.support.GenericApplicationContext@7907ec20:
> startup date [Sun Mar 27 20:03:57 EDT 2016]; root of context hierarchy
> [20:03:57]__  
> [20:03:57]   /  _/ ___/ |/ /  _/_  __/ __/
> [20:03:57]  _/ // (7 7// /  / / / _/
> [20:03:57] /___/\___/_/|_/___/ /_/ /___/
> [20:03:57]
> [20:03:57] ver. 1.5.0-final#20151229-sha1:f1f8cda2
> [20:03:57] 2015 Copyright(C) Apache Software Foundation
> [20:03:57]
> [20:03:57] Ignite documentation: http://ignite.apache.org
> [20:03:57]
> [20:03:57] Quiet mode.
> [20:03:57]   ^-- Logging to file
> 'C:\Data\Professional\java\ignite\software\apache-ignite-fabric-1.5.0.final-bin\work\log\ignite-1966dd40.0.log'
> [20:03:57]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [20:03:57]
> [20:03:57] OS: Windows 10 10.0 amd64
> [20:03:57] VM information: Java(TM) SE Runtime Environment 1.8.0_65-b17
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.65-b01
> [20:03:59] Configured plugins:
> [20:03:59]   ^-- None
> [20:03:59]
> [20:04:00] Security status [authentication=off, tls/ssl=off]
> [20:04:04,710][SEVERE][main][IgniteKernal] Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> reconCnt=10, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:36)
> at
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:72)
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
> binary marshaller "compactFooter" property differs from the same property
> on remote node (make sure all nodes in topology have the same value of
> "compactFooter" property) [locMarshallerCompactFooter=false,
> rmtMarshallerCompactFooter=true,
> locNodeAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
> /192.168.0.7, /2001:0:5ef5:79fd:2c57:a4e:bb9b:11d9], locPort=0,
> rmtNodeAddr=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1, /
> 192.168.0.7, /2001:0:5ef5:79fd:2c57:a4e:bb9b:11d9],
> locNodeId=1966dd40-4c81-4f5c-a97c-f7a9dd0a9c15,
> rmtNodeId=e89a03d0-4984-4c7e-9d21-c2225a05886e]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1647)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1460)
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [20:04:04,725][SEVERE][main][IgniteKernal] Got exception while starting
> (will

Re: Ignite terminology

2016-03-28 Thread Vladimir Ozerov

Hi Alexander,

Basically, "grid" == "Ignite cluster" and "grid instance" == "ignite node".
"Grid" terms came from old GridGain days. I suggest you to operate on terms
"node" and "cluster".

Ignition.ignite(String) returns a node with a given name started in current
JVM. If you re-start the node with the same name, instance returned after
restart will differ from instance returned before restart:

Ignition.start([config with gridName="A"]);
Ignite before = Ignition.ignite("A");

Ignition.stop("A", true);

Ignition.start([config with gridName="A"]);
Ignite after = Ignition.ignite("A");

assert before == after; // Will fail.

Vladimir.

On Sat, Mar 26, 2016 at 12:04 AM, alexGalushka 
wrote:

> Hello Ignite community!
>
> I read through the Ignite docs a few times and was playing with Ignite for
> a
> few weeks.
> But I still can't figure out the Ignite terminology...
>
> What are definitions and relations of the following: grid, grid instance,
> ignite cluster (cluster), ignite node (node)?
> I feel like in the Ignite context grid and cluster are interchangeably
> terms, but still not 100% sure about it.
>
> How to make the nodes belong to the same cluster (/grid, if the term is
> interchangeable)? Setting the same gridName seems to do it:
>
> Ignition.ignite("MY_GRID_NAME").cluster().nodes()...
>
> I see 2 nodes in the collection and with the correct node IDs.
>
> But I'm confused by the .ignite(...) java doc, which says: "Note that
> caller
> of this method should not assume that it will return the same instance
> every
> time. Grid name defines what grid a particular grid instance (and
> correspondingly its node) belongs to"
>
> --Alexander.
>
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-terminology-tp3687.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Hibernate loadcache error?

Ignite Cache and Compute Performance

Re: Error in cache.loadCache(null,ENTRY_COUNT);

Re: Hibernate loadcache error?

Re: Ignite Cache - High Memory Overhead caused by GridCircularBuffer$Item instances

Re: Host Arrays in C++ API

Re: Host Arrays in C++ API

Re: Host Arrays in C++ API

ignite not support expression: EXISTS?

Re: Error Starting Node from .net

Re: Ignite terminology

Re: SqlQuery Error

Host Arrays in C++ API

Re: HDFS as persistent store for data grid

Re: SqlQuery Error

Error in cache.loadCache(null,ENTRY_COUNT);

Re: HDFS as persistent store for data grid

Re: Error Starting Node from .net

Re: Ignite terminology

19 matches

Site Navigation

Mail list logo

Footer information