Re: Query Monitoring

2019-04-10 Thread Skollur
How do i see this view?



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


Query Monitoring

2019-04-10 Thread Skollur
I am using Apache ignite 2.7.0 and agent - ignite-web-agent-2.7.3. I have
also configured cache with ccfg.setStatisticsEnabled(true) and
ccfg.setQueryDetailMetricsSize(10);
But I seeing error in ignite web console as - "No statistic information
about executed query
Query monitoring is not available for the current cluster.
This may be because either query monitoring is disabled or no query has been
executed yet.
To enable query monitoring, configure
CacheConfiguration.queryDetailMetricsSize property."  Is there anything else
to be configured?



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


Ignite Performance

2019-04-05 Thread Skollur
I have 250,000 records for each cache store and when I tried to join they are
pretty slow. 
Is annotation -> @affinityKey, @SqlQueryField works in java version? I am
using JDK1.8 version AND NOT Spring version. 

Can someone help how to use @affinitykey in group for below example in
'PARTIONED' without creating too much index. I am using REPLICATE mode now.
The example in ignite website is not clear with just two tables. What are
various recommendation to get good response from query execution.


Cache1
---

package com.test.config
public class Account implements Serializable {
/** */
private static final long serialVersionUID = 0L;

/** Value for dwId. */
private long dwId;

/** Value for accountNumber. */
private Long accountNumber;

/** Value for accountType. */
private String accountType;
}

---
package com.test.config
public class AccountCache {

public static CacheConfiguration createAccountCache() throws Exception {
CacheConfiguration ccfg = new CacheConfiguration();
ccfg.setName(cacheName);
ccfg.setCacheMode(CacheMode.REPLICATED);
cacheStoreFactory.setTypes(jdbcTypeAccount("Account");
ccfg.setCacheStoreFactory(cacheStoreFactory);

ArrayList qryEntities = new ArrayList<>();
QueryEntity qryEntity = new QueryEntity();
qryEntity.setKeyType("java.lang.Long");
qryEntity.setValueType("com.test.Account");
qryEntity.setTableName("Account");
qryEntity.setKeyFieldName("dwId");
HashSet keyFields = new HashSet<>();
keyFields.add("dwId");
qryEntity.setKeyFields(keyFields);
LinkedHashMap fields = new LinkedHashMap<>();
fields.put("dwId", "java.lang.Long");
fields.put("accountNumber", "java.lang.Long");
fields.put("accountType", "java.lang.String");
}


 **/
private static JdbcType jdbcTypeAccount(String cacheName) {
JdbcType type = new JdbcType();

type.setCacheName(cacheName);
type.setKeyType(Long.class);
type.setValueType("com.test.Account");
type.setDatabaseSchema("dbo");
type.setDatabaseTable("Account");
type.setKeyFields(new JdbcTypeField(Types.BIGINT, "DW_Id",
long.class, "dwId"));
type.setValueFields(
new JdbcTypeField(Types.BIGINT, "Account_Number",
Long.class, "accountNumber"),
new JdbcTypeField(Types.VARCHAR, "Account_Type",
String.class, "accountType"),
);

return type;
}
}

Cache 2

package com.test.config
public class AccountAddress implements Serializable {
/** */
private static final long serialVersionUID = 0L;

/** Value for dwId. */
private long dwId;

/** Value for accountNumber. */
private Long accountNumber;

/** Value for accountType. */
private String accountType;

/** Value for addressId. */
private Long addressId;
}

-
package com.test.config
public class AccountAddressCache {

public static CacheConfiguration createAccountAddressCache() throws
Exception {
CacheConfiguration ccfg = new CacheConfiguration();
ccfg.setName(cacheName);
ccfg.setCacheMode(CacheMode.REPLICATED);
cacheStoreFactory.setTypes(jdbcTypeAccountAddress("AccountAddress");
ccfg.setCacheStoreFactory(cacheStoreFactory);

ArrayList qryEntities = new ArrayList<>();

QueryEntity qryEntity = new QueryEntity();
qryEntity.setKeyType("java.lang.Long");
qryEntity.setValueType("com.test.AccountAddress");
qryEntity.setTableName("Account_Address");
qryEntity.setKeyFieldName("dwId");
HashSet keyFields = new HashSet<>();
keyFields.add("dwId");
qryEntity.setKeyFields(keyFields);

LinkedHashMap fields = new LinkedHashMap<>();

fields.put("dwId", "java.lang.Long");
fields.put("accountNumber", "java.lang.Long");
fields.put("accountType", "java.lang.String");

qryEntity.setFields(fields);
ArrayList indexes = new ArrayList<>();
QueryIndex index = new QueryIndex();
index.setName("NonClustered_Index_AC_ID");
index.setIndexType(QueryIndexType.SORTED);
LinkedHashMap indFlds = new LinkedHashMap<>();
indFlds.put("dwId", true);
indFlds.put("accountNumber", true);
indexes.add(index);
qryEntity.setIndexes(indexes);
   
qryEntities.add(qryEntity);
   //ccfg.setIndexedTypes(Long.class,Address.class);
ccfg.setQueryEntities(qryEntities);

return ccfg;
}

/**
 * Create JDBC type for "jdbcTypeAccountAddress".
 * 
 * @param cacheName Cache name.
 * @return Configured JDBC type.
 **/
private static JdbcType jdbcTypeAccountAddress(String cacheName) {
JdbcType type = new JdbcType();

type.setCacheName(cacheName);
type.setKeyType(Long.class);
type.setValueType("com

Cache Join

2019-03-27 Thread Skollur
Hello

I am using apache ignite 2.7 version and trying to join three tables and My
query looks as below. All tables are configured as PARTIONED and also set
"distributedjoin=true" 
==
SELECT 
CAS.Group_Customer_ID as groupCustomerId,
CAS.Account_Number as accountNumber,
'Custody Account' as productTitle,
CAS.Investment_Model as investmentModel,
sum(CAS.Market_Value) AS marketValue,
CSS.Category_Sequence as sequenceNumber,
sum(ASM.Prev_Month_Bal)  as preMonthBal,
sum(ASM.Prev_Year_Bal) as preYearBal  
 FROM
"VwCustodyAccountPositionCpsCache".VW_CUSTODY_ACCOUNT_POSITION_CPS CAS 
INNER JOIN "IdbCpsSequenceCache".IDB_CPS_SEQUENCE CSS ON 
CAS.Account_Type = CSS.Account_Type  
AND CAS.As_Of_Date BETWEEN '2018-12-31' AND '2018-12-31' 
AND CAS.Group_Customer_ID = 61 
 INNER JOIN "InvestmentSummaryMonthlyCache".ASSET_SUMMARY_MONTHLY ASM ON
CAS.Group_Customer_ID = ASM.Group_Customer_ID  
AND CAS.Account_Number = ASM.Account_Number   
AND CAS.As_of_Date = ASM.Effective_Date 
AND CAS.Account_Type = ASM.Account_Type  
AND CAS.Product = ASM.Product 
AND CAS.Asset_Class_Allocation = ASM.Asset_Class
group by  
CAS.Group_Customer_ID,
CAS.Account_Number,
CAS.Investment_Model,
CSS.Category_Sequence
=
I have added index for each fields which are used in each cache table as
below. Example in InvestmentSummaryMonthlyCache:-

   ArrayList indexes = new ArrayList<>();
QueryIndex index = new QueryIndex();
index.setName("NonClustered_Index_Summary_Monthly");
index.setIndexType(QueryIndexType.SORTED);
LinkedHashMap indFlds = new LinkedHashMap<>();
indFlds.put("dwId", true);
indFlds.put("groupCustomerId", true);
indFlds.put("accountNumber", true);
indFlds.put("accountType", true);
indFlds.put("product", true);
indFlds.put("productType", true);
indFlds.put("subProduct", true);
indFlds.put("assetClass", true);
indFlds.put("effectiveDate", true);
index.setFields(indFlds);
indexes.add(index);
qryEntity.setIndexes(indexes);
qryEntities.add(qryEntity);
=
When I tried to execute query(I have all fields defined in index as above),
getting an error -> SQL Error [5]: javax.cache.CacheException: Failed to
prepare distributed join query: join condition does not use index
[joinedCache=InvestmentSummaryMonthlyCache, What am I missing here?


plan=SELECT
CAS__Z0.GROUP_CUSTOMER_ID AS __C0_0,
CAS__Z0.ACCOUNT_NUMBER AS __C0_1,
'Custody Account' AS __C0_2,
CAS__Z0.INVESTMENT_MODEL AS __C0_3,
SUM(CAS__Z0.MARKET_VALUE) AS __C0_4,
CSS__Z1.CATEGORY_SEQUENCE AS __C0_5,
SUM(ASM__Z2.PREV_MONTH_BAL) AS __C0_6,
SUM(ASM__Z2.PREV_YEAR_BAL) AS __C0_7
FROM "VwCustodyAccountPositionCpsCache".VW_CUSTODY_ACCOUNT_POSITION_CPS
CAS__Z0
/*
"VwCustodyAccountPositionCpsCache".VW_CUSTODY_ACCOUNT_POSITION_CPS.__SCAN_
*/
/* WHERE (CAS__Z0.AS_OF_DATE <= DATE '2018-12-31')
AND ((CAS__Z0.GROUP_CUSTOMER_ID = 80061)
AND (CAS__Z0.AS_OF_DATE >= DATE '2018-12-31'))
*/
INNER JOIN "InvestmentSummaryMonthlyCache".ASSET_SUMMARY_MONTHLY ASM__Z2
/* batched:broadcast
"InvestmentSummaryMonthlyCache".ASSET_SUMMARY_MONTHLY.__SCAN_ */
ON 1=1
/* WHERE (CAS__Z0.ACCOUNT_NUMBER = ASM__Z2.ACCOUNT_NUMBER)
AND ((CAS__Z0.GROUP_CUSTOMER_ID = ASM__Z2.GROUP_CUSTOMER_ID)
AND ((CAS__Z0.AS_OF_DATE = ASM__Z2.EFFECTIVE_DATE)
AND ((CAS__Z0.ACCOUNT_TYPE = ASM__Z2.ACCOUNT_TYPE)
AND ((CAS__Z0.ASSET_CLASS_ALLOCATION = ASM__Z2.ASSET_CLASS)
AND (CAS__Z0.PRODUCT = ASM__Z2.PRODUCT)
*/
INNER JOIN "IdbCpsSequenceCache".IDB_CPS_SEQUENCE CSS__Z1
/* batched:broadcast "IdbCpsSequenceCache".NONCLUSTERED_INDEX_LC:
ACCOUNT_TYPE = CAS__Z0.ACCOUNT_TYPE */
ON 1=1
WHERE ((CAS__Z0.GROUP_CUSTOMER_ID = 80061)
AND ((CAS__Z0.ACCOUNT_TYPE = CSS__Z1.ACCOUNT_TYPE)
AND ((CAS__Z0.AS_OF_DATE >= DATE '2018-12-31')
AND (CAS__Z0.AS_OF_DATE <= DATE '2018-12-31'
AND ((CAS__Z0.ASSET_CLASS_ALLOCATION = ASM__Z2.ASSET_CLASS)
AND ((CAS__Z0.PRODUCT = ASM__Z2.PRODUCT)
AND ((CAS__Z0.ACCOUNT_TYPE = ASM__Z2.ACCOUNT_TYPE)
AND ((CAS__Z0.AS_OF_DATE = ASM__Z2.EFFECTIVE_DATE)
AND ((CAS__Z0.GROUP_CUSTOMER_ID = ASM__Z2.GROUP_CUSTOMER_ID)
AND (CAS__Z0.ACCOUNT_NUMBER = ASM__Z2.ACCOUNT_NUMBER))
GROUP BY CAS__Z0.GROUP_CUSTOMER_ID, CAS__Z0.ACCOUNT_NUMBER,
CAS__Z0.INVESTMENT_MODEL, CSS__Z1.CATEGORY_SEQUENCE]
  SQL Error [5]: javax.cache.CacheException: Failed to prepare
distributed join query: join condition does not use index
[joinedCache=InvestmentSummaryMonthlyCache, plan=SELECT
CAS__Z0.GROUP_CUSTOMER_ID AS __C0_0,
CAS__Z0.ACCOUNT_NUMBER AS __C0_1,
   

Ignite Remote Node

2018-12-27 Thread Skollur
Hello

I have upgraded my code from Apache ignite version 2.6 to 2.7. I am running
two server nodes in two different machines. However after upgrade, noticed
that these two server nodes joined. Log shows as servers=2, state=ACTIVE.

Based on previous suggestion, I have commented out TCPDiscoverSPI and still
see server nodes are joined in 2.7 version. How to make sure server nodes
runs in one machine and not joining with remote (stand alone)?

IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName("testdb");

/*TcpDiscoverySpi discovery = new TcpDiscoverySpi();
   
discovery.setLocalAddress(IPClusterConfigInitialize.IpClusterConfig().getProperty("ipClusterConfig"));
discovery.setLocalPort(new
Integer(IPClusterConfigInitialize.IpClusterConfig().getProperty("port")));
cfg.setDiscoverySpi(discovery);*/

cfg.setPeerClassLoadingEnabled(false);





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


web console

2018-12-18 Thread Skollur
I am trying to ocnnect web console and downloaded ignite-web-agent-2.7.1. It
doesnt seems to support java 1.8 and getting an error "jdk1.8.0_171 was
unexpected at this time." What is the java version supported for
ignite-web-agent-2.7.1?




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


Apache Ignite Join

2018-12-12 Thread Skollur
I have single node with REPLICATE mode. Record counts in database and ignite
is matching when query the number of records in each table. However when it
comes to join,  there is a mismatch in some cases. I am using JAVA code
version(Not Spring Version).

Example: 

Table A has code as below :- 
HashMap aliases = new HashMap<>();
aliases.put("id", "ID");
aliases.put("accountType", "Account_Type");
aliases.put("subCategory", "Sub_Category");
qryEntity.setAliases(aliases);
ArrayList indexes = new ArrayList<>();
QueryIndex index = new QueryIndex();
index.setName("NonClustered_Index_LC");
index.setIndexType(QueryIndexType.SORTED);
LinkedHashMap indFlds = new LinkedHashMap<>();
indFlds.put("id", true);
indFlds.put("accountType", true);
indFlds.put("subCategory", true);
index.setFields(indFlds);
indexes.add(index);
qryEntity.setIndexes(indexes);

Table B has below :- 

HashMap aliases = new HashMap<>();
aliases.put("id", "ID");
aliases.put("accountType", "Account_Type");
aliases.put("subCategory", "Sub_Category");
qryEntity.setAliases(aliases);
ArrayList indexes = new ArrayList<>();
QueryIndex index = new QueryIndex();
index.setName("NonClustered_Index_LC");
index.setIndexType(QueryIndexType.SORTED);
LinkedHashMap indFlds = new LinkedHashMap<>();
indFlds.put("accountNumber", true);
indFlds.put("accountType", true);
indFlds.put("assetClassAllocation", true);
index.setFields(indFlds);
indexes.add(index);
qryEntity.setIndexes(indexes);


When  below query is executed with JOIN executed count returns correct and
results in both SQL and IGNITE is correct i.e 20.

SELECT 
count(*)
FROM 
TABLEA WAS
INNER JOIN TABLEB CSS ON 
WAS.accountType = CSS.accountType
--
But when joined with one additional parameter as below, I get different
results different from database (i.e database has 127 and ignite shows 66).

SELECT 
count(*)
FROM 
TABLEA WAS
INNER JOIN TABLEB CSS ON 
WAS.accountType = CSS.accountType
AND was.assetClassAllocation = css.subCategory.

Any suggestion? Note I have the data in index.





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


Re: Ignite Query Slow

2018-12-11 Thread Skollur
is there anyway i can run ignite on machine and port without discovery?



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


Re: Ignite Query Slow

2018-12-11 Thread Skollur
It is different machine. Wondering why not able to use same port? I have put
the IP and port for each node in different machine.

Machine 1: node
discovery.setLocalAddress("192.2.2.1");
discovery.setLocalPort(new Integer("10800")));

Machine 2: node 
discovery.setLocalAddress("192.2.2.2");
discovery.setLocalPort(new Integer("10800")));



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


Re: Ignite Query Slow

2018-12-11 Thread Skollur
I have following code in node1 ->
TcpDiscoverySpi discovery = new TcpDiscoverySpi();
discovery.setLocalAddress("192.2.2.1");
discovery.setLocalPort(new Integer("10800")));
cfg.setDiscoverySpi(discovery);


and node 2 ->
TcpDiscoverySpi discovery = new TcpDiscoverySpi();
discovery.setLocalAddress("192.2.2.2");
discovery.setLocalPort(new Integer("10800")));
cfg.setDiscoverySpi(discovery);


But I see node2 is starting in port 10801 and not 10800. How this is
possible?



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


Re: Ignite Query Slow

2018-12-10 Thread Skollur
sql-performance.PNG
 
 
enclosed sql performance time.



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


Re: Ignite Query Slow

2018-12-10 Thread Skollur
Ok..Will 2 nodes helps? I saw only one node is busy most of time since I have
configured as REPLICATE and also found that REPLICATE is faster in multi
join queries than PARTITIONED in my case. Is there anyway REPLICATE (with 2
nodes) take loads equally among 2 nodes?



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


Re: Ignite Query Slow

2018-12-10 Thread Skollur
How about 6 cores. Will that help? In that case what is the thread counts?




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


Re: Ignite Query Slow

2018-12-10 Thread Skollur
Enclosed CPU/Thread usage. Ignite  became super slow after applying below.  I
am still not sure how many threads are required to span 100 queries
simultaneously. I am seeing CPU is hitting almost 100%.

cfg.setQueryThreadPoolSize(16); 
cfg.setSystemThreadPoolSize(16); 
cfg.setPublicThreadPoolSize(16); 
cfg.setServiceThreadPoolSize(16); 
cfg.setRebalanceThreadPoolSize(10); 

Will below helps?
//ccfg.setSqlOnheapCacheEnabled(true);  //ccfg.setOnheapCacheEnabled(true);



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


Re: Ignite Query Slow

2018-12-06 Thread Skollur
Thank you for reply. I have 2 core, 20 GB memory space allocated for Ignite
cache. My data size is about 3 to 4 GB.  I have batch process(multi
threaded) where simultaneously 100 requests sends to ignite cache (same
query with different parameters for each request).

What is the recommended thread pool size for 100 requests at a time? Is just 
setQueryThreadPoolSize(16) is enough or do I need to increase or any other
parameter needs to be considered?

After your reply, I have setup as below and can you please let me know if
anything missing here or to be added? Thanks for your help.

 
 cfg.setQueryThreadPoolSize(16);
cfg.setSystemThreadPoolSize(16);
cfg.setPublicThreadPoolSize(16);
cfg.setServiceThreadPoolSize(16);
cfg.setRebalanceThreadPoolSize(10);



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


Re: Ignite Query Slow

2018-12-06 Thread Skollur
Currently I have only one node and other node is idle and brought it down.
I have noticed that only one node is busy and I have code as below.

IgniteConfiguration cfg = new IgniteConfiguration();
   TcpDiscoverySpi discovery = new TcpDiscoverySpi();
discovery.setLocalAddress("192.0.1.2");
discovery.setLocalPort(10800);
cfg.setDiscoverySpi(discovery);
cfg.setPeerClassLoadingEnabled(true);



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


Re: Ignite Query Slow

2018-12-04 Thread Skollur
Ignite.zip
  
Ignite is using high CPU and enclosed high CPU profile. Let me know if you
need any further information to help us on this.



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


Re: Ignite Query Slow

2018-11-27 Thread Skollur
Attached.

Thanks gclog.zip
  



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


Re: Ignite Query Slow

2018-11-26 Thread Skollur
Also attached GC->

2018-11-26T13:35:23.058-0500: 1172.703: [GC pause (G1 Evacuation Pause)
(young), 0.0070730 secs]
   [Parallel Time: 6.3 ms, GC Workers: 2]
  [GC Worker Start (ms): Min: 1172702.9, Avg: 1172703.3, Max: 1172703.7,
Diff: 0.8]
  [Ext Root Scanning (ms): Min: 1.1, Avg: 1.4, Max: 1.7, Diff: 0.7, Sum:
2.8]
  [Update RS (ms): Min: 0.6, Avg: 0.7, Max: 0.7, Diff: 0.1, Sum: 1.3]
 [Processed Buffers: Min: 5, Avg: 7.0, Max: 9, Diff: 4, Sum: 14]
  [Scan RS (ms): Min: 0.2, Avg: 0.2, Max: 0.2, Diff: 0.0, Sum: 0.4]
  [Code Root Scanning (ms): Min: 0.1, Avg: 0.1, Max: 0.1, Diff: 0.0,
Sum: 0.2]
  [Object Copy (ms): Min: 3.4, Avg: 3.4, Max: 3.5, Diff: 0.1, Sum: 6.9]
  [Termination (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.0]
 [Termination Attempts: Min: 1, Avg: 1.0, Max: 1, Diff: 0, Sum: 2]
  [GC Worker Other (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum:
0.1]
  [GC Worker Total (ms): Min: 5.4, Avg: 5.8, Max: 6.2, Diff: 0.8, Sum:
11.6]
  [GC Worker End (ms): Min: 1172709.1, Avg: 1172709.1, Max: 1172709.1,
Diff: 0.0]
   [Code Root Fixup: 0.0 ms]
   [Code Root Purge: 0.0 ms]
   [Clear CT: 0.1 ms]
   [Other: 0.7 ms]
  [Choose CSet: 0.0 ms]
  [Ref Proc: 0.2 ms]
  [Ref Enq: 0.0 ms]
  [Redirty Cards: 0.1 ms]
  [Humongous Register: 0.0 ms]
  [Humongous Reclaim: 0.0 ms]
  [Free CSet: 0.2 ms]
   [Eden: 296.0M(296.0M)->0.0B(294.0M) Survivors: 3072.0K->4096.0K Heap:
456.9M(512.0M)->161.4M(512.0M)]
 [Times: user=0.01 sys=0.00, real=0.00 secs] 
2018-11-26T13:35:23.305-0500: 1172.950: [GC pause (G1 Evacuation Pause)
(young), 0.0065406 secs]
   [Parallel Time: 5.8 ms, GC Workers: 2]
  [GC Worker Start (ms): Min: 1172950.3, Avg: 1172950.3, Max: 1172950.3,
Diff: 0.0]
  [Ext Root Scanning (ms): Min: 1.4, Avg: 1.4, Max: 1.5, Diff: 0.0, Sum:
2.9]
  [Update RS (ms): Min: 0.5, Avg: 0.5, Max: 0.6, Diff: 0.0, Sum: 1.1]
 [Processed Buffers: Min: 3, Avg: 5.0, Max: 7, Diff: 4, Sum: 10]
  [Scan RS (ms): Min: 0.2, Avg: 0.2, Max: 0.2, Diff: 0.0, Sum: 0.3]
  [Code Root Scanning (ms): Min: 0.1, Avg: 0.1, Max: 0.1, Diff: 0.0,
Sum: 0.2]
  [Object Copy (ms): Min: 3.4, Avg: 3.4, Max: 3.4, Diff: 0.0, Sum: 6.8]
  [Termination (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.0]
 [Termination Attempts: Min: 1, Avg: 1.0, Max: 1, Diff: 0, Sum: 2]
  [GC Worker Other (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum:
0.1]
  [GC Worker Total (ms): Min: 5.7, Avg: 5.7, Max: 5.7, Diff: 0.0, Sum:
11.4]
  [GC Worker End (ms): Min: 1172956.0, Avg: 1172956.0, Max: 1172956.0,
Diff: 0.0]
   [Code Root Fixup: 0.0 ms]
   [Code Root Purge: 0.0 ms]
   [Clear CT: 0.1 ms]
   [Other: 0.7 ms]
  [Choose CSet: 0.0 ms]
  [Ref Proc: 0.2 ms]
  [Ref Enq: 0.0 ms]
  [Redirty Cards: 0.1 ms]
  [Humongous Register: 0.0 ms]
  [Humongous Reclaim: 0.0 ms]
  [Free CSet: 0.2 ms]
   [Eden: 294.0M(294.0M)->0.0B(293.0M) Survivors: 4096.0K->4096.0K Heap:
455.4M(512.0M)->161.5M(512.0M)]
 [Times: user=0.01 sys=0.00, real=0.01 secs] 
2018-11-26T13:35:23.590-0500: 1173.235: [GC pause (G1 Evacuation Pause)
(young), 0.0068220 secs]
   [Parallel Time: 6.1 ms, GC Workers: 2]
  [GC Worker Start (ms): Min: 1173235.1, Avg: 1173235.2, Max: 1173235.2,
Diff: 0.0]
  [Ext Root Scanning (ms): Min: 1.4, Avg: 1.5, Max: 1.6, Diff: 0.1, Sum:
3.0]
  [Update RS (ms): Min: 0.6, Avg: 0.6, Max: 0.7, Diff: 0.1, Sum: 1.3]
 [Processed Buffers: Min: 6, Avg: 7.0, Max: 8, Diff: 2, Sum: 14]
  [Scan RS (ms): Min: 0.2, Avg: 0.2, Max: 0.2, Diff: 0.1, Sum: 0.4]
  [Code Root Scanning (ms): Min: 0.1, Avg: 0.1, Max: 0.1, Diff: 0.0,
Sum: 0.2]
  [Object Copy (ms): Min: 3.4, Avg: 3.5, Max: 3.5, Diff: 0.1, Sum: 6.9]
  [Termination (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.0]
 [Termination Attempts: Min: 1, Avg: 1.0, Max: 1, Diff: 0, Sum: 2]
  [GC Worker Other (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum:
0.1]
  [GC Worker Total (ms): Min: 5.9, Avg: 5.9, Max: 5.9, Diff: 0.0, Sum:
11.8]
  [GC Worker End (ms): Min: 1173241.0, Avg: 1173241.0, Max: 1173241.0,
Diff: 0.0]
   [Code Root Fixup: 0.0 ms]
   [Code Root Purge: 0.0 ms]
   [Clear CT: 0.1 ms]
   [Other: 0.6 ms]
  [Choose CSet: 0.0 ms]
  [Ref Proc: 0.1 ms]
  [Ref Enq: 0.0 ms]
  [Redirty Cards: 0.0 ms]
  [Humongous Register: 0.0 ms]
  [Humongous Reclaim: 0.0 ms]
  [Free CSet: 0.2 ms]
   [Eden: 293.0M(293.0M)->0.0B(293.0M) Survivors: 4096.0K->4096.0K Heap:
454.5M(512.0M)->161.6M(512.0M)]
 [Times: user=0.01 sys=0.00, real=0.00 secs] 
2018-11-26T13:35:23.922-0500: 1173.567: [GC pause (G1 Evacuation Pause)
(young), 0.0075437 secs]
   [Parallel Time: 6.6 ms, GC Workers: 2]
  [GC Worker Start (ms): Min: 1173567.5, Avg: 1173567.5, Max: 1173567.5,
Diff: 0.0]
  [Ext Root Scanning (ms): Min: 1.5, Avg: 1.5, Max: 1.6, Diff: 0.1, Sum:
3.1]
  [Update RS (ms): Min: 0.5, Avg: 0.6, Max: 0.7, Diff: 

Re: Ignite Query Slow

2018-11-26 Thread Skollur
Hello

Are u suggesting to have more nodes with REPLICATE OR PARTITIONED settings?

Thanks



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


Ignite Query Slow

2018-11-23 Thread Skollur
Hello

I have ignite server running with 2 nodes. Each node has 30 cache stores
with one table in each with REPLICATE configured. Found query is taking
longer to return when simultaneous 100 requests were sent to ignite. In the
first iteration the query is quick. But as number of hits more, same query
with different parameter takes longer. Note I have INDEX for each of joins
and query is quick for one request and takes about 400 milli seconds and
same query takes longer about 30 seconds when multiple simultaneous requests
were processing. Is there any solution?

Thanks



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


Ignite Query Slow

2018-11-23 Thread Skollur
Hello

I have ignite server running with 2 nodes. Each node has 30 cache stores
with one table in each with REPLICATE configured. Found query is taking
longer to return when simultaneous 100 requests were sent to ignite. In the
first iteration the query is quick. But as number of hits more, same query
with different parameter takes longer. Note I have INDEX for each of joins
and query is quick for one request and takes about 400 milli seconds and
same query takes longer when multiple simultaneous requests. Is there any
solution?

Thanks



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


Security Setup

2018-11-05 Thread Skollur
I am trying to setup basic login and password. I have coded as below but
getting an error as in the Ignite documentation. 

IgniteConfiguration cfg = new IgniteConfiguration();
// Ignite persistence configuration.
DataStorageConfiguration storageCfg = new
DataStorageConfiguration();
// Enabling the persistence.
   
storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);
// Applying settings.
cfg.setDataStorageConfiguration(storageCfg);
// Enable authentication
cfg.setAuthenticationEnabled(true);
===
12:20:25,012][SEVERE][main][IgniteKernal%idb] Exception during start
processors, node will be stopped and close connections
class org.apache.ignite.IgniteCheckedException: Failed to start processor:
GridProcessorAdapter []
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1742)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:995)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:671)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:596)
at org.apache.ignite.Ignition.start(Ignition.java:327)
at
com.idb.cache.init.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:15)
Caused by: class org.apache.ignite.IgniteCheckedException: Reading
marshaller mapping from file com failed; last symbol of file name is
expected to be numeric.
at
org.apache.ignite.internal.MarshallerMappingFileStore.getPlatformId(MarshallerMappingFileStore.java:223)
at
org.apache.ignite.internal.MarshallerMappingFileStore.restoreMappings(MarshallerMappingFileStore.java:164)
at
org.apache.ignite.internal.MarshallerContextImpl.onMarshallerProcessorStarted(MarshallerContextImpl.java:539)
at
org.apache.ignite.internal.processors.marshaller.GridMarshallerMappingProcessor.start(GridMarshallerMappingProcessor.java:114)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
... 8 more
Caused by: java.lang.NumberFormatException: For input string: "m"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Byte.parseByte(Byte.java:149)
at java.lang.Byte.parseByte(Byte.java:175)
at
org.apache.ignite.internal.MarshallerMappingFileStore.getPlatformId(MarshallerMappingFileStore.java:220)



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


RE: Ignite Query Slow

2018-10-23 Thread Skollur
Any help on this?



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


RE: Ignite Query Slow

2018-10-17 Thread Skollur
Thank you..Tried @QuerySQLFields...but column name not appeared same as
database table(i.e underscore("_") is missing in ignite). Hence I have added
index to qryEntity and noticed that Query takes about 7 seconds (i.e select
* from customercache.customer) for against ignite cache data of 200,000
records to fetch 200 records in dbeaver. Same query against database comes
in fractions of seconds. I have INDEX created for two fields. I am running
cache with 8 GB Memory, one server node. The codes are mostly generated from
ignite web console. Is there anything am I missing from below code or
anything can be improved on below code? Any suggestion to improve this
helps.



Cache Code

public class CustomerCache {
public static CacheConfiguration cacheCustomerCache() throws Exception {
CacheConfiguration ccfg = new CacheConfiguration();
ccfg.setName("CustomerCache");
ccfg.setCacheMode(CacheMode.PARTITIONED);
ccfg.setAtomicityMode(CacheAtomicityMode.ATOMIC);
CacheJdbcPojoStoreFactory cacheStoreFactory = new
CacheJdbcPojoStoreFactory();
cacheStoreFactory.setDataSourceFactory(new Factory() {
@Override public DataSource create() {
return DataSources.INSTANCE_DB;
};
});

cacheStoreFactory.setDialect(new SQLServerDialect());
cacheStoreFactory.setTypes(jdbcTypeCustomer(ccfg.getName()));
ccfg.setCacheStoreFactory(cacheStoreFactory);
ccfg.setReadThrough(true);
ccfg.setWriteThrough(true);
ArrayList qryEntities = new ArrayList<>();
QueryEntity qryEntity = new QueryEntity();
qryEntity.setKeyType("java.lang.Long");
qryEntity.setValueType("com.model.Customer");
LinkedHashMap fields = new LinkedHashMap<>();
fields.put("dwId", "java.lang.Long");
fields.put("customerId", "java.lang.Long");
fields.put("customerName", "java.lang.String");
qryEntity.setFields(fields);
HashMap aliases = new HashMap<>();
aliases.put("dwId", "DW_Id");
aliases.put("customerId", "Customer_ID");
aliases.put("customerName", "Customer_Name");
qryEntity.setAliases(aliases);

/Adding Index   
ArrayList indexes = new ArrayList<>();
QueryIndex index = new QueryIndex();
index.setName("NonClustered_Index_ID");
index.setIndexType(QueryIndexType.SORTED);
LinkedHashMap indFlds = new LinkedHashMap<>();
indFlds.put("dwId", true);
indFlds.put("customerId", true);
index.setFields(indFlds);
indexes.add(index);
qryEntity.setIndexes(indexes);


qryEntities.add(qryEntity);
ccfg.setQueryEntities(qryEntities);
return ccfg;
}

private static JdbcType jdbcTypeCustomer(String cacheName) {
JdbcType type = new JdbcType();
type.setCacheName(cacheName);
type.setKeyType("java.lang.Long");
type.setValueType("com.model.Customer");
type.setDatabaseSchema("dbo");
type.setDatabaseTable("Customer");
type.setValueFields(
new JdbcTypeField(Types.BIGINT, "DW_Id", long.class, "dwId"),
new JdbcTypeField(Types.BIGINT, "Customer_ID", Long.class,
"customerId"),
new JdbcTypeField(Types.VARCHAR, "First_Name", String.class,
"customerName")
);
return type;
}
}

POJO Class
--

public class Customer implements Serializable {
private static final long serialVersionUID = 0L;
private long dwId;
private Long customerId;
}



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


Duplicate Table Error

2018-10-12 Thread Skollur
Getting an error Duplicate table name [cache=CustomerCache,tblName=CUSTOMER,
type1=Customer, type2=Customer] when i tried to add index as below

ccfg.setIndexedTypes(Long.class,Customer.class);

public class Customer implements Serializable {
/** Value for dwId. */
@QuerySqlField(index = true)
private long dwId;
}

class CustomerCache{


qryEntities.add(qryEntity);
ccfg.setIndexedTypes(Long.class,Customer.class);
ccfg.setQueryEntities(qryEntities);
return ccfg;
}





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


Re: Ignite Query Slow

2018-10-02 Thread Skollur
Documentation has example as ccfg.setIndexedTypes(Long.class, Person.class);.
I believe this is single field. How to register multiple indexes for
CacheConfiguration?




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


Re: Ignite Query Slow

2018-10-01 Thread Skollur
I tried with setting up field with @QuerySqlField (index = true) and still
slow.

Example : 
/** Value for customerId. */
@QuerySqlField (index = true)
private Long customerId



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


Re: Apache Ingite Join returns wrong records

2018-10-01 Thread Skollur
Is there setDistributedJoins at cache level?



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


Re: Ignite Query Slow

2018-09-28 Thread Skollur
Thank you for suggestion. Can you give example how to create secondary
indices?



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


Apache Ingite Join returns wrong records

2018-09-28 Thread Skollur
I am using Apache Ignite 2.6 version. I have two tables as below i.e SUMMARY
and SEQUENCE

SUMMARY-> DW_Id bigint (Primary key) , Sumamry_Number varchar, Account_Type
varchar
SEQUENCE-> DW_Id bigint (Primary key) , Account_Type varchar

Database and cache has same number of records in both tables. Database JOIN
query returns 1500 counts/records and However IGNITE JOIN returns only 4
counts and 4 records. Ignite cache is build based on auto generated web
console. Query used is as below. There is no key involved while joining two
cache tables here from two cache.tables. This is simple join based on
value(i.e account type - string). How to get correct value for JOIN in
Ignite?

SELECT COUNT(*) FROM SUMMARY LIQ 
INNER JOIN SEQUENCE CPS ON
LIQ.Account_Type = CPS.Account_Type




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


Re: Ignite Query Slow

2018-09-28 Thread Skollur
Here is the explain query

#   PLAN
1   "SELECT
ADDR__Z2.ADDRESS_LINE_1 AS __C0_0,
ADDR__Z2.ADDRESS_LINE_2 AS __C0_1,
ADDR__Z2.ADDRESS_LINE_3 AS __C0_2,
ADDR__Z2.STREET AS __C0_3,
ADDR__Z2.CITY AS __C0_4,
ADDR__Z2.STATE AS __C0_5,
ADDR__Z2.COUNTRY AS __C0_6,
ADDR__Z2.ZIP_POSTAL AS __C0_7
FROM "GroupAddressCache".GROUP_ADDRESS GA__Z1
/* "GroupAddressCache".GROUP_ADDRESS.__SCAN_ */
/* WHERE (GA__Z1.ADDRESS_TYPE = 'Mailing')
AND (GA__Z1.RECORD_IS_VALID = 'Y')
*/
INNER JOIN "GroupCache"."[GROUP]" GRP__Z0
/* "GroupCache"."[GROUP]".__SCAN_ */
ON 1=1
/* WHERE (GRP__Z0.RECORD_IS_VALID = 'Y')
AND ((GRP__Z0.GROUP_CUSTOMER_ID = 44)
AND (GRP__Z0.GROUP_CUSTOMER_ID = GA__Z1.GROUP_CUSTOMER_ID))
*/
INNER JOIN "AddressCache".ADDRESS ADDR__Z2
/* "AddressCache"."_key_PK_proxy": DW_ID = GA__Z1.ADDRESS_ID */
ON 1=1
WHERE (GA__Z1.ADDRESS_ID = ADDR__Z2.DW_ID)
AND ((GA__Z1.ADDRESS_TYPE = 'Mailing')
AND ((GA__Z1.RECORD_IS_VALID = 'Y')
AND ((GRP__Z0.GROUP_CUSTOMER_ID = GA__Z1.GROUP_CUSTOMER_ID)
AND ((GRP__Z0.GROUP_CUSTOMER_ID = 44)
AND (GRP__Z0.RECORD_IS_VALID = 'Y')"
2   "SELECT
__C0_0 AS ADDRESS_LINE_1,
__C0_1 AS ADDRESS_LINE_2,
__C0_2 AS ADDRESS_LINE_3,
__C0_3 AS STREET,
__C0_4 AS CITY,
__C0_5 AS STATE,
__C0_6 AS COUNTRY,
__C0_7 AS ZIP_POSTAL
FROM PUBLIC.__T0
/* PUBLIC."merge_scan" */"



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


Re: Ignite Query Slow

2018-09-27 Thread Skollur
1. I have defined primary key - dwId 
2. Not defined affinity_key since there is no Forgein Key in table. 
3. 
CacheConfiguration ccfg = new CacheConfiguration();
ccfg.setName(cacheName);
ccfg.setCacheMode(CacheMode.PARTITIONED);
ccfg.setAtomicityMode(CacheAtomicityMode.ATOMIC);
ccfg.setPeerClassLoadingEnabled(true); 

The code i am using is generated from ignite web console.

Code is below.


CacheConfiguration
ccfg=CacheConfigurationInitialize.initCacheConfiguration(
IdbCacheConstants.GROUP_MEMBER_CACHE, 

jdbcTypeGroupMember(IdbCacheConstants.GROUP_MEMBER_CACHE));

ArrayList qryEntities = new ArrayList<>();

QueryEntity qryEntity = new QueryEntity();

qryEntity.setKeyType("java.lang.Long");
qryEntity.setValueType("com.idb.cache.model.GroupMember");
qryEntity.setTableName("Group_Member");
qryEntity.setKeyFieldName("dwId");

HashSet keyFields = new HashSet<>();

keyFields.add("dwId");

qryEntity.setKeyFields(keyFields);

LinkedHashMap fields = new LinkedHashMap<>();

fields.put("dwId", "java.lang.Long");
fields.put("groupCustomerId", "java.lang.Long");
fields.put("customerId", "java.lang.Long");
fields.put("role", "java.lang.String");
fields.put("isPrimary", "java.lang.String");
fields.put("recordValidFromDate", "java.sql.Date");
fields.put("recordValidToDate", "java.sql.Date");
fields.put("recordIsValid", "java.lang.String");
fields.put("recordCreatedTime", "java.sql.Timestamp");
fields.put("recordCreatedBy", "java.lang.String");
fields.put("recordUpdatedTime", "java.sql.Timestamp");
fields.put("recordUpdatedBy", "java.lang.String");
fields.put("dwBatch", "java.lang.Long");
fields.put("dwSourcecode", "java.lang.String");
fields.put("dwTimestamp", "java.sql.Timestamp");

qryEntity.setFields(fields);

HashMap aliases = new HashMap<>();

aliases.put("dwId", "DW_Id");
aliases.put("groupCustomerId", "Group_Customer_ID");
aliases.put("customerId", "Customer_ID");
aliases.put("recordValidFromDate", "Record_Valid_From_Date");
aliases.put("recordValidToDate", "Record_Valid_To_Date");
aliases.put("recordIsValid", "Record_Is_Valid");
aliases.put("recordCreatedTime", "Record_Created_Time");
aliases.put("recordCreatedBy", "Record_Created_By");
aliases.put("recordUpdatedTime", "Record_Updated_Time");
aliases.put("recordUpdatedBy", "Record_Updated_By");
aliases.put("dwBatch", "DW_Batch");
aliases.put("dwSourcecode", "DW_SourceCode");
aliases.put("dwTimestamp", "DW_TimeStamp");

qryEntity.setAliases(aliases);
qryEntities.add(qryEntity);

ccfg.setQueryEntities(qryEntities);

return ccfg;



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


Ignite Query Slow

2018-09-27 Thread Skollur
I have 3 cache store and each has its own table. When I tried to do simple
join, query is taking longer in DBeaver.  Server topology is ver=4,
servers=1, clients=1, CPUs=4, offheap=3.2GB, heap=6.0GB

Cache 1. GroupCache"."[GROUP]" has 100k records
Cache 2. "GroupMemberCache".GROUP_MEMBER  has 200k records
Cache 3. "CustomerCache".CUSTOMER has 200k records

Query is as below
SELECT CUST.Name
FROM "GroupCache"."[GROUP]" GRP
INNER JOIN "GroupMemberCache".GROUP_MEMBER GM
ON GRP.Group_Customer_ID = 44 
INNER JOIN "CustomerCache".CUSTOMER CUST
ON GM.Customer_ID = CUST.Customer_ID
AND GM.Record_Is_Valid = 'Y'
AND GRP.Record_Is_Valid = 'Y'
AND GRP.Group_Customer_ID = GM.Group_Customer_ID
AND GM.Record_Is_Valid = 'Y'

Query is executing longer than 2000 seconds. Any suggestion on this?



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


Re: Error while loading data to cache

2018-09-18 Thread Skollur
Your suggestion is working.Thank you.



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


Error while loading data to cache

2018-09-17 Thread Skollur
I am trying to load data to cache using below code and seeing an error.


ignite.cache("CustomerCache").loadCache(new IgniteBiPredicate()
{
@Override
public boolean apply(Object key, Object value) {
if(((Customer) value).getId()==11);
return true;
}
});

ERROR:-

Caused by: java.lang.ClassCastException:
org.apache.ignite.internal.binary.BinaryObjectImpl cannot be cast to
com.idb.cache.model.Customer
at
com.idb.cache.load.LoadIdbIgniteCaches$1.apply(LoadIdbIgniteCaches.java:36)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.loadEntry(GridDhtCacheAdapter.java:639)



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


Re: Loading Cache

2018-09-17 Thread Skollur
Tried below code, but code is not complaining in IDE..Keep seeing error
message asking to change the method loadcache() to method localloadCache().
When changed to method localloadcache(), asking to change method to
loadCache().


ignite.cache("CustomerCache").loadCache(new
IgniteBiPredicate(){
@Override
public boolean apply(Object key, Customer 
customer) {
return 
customer.field("dwTimestamp").after(fromDate) &&
customer.field("dwTimestamp").after(toDate);
}}, null);



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


Igniter TCPDiscovery

2018-09-05 Thread Skollur
I have two independent machines where ignite server node is running. i.e 
,193.169.15.50 and ,193.169.15.51. Both are running with two different
versions of cache. However when i tried to load the data to cache(i.e
,193.169.15.50) from one of these machine, it always finds another machine
(i.e 193.169.15.51) and mismatch while loading the data. How this is
possible when I had code as below?

TcpDiscoverySpi discovery = new TcpDiscoverySpi();
   TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
  
ipFinder.setAddresses(Arrays.asList("127.0.0.1:10800,93.169.15.50")));
   discovery.setIpFinder(ipFinder);
   cfg.setDiscoverySpi(discovery);
   cfg.setPeerClassLoadingEnabled(true);






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


Re: Loading Cache

2018-09-05 Thread Skollur
Thank you for reply. Is there example can you provide to load the data with
criteria i.e load data (select query) is based on date range is restricted.

i.e cache.loadcache(select * from table name where date = '02/02/108').



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


Loading Cache

2018-08-21 Thread Skollur
Currently I am loading data with one line in java. Below ocmmand will load
all data from database to Cache.
Example: ignite.cache("CustomerCache").loadCache(null);

I would like to load data for specific period. How would I do that?




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


Re: Running Server Node in UNIX

2018-07-17 Thread Skollur
Running below command in UNIX and getting error.it runs fine in windows
in eclipse..any help on this?

1. java -cp /opt/lib/*.jar:/opt/com/test/cache/*.*:/opt/com/test/config/*.*
ServerNodeCodeStartup   Error: Could not find or load main class
ServerNodeCodeStartup

2. java -cp /opt/lib/*.jar:/opt/com/test/cache/*.*:/opt/com/test/config/*.*
com.test.cache.ServerNodeCodeStartup   Error: Could not find or
load main class ServerNodeCodeStartup





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


Re: Running Server Node in UNIX

2018-07-17 Thread Skollur
is any help on this?



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


Re: Running Server Node in UNIX

2018-07-16 Thread Skollur
Thank you. I have all jars in lib as below and added to the cp command.

lib folder -
./lib/ignite-indexing-2.5.0.jar
./lib/ignite-rest-http-2.5.0.jar
./lib/mssql-jdbc-6.4.0.jre8.jar
./lib/ignite-slf4j-2.5.0.jar 
./ib/...jar

source code compiled as below structure(.class)
-com/cache/constant/*.class
-com/cache/domain/*.class
-com/cache/load/*.class
-com/cache/init/ServerNodeCodeStartup.class


Tried both below.
1)java -cp ./opt/lib/*.jar com/cache/init/ServerNodeCodeStartup and output
Error: Could not find or load main class
com.cache.init.ServerNodeCodeStartup

2)cd /com/cache/init/
Tried java -cp ./opt/lib/*.jar ServerNodeCodeStartup and output
Error: Could not find or load main class ServerNodeCodeStartup








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


Re: Running Server Node in UNIX

2018-07-16 Thread Skollur
I don't have IGNITE_HOME set up from my windows- eclipse and able to run
without any issue. 
I have ignite-core, ignite-spring, ignite-indexing and ignite-rest-http in
the pom.xml.

I am trying to run same structure in UNIX. I have required libs in the jar.
Is anything am i missing?



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


Running Server Node in UNIX

2018-07-16 Thread Skollur
Hello,

I am trying to run Ignite in Unix and getting below error. Same program runs
works from Eclipse.

Command:
java -cp /opt/cache/ignite-cache.jar
com/test/cache/init/ServerNodeCodeStartup 

Packaged into ignite-cache.jar

Class Structure:
 -com/test/cache/*.classes
 -lib/*.jar 
 -META-INF


Output :
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/ignite/spi/discovery/tcp/ipfinder/TcpDiscoveryIpFinder
at
com.idb.cache.init.ServerNodeCodeStartup.main(ServerNodeCodeStartup.java:15)
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 1 more
==






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


Re: Apache Ignite Rest API JOIN with multiple Caches

2018-06-20 Thread Skollur
The above solution works fine with Ignite JDBC and however I am trying with
Ignite REST API. 

http://localhost:8080/ignite?cmd=qryfldexe&pageSize=100&cacheName=CustomerCache&qry=select+id+from+Customer
c+join+
AccountCache.account a+on+where+c.id=a.id

I am getting 
"error": "Schema \"ACCOUNTCACHE\" not found; SQL statement:






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


Apache Ignite Rest API JOIN with multiple Caches

2018-06-20 Thread Skollur
Hello,


I have two objects i.e account and customer loaded to apache ignite server.
Both objects are loaded with data and each of them stored in its cache.
Account object/table is loaded to accountcache and customer object/table is
loaded to customercache. I am trying to access both the tables with join
using apache ignite rest api. I am unable to use join using rest-api-.2.5.0
version.

Cache Structure  and table/object

CustomerCache -> customer
AccountCache-> account

Below Rest URL works for me.
a)
http://localhost:8080/ignite?cmd=qryfldexe&pageSize=1000&cacheName=CustomerCache&qry=select+id+from+customer

b)
http://localhost:8080/ignite?cmd=qryfldexe&pageSize=1000&cacheName=AccountCache&qry=select+id+from+account.

I would like to execute join on both CustomerCache.customer and
AccountCache.account. However I am unable to do so. Could you please provide
join cache/table example using apache ignite rest api?

I tried below
http://localhost:8080/ignite?cmd=qryfldexe&pageSize=1000&cacheName=CustomerCache&AccountCache&qry=select+id+from+Customer
c+join+
account a+on+where+c.id=a.id 

It throws an error  :"error": "Table \"ACCOUNT\" not found; SQL
statement:\nselect id from




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