queryParallelism in server XML

2017-12-12 Thread Ahmad Al-Masry 
Dears;
How can I enable CacheConfiguration.queryParallelism in server XML?
BR

-- 



This email, and the content it contains, are intended only for the persons 
or entities to which it is addressed. It may contain sensitive, 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended 
recipient(s) is prohibited. If you received this email in error, please 
immediately contact security[at]harri[dot]com and delete it from any device 
or system on which it may be stored.

Re: Data lose in query

2017-12-11 Thread Ahmad Al-Masry 
How can I enable this on the server configuration XML?
BR

> On Dec 11, 2017, at 2:31 PM, Nikolai Tikhonov <ntikho...@apache.org> wrote:
> 
> Hi,
> 
> Strongly recommend to care about collocation of your data (as above suggested 
> by Vlad) instead of enable DistributedJoins flag. The performance of this 
> type of joins is worse then the performance of the affinity collocation based 
> joins due to the fact that there will be much more network round-trips and 
> data movement between the nodes to fulfill a query [1].
> 
> 1. 
> https://apacheignite-sql.readme.io/docs/distributed-joins#non-collocated-joins
>  
> <https://apacheignite-sql.readme.io/docs/distributed-joins#non-collocated-joins>
> 
> 
> On Mon, Dec 11, 2017 at 3:03 PM, Ahmad Al-Masry <ma...@harri.com 
> <mailto:ma...@harri.com>> wrote:
> Hi;
> When I enabled the distributed JOIN, get the following Exception:
> 
> java.sql.SQLException: javax.cache.CacheException: Failed to prepare 
> distributed join query: join condition does not use index 
> [joinedCache=PositionTypeCache
> 
> Should I remove the indexes before doing distributed joins?
> BR
> 
> 
>> On Dec 11, 2017, at 10:43 AM, Vladislav Pyatkov <vldpyat...@gmail.com 
>> <mailto:vldpyat...@gmail.com>> wrote:
>> 
>> Hi,
>> 
>> When you use JOIN, you should to enable DistributedJoins flag[1], or tack 
>> care about collocated of each joined entry[2].
>> 
>> [1]: org.apache.ignite.cache.query.SqlFieldsQuery#setDistributedJoins
>> [2]: https://apacheignite.readme.io/docs 
>> <https://apacheignite.readme.io/docs>
>> 
>> On Mon, Dec 11, 2017 at 11:36 AM, Ahmad Al-Masry <ma...@harri.com 
>> <mailto:ma...@harri.com>> wrote:
>> Dears;
>> The when I execute the attached query on Mysql data source or on a single 
>> node ignite, it returns about 25k records.
>> When multiple node, it gives me about 3500 records.
>> The caches are atomic and partitioned.
>> Any suggestions.
>> BR
>> 
>> --
>> 
>> 
>> 
>> This email, and the content it contains, are intended only for the persons
>> or entities to which it is addressed. It may contain sensitive,
>> confidential and/or privileged material. Any review, retransmission,
>> dissemination or other use of, or taking of any action in reliance upon,
>> this information by persons or entities other than the intended
>> recipient(s) is prohibited. If you received this email in error, please
>> immediately contact security[at]harri[dot]com and delete it from any device
>> or system on which it may be stored.
>> 
>> 
>> 
>> -- 
>> Vladislav Pyatkov
> 
> 
> 
> This email, and the content it contains, are intended only for the persons or 
> entities to which it is addressed. It may contain sensitive, confidential 
> and/or privileged material. Any review, retransmission, dissemination or 
> other use of, or taking of any action in reliance upon, this information by 
> persons or entities other than the intended recipient(s) is prohibited. If 
> you received this email in error, please immediately contact 
> security[at]harri[dot]com and delete it from any device or system on which it 
> may be stored.
> 


-- 



This email, and the content it contains, are intended only for the persons 
or entities to which it is addressed. It may contain sensitive, 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended 
recipient(s) is prohibited. If you received this email in error, please 
immediately contact security[at]harri[dot]com and delete it from any device 
or system on which it may be stored.

Re: Data lose in query

2017-12-11 Thread Ahmad Al-Masry 
Hi;
When I enabled the distributed JOIN, get the following Exception:

java.sql.SQLException: javax.cache.CacheException: Failed to prepare 
distributed join query: join condition does not use index 
[joinedCache=PositionTypeCache

Should I remove the indexes before doing distributed joins?
BR

> On Dec 11, 2017, at 10:43 AM, Vladislav Pyatkov <vldpyat...@gmail.com> wrote:
> 
> Hi,
> 
> When you use JOIN, you should to enable DistributedJoins flag[1], or tack 
> care about collocated of each joined entry[2].
> 
> [1]: org.apache.ignite.cache.query.SqlFieldsQuery#setDistributedJoins
> [2]: https://apacheignite.readme.io/docs <https://apacheignite.readme.io/docs>
> 
> On Mon, Dec 11, 2017 at 11:36 AM, Ahmad Al-Masry <ma...@harri.com 
> <mailto:ma...@harri.com>> wrote:
> Dears;
> The when I execute the attached query on Mysql data source or on a single 
> node ignite, it returns about 25k records.
> When multiple node, it gives me about 3500 records.
> The caches are atomic and partitioned.
> Any suggestions.
> BR
> 
> --
> 
> 
> 
> This email, and the content it contains, are intended only for the persons
> or entities to which it is addressed. It may contain sensitive,
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended
> recipient(s) is prohibited. If you received this email in error, please
> immediately contact security[at]harri[dot]com and delete it from any device
> or system on which it may be stored.
> 
> 
> 
> -- 
> Vladislav Pyatkov


-- 



This email, and the content it contains, are intended only for the persons 
or entities to which it is addressed. It may contain sensitive, 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended 
recipient(s) is prohibited. If you received this email in error, please 
immediately contact security[at]harri[dot]com and delete it from any device 
or system on which it may be stored.

Re: Query Execution Error when changing the cache from PARTITIONED to REPLICATED

2017-12-10 Thread Ahmad Al-Masry 
Dears;
I also noticed that when I reduced to single node, the problem happens, even 
that it has 2 GB free of RAM.
Any suggestions?
BR

> On Dec 10, 2017, at 4:23 PM, Ahmad Al-Masry <ma...@harri.com> wrote:
> 
> Dears;
> I try to execute a complex query on a cluster of two nodes,
> When the cashes are configured as PARTITIONED, the execution takes about 12 
> seconds, but when I changed it to REPLICATED, the attached error appears. And 
> when tried to increase Java heap, the query reaches to time out.
> Also attached is the nodes configuration.
> BR
> 


-- 



This email, and the content it contains, are intended only for the persons 
or entities to which it is addressed. It may contain sensitive, 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended 
recipient(s) is prohibited. If you received this email in error, please 
immediately contact security[at]harri[dot]com and delete it from any device 
or system on which it may be stored.

Apache Ignite Web Consol Monitor

2017-12-08 Thread Ahmad Al-Masry 
Hi;
I have installed Ignite Web Console on an Ubuntu 16.04.3 VM with OpenJDK 
1.8.0_151 using the steps in documentation:
https://apacheignite-tools.readme.io/docs/ignite-web-console 

I followed Build and Deploy and Run Ignite Web Console In Production Mode with 
Nginx. I successfully created a user and logged into the system. 
I can’t find the monitor tab that exists in the console hosted by GridGain in 
this video:
https://www.youtube.com/watch?v=V-o3IFVnk5k 

Is it supposed, and if yes how can I enable it?
BR 
-- 



This email, and the content it contains, are intended only for the persons 
or entities to which it is addressed. It may contain sensitive, 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, 
this information by persons or entities other than the intended 
recipient(s) is prohibited. If you received this email in error, please 
immediately contact security[at]harri[dot]com and delete it from any device 
or system on which it may be stored.

Re: Problem with loading data

2017-12-07 Thread Ahmad Al-Masry 
Dear;
After I did run the server code locally in debug mode, I found the problematic 
query:
SELECT
id,
job_id,
applicant_id,
bucket,
bucket_id,
STATUS,
ORDER,
is_new,
candidate_archived,
candidate_archived_date,
seen_by_candidate,
requirement_confirm,
applied_date,
started,
bucket_updated,
ats_notified,
work_eligibility_option_id,
_enabled,
created,
updated,
updated_by,
updated_by_type,
deleted,
deleted_on,
deleted_by,
employer_message_date,
candidate_message_date,
door_id,
device_type,
referrer,
referrer_campaign,
work_eligibility 
FROM
db.job_application;

The problem is that we have a column named “ORDER”, and the select query fails 
because ORDER is a keyword.
To overcome this, the column in the query should be quoted with ` (A.K.A 
`ORDER`) to work.
Is their any workaround?
BR

> On Dec 6, 2017, at 9:10 AM, Ahmad Al-Masry <ma...@harri.com> wrote:
> 
> Hi, and thank you for your reply;
> Attached are the project structure downloaded from web console and the tables 
> structure.
> Kindly your help.
> BR
> 
> 
> 
> 
> 
>> On Dec 5, 2017, at 5:35 PM, Nikolai Tikhonov <ntikho...@apache.org 
>> <mailto:ntikho...@apache.org>> wrote:
>> 
>> Hello!
>> 
>> It looks that Web Console generated an incorrect schema for PositionCache 
>> cache. Can you share CacheConfiguration and schema for the related table?
>> 
>> 
>> On Tue, Dec 5, 2017 at 5:00 PM, Ahmad Al-Masry <ma...@harri.com 
>> <mailto:ma...@harri.com>> wrote:
>> Hi;
>> Want to to test Ignite to improve the performance of our reporting system.
>> The datasource is MySQL. 
>> We used The Web Console to create the integration with MySQL and used the 
>> auto generated package from there to load the data.
>> Some the tables have loaded successfully and the rest did not, and the 
>> following of some of the exceptions:
>> 1- This Error gives SQL syntax error when trying to load Job table:
>> Dec 05, 2017 3:54:32 PM org.apache.ignite.logger.java.JavaLogger error
>> SEVERE: Failed to obtain remote job result policy for result from 
>> ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl 
>> [job=C2 [c=LoadCacheJobV2 [keepBinary=false]], sib=GridJobSiblingImpl 
>> [sesId=88b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, 
>> jobId=98b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, 
>> nodeId=705cc1c6-2965-4700-83b3-0fc9671a70e0, isJobDone=false], 
>> jobCtx=GridJobContextImpl 
>> [jobId=98b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, timeoutObj=null, 
>> attrs={}], node=TcpDiscoveryNode [id=705cc1c6-2965-4700-83b3-0fc9671a70e0, 
>> addrs=[0:0:0:0:0:0:0:1%lo, 10.10.11.31, 127.0.0.1], 
>> sockAddrs=[ip-10-10-11-31.ec2.internal/10.10.11.31:47500 
>> <http://10.10.11.31:47500/>, 0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500 
>> <http://127.0.0.1:47500/>], discPort=47500, order=1, intOrder=1, 
>> lastExchangeTime=1512482063467, loc=false, ver=2.3.0#19700101-sha1:, 
>> isClient=false], ex=class o.a.i.IgniteException: Failed to load cache: 
>> JobApplicationCache, hasRes=true, isCancelled=false, isOccupied=true]
>> class org.apache.ignite.IgniteException: Remote job threw user exception 
>> (override or implement ComputeTask.result(..) method if you would like to 
>> have automatic failover for this exception).
>>  at 
>> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1047)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1040)
>>  at 
>> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6663)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1040)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:858)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1066)
>>  at 
>> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1301)
>>  at 
>> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
>>  at 
>>

Problem with loading data

2017-12-05 Thread Ahmad Al-Masry 
Hi;
Want to to test Ignite to improve the performance of our reporting system.
The datasource is MySQL. 
We used The Web Console to create the integration with MySQL and used the auto 
generated package from there to load the data.
Some the tables have loaded successfully and the rest did not, and the 
following of some of the exceptions:
1- This Error gives SQL syntax error when trying to load Job table:
Dec 05, 2017 3:54:32 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to obtain remote job result policy for result from 
ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl 
[job=C2 [c=LoadCacheJobV2 [keepBinary=false]], sib=GridJobSiblingImpl 
[sesId=88b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, 
jobId=98b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, 
nodeId=705cc1c6-2965-4700-83b3-0fc9671a70e0, isJobDone=false], 
jobCtx=GridJobContextImpl 
[jobId=98b94f62061-b5688ca0-691e-4982-84e7-9f5cc596a8b7, timeoutObj=null, 
attrs={}], node=TcpDiscoveryNode [id=705cc1c6-2965-4700-83b3-0fc9671a70e0, 
addrs=[0:0:0:0:0:0:0:1%lo, 10.10.11.31, 127.0.0.1], 
sockAddrs=[ip-10-10-11-31.ec2.internal/10.10.11.31:47500, 
0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1512482063467, loc=false, 
ver=2.3.0#19700101-sha1:, isClient=false], ex=class 
o.a.i.IgniteException: Failed to load cache: JobApplicationCache, hasRes=true, 
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception 
(override or implement ComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
at 
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1047)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1040)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6663)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1040)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:858)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1066)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1301)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1555)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1183)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1090)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteException: Failed to load cache: 
JobApplicationCache
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1858)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6631)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1115)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1913)
... 7 more
Caused by: class org.apache.ignite.IgniteException: Failed to load cache: 
JobApplicationCache
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJob.localExecute(GridCacheAdapter.java:5472)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJobV2.localExecute(GridCacheAdapter.java:5516)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6131)
at 
org.apache.ignite.compute.ComputeJobAdapter.call(ComputeJobAdapter.java:132)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1855)
... 14 more