Re: Row count [select count(*) from table] not matching with the actual row count present in the table

[shivakumar]

HI 
Any Idea on this issue ? 
I have created Jira bug for this issue
https://issues.apache.org/jira/browse/IGNITE-11917


regars,
shiva



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

max number of TCP connections

[Clay Teahouse]

Hi All

What is the max number of TCP connections that can be specified for the
ListenSyslog processor?  The default seems to be 2.

thanks
Clay

Re: .net service method call error

[Pavel Tupitsyn]

Hi Som,

I've tried your code and did not get any errors, seems to work for me.
Can you please upload a minimal runnable project with a reproducer?
Maybe configuration is missing or some other things come into play.

Thanks,
Pavel

On Mon, Jun 17, 2019 at 12:17 PM Som Som <2av10...@gmail.com> wrote:

> hello.
>
> I’m trying to deploy a service and call its method. Topology is one server
> and one client.
>
>
>
> Service:
>
>
>
> [Serializable]
>
> public class Service1 : IService, IPlusMinusService
>
> {
>
> [InstanceResource]
>
> private readonly IIgnite _ignite;
>
>
>
> private ICache _cache;
>
>
>
> public void Init(IServiceContext context)
>
> {
>
> _cache = _ignite.GetCache("Test_Int_Int");
>
> }
>
>
>
> public void Execute(IServiceContext context)
>
> {
>
> //throw new NotImplementedException();
>
> }
>
>
>
> public void Cancel(IServiceContext context)
>
> {
>
> //throw new NotImplementedException();
>
> }
>
>
>
> public void PlusOne()
>
> {
>
> _cache.Put(1, _cache.Get(1) + 1);
>
> }
>
>
>
> public void MinusOne()
>
> {
>
> _cache.Put(1, _cache.Get(1) - 1);
>
> }
>
> }
>
>
>
>
>
> Code:
>
>  using (var ignite = Ignition.StartFromApplicationConfiguration())
>
> {
>
> var cache = ignite.GetOrCreateCache(
> "Test_Int_Int");
>
> cache.Put(1, 0);
>
>
>
> var cacheGrp = ignite.GetCluster().ForCacheNodes(
> "Test_Int_Int");
>
> var services = cacheGrp.GetServices();
>
> services.DeployNodeSingleton("SVC1_1",new Service1());
>
>
>
> IPlusMinusService SVC1_1 = services.GetService(
> "SVC1_1"); // Returns null
>
> IPlusMinusService proxy =
> services.GetServiceProxy("SVC1_1");
>
> proxy.PlusOne();   //Fires an error
>
> }
>
> error log:
>
> 2019 12:10:34 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): GridJobResultImp
>
> l [job=C2 [c=ServiceProxyCallable [mtdName=invokeMethod, svcName=SVC1_1,
> ignite=null]], sib=GridJobSiblingImpl [sesId=0cca3b46b61-2e1b3707-3
>
> a3a-4819-a903-3b58bb1db2c0,
> jobId=1cca3b46b61-2e1b3707-3a3a-4819-a903-3b58bb1db2c0,
> nodeId=27895328-1d37-4907-842b-fab79738dbc1, isJobDone=f
>
> alse], jobCtx=GridJobContextImpl
> [jobId=1cca3b46b61-2e1b3707-3a3a-4819-a903-3b58bb1db2c0, timeoutObj=null,
> attrs={}], node=TcpDiscoveryNode
>
> [id=27895328-1d37-4907-842b-fab79738dbc1, addrs=[0:0:0:0:0:0:0:1,
> 127.0.0.1, 172.19.91.29], sockAddrs=[DSP-RiskroomDev.bcsprime.local/172.19
>
> .91.29:48500, /0:0:0:0:0:0:0:1:48500, /127.0.0.1:48500], discPort=48500,
> order=1, intOrder=1, lastExchangeTime=1560762626538, loc=false, ver
>
> =2.7.0#20181130-sha1:256ae401, isClient=false], ex=class
> o.a.i.IgniteException: Service not found: SVC1_1, hasRes=true,
> isCancelled=false, i
>
> sOccupied=true]
>
> class org.apache.ignite.IgniteException: Remote job threw user exception
> (override or implement ComputeTask.result(..) method if you would l
>
> ike to have automatic failover for this exception): Service not found:
> SVC1_1
>
> at
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:102)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1053)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1046)
>
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6848)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1046)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:864)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1081)
>
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1316)
>
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
>
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
>
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
>
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
>
> 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.jav

Re: Need help with Linux ODBC Driver

[Igor Sapego]

Hi,

I'm not working on this issue currently and is not aware
if anyone else in the community looking at it.

But I think it's going to be fixed by 2.8 or 2.9 as it looks
quite important.

Best Regards,
Igor


On Fri, Jun 7, 2019 at 7:53 PM Charles Rene 
wrote:

> Hi Igor, When will this issue be addressed? Thanks, Charlie
>
> On Mon, May 13, 2019 at 9:55 AM Igor Sapego  wrote:
>
>> It seems like some encoding related issue to me.
>> Added a Jira ticket: [1].
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-11845
>>
>> Best Regards,
>> Igor
>>
>>
>> On Thu, May 2, 2019 at 1:15 AM Charles Rene 
>> wrote:
>>
>>> Hello,
>>>
>>> I'm having trouble using the Apache Ignite 2.7.0 Linux built ODBC
>>> driver. I'm running a .Net Core 2.2 console application in a Linux
>>> environment in Docker.
>>>
>>> The problem is that when I run a SELECT statement through .Net's
>>> System.Data.Odbc, I get back "bad data". It looks like a mismatch in
>>> encoding.
>>>
>>> The data looks like  "8\00\05\07\09\0d\09\08\0-\0" where as it should
>>> be "80579d98-9010-4610-b12e-ed33ed7d3c62".
>>>
>>> Details about my investigation can be found here:
>>>
>>> https://stackoverflow.com/questions/55875927/apache-ignite-2-7-odbc-linux-bad-data-returned
>>>
>>>
>>> Any idea what the problem might be?
>>>
>>> Thank you,
>>> Charlie
>>>
>>

Re: Connect external application to Ignite cluster via REST

[Denis Mekhanikov]

Kushan,

I would recommend using one of thin clients, since they have better
performance comparing to REST.
They work over a binary protocol, while REST needs data to be serialized as
strings.

Connectors for thin clients are enabled on all nodes by default, so you can
any one to connect.
Find more in the documentation:
https://apacheignite.readme.io/docs/thin-clients

Denis

пт, 14 июн. 2019 г. в 20:10, Kishan :

> We have ignite cluster up with four nodes. This cluster is hydrated with
> data
> into its cache. We want an external application to connect with cluster and
> get all the data objects of particular cache from the cluster via REST.
>
> I am thinking of following approaches:
> 1) Using ignite's service grid and deploy service into the grid, But I am
> not able to figure out a way to consume that service via REST call.
> 2) Someone suggested to bring up the service using ignite's compute task
> which can be invoked via REST call. The problem with approach is that the
> compute task won't return set of objects to REST client.
> 3) Bringing up the Jetty web server using service deployed on service
> grid(starting server in init method of service), and then make REST client
> to connect with that web server.
> 4) Using thin clients provided by ignite(Problem with this is that client
> will connect to only one cluster node, what if that node goes down)
> 5) Using REST APIs provided by ignite(As we want all the data objects of
> one
> cache, we are thinking of using REST APIs which executes SQL query and
> return output objects from cluster's cache)
>
> Which approach will work and which is the best one?
>
> Thanks in advance.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Stop JVM on network Segmenation

[tarunk]

Hi All,

Can anyone please help with below original query ?



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

.net service method call error

[Som Som]

hello.

I’m trying to deploy a service and call its method. Topology is one server
and one client.



Service:



[Serializable]

public class Service1 : IService, IPlusMinusService

{

[InstanceResource]

private readonly IIgnite _ignite;



private ICache _cache;



public void Init(IServiceContext context)

{

_cache = _ignite.GetCache("Test_Int_Int");

}



public void Execute(IServiceContext context)

{

//throw new NotImplementedException();

}



public void Cancel(IServiceContext context)

{

//throw new NotImplementedException();

}



public void PlusOne()

{

_cache.Put(1, _cache.Get(1) + 1);

}



public void MinusOne()

{

_cache.Put(1, _cache.Get(1) - 1);

}

}





Code:

 using (var ignite = Ignition.StartFromApplicationConfiguration())

{

var cache = ignite.GetOrCreateCache("Test_Int_Int"
);

cache.Put(1, 0);



var cacheGrp = ignite.GetCluster().ForCacheNodes(
"Test_Int_Int");

var services = cacheGrp.GetServices();

services.DeployNodeSingleton("SVC1_1",new Service1());



IPlusMinusService SVC1_1 = services.GetService(
"SVC1_1"); // Returns null

IPlusMinusService proxy =
services.GetServiceProxy("SVC1_1");

proxy.PlusOne();   //Fires an error

}

error log:

2019 12:10:34 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): GridJobResultImp

l [job=C2 [c=ServiceProxyCallable [mtdName=invokeMethod, svcName=SVC1_1,
ignite=null]], sib=GridJobSiblingImpl [sesId=0cca3b46b61-2e1b3707-3

a3a-4819-a903-3b58bb1db2c0,
jobId=1cca3b46b61-2e1b3707-3a3a-4819-a903-3b58bb1db2c0,
nodeId=27895328-1d37-4907-842b-fab79738dbc1, isJobDone=f

alse], jobCtx=GridJobContextImpl
[jobId=1cca3b46b61-2e1b3707-3a3a-4819-a903-3b58bb1db2c0, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode

[id=27895328-1d37-4907-842b-fab79738dbc1, addrs=[0:0:0:0:0:0:0:1,
127.0.0.1, 172.19.91.29], sockAddrs=[DSP-RiskroomDev.bcsprime.local/172.19

.91.29:48500, /0:0:0:0:0:0:0:1:48500, /127.0.0.1:48500], discPort=48500,
order=1, intOrder=1, lastExchangeTime=1560762626538, loc=false, ver

=2.7.0#20181130-sha1:256ae401, isClient=false], ex=class
o.a.i.IgniteException: Service not found: SVC1_1, hasRes=true,
isCancelled=false, i

sOccupied=true]

class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would l

ike to have automatic failover for this exception): Service not found:
SVC1_1

at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:102)

at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1053)

at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1046)

at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6848)

at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1046)

at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:864)

at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1081)

at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1316)

at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)

at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)

at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)

at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)

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: Service not found:
SVC1_1

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:568)

at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6816)

at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)

at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.jav

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

[Kamlesh Joshi]

Thanks Ilya, will give it a try !

Thanks and Regards,
Kamlesh Joshi

From: Ilya Kasnacheev 
Sent: Friday, June 14, 2019 8:40 PM
To: user@ignite.apache.org
Subject: Re: [External]Re: Is there any way to force recover the cluster - 
copying running cluster datastore


The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.
Hello!

Yes, I believe that's the correct dir. It contains checkpoint markers which you 
should remove.

Regards,
--
Ilya Kasnacheev


пт, 14 июн. 2019 г. в 17:30, Kamlesh Joshi 
mailto:kamlesh.jo...@ril.com>>:
Hi Ilya,

WAL markers you mean cp folder inside datastore ? or any other ?

Thanks and Regards,
Kamlesh Joshi

From: Ilya Kasnacheev 
mailto:ilya.kasnach...@gmail.com>>
Sent: Friday, June 14, 2019 6:59 PM
To: user@ignite.apache.org
Subject: Re: [External]Re: Is there any way to force recover the cluster - 
copying running cluster datastore


The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.
Hello!

If your node did not crash during a checkpoint, complerely removing WAL files 
and WAL markers should set you back to some stable state.

If it did crash during a checkpoint, you can't start with corrupted WAL.

Regards,
--
Ilya Kasnacheev


ср, 12 июн. 2019 г. в 17:37, Kamlesh Joshi 
mailto:kamlesh.jo...@ril.com>>:
Hi Denis,

Only WAL disk is corrupted but datastore is intact by any way can we restore 
the cluster ? some data loss is fine. Any suggestion on this?

Thanks and Regards,
Kamlesh Joshi

From: Kamlesh Joshi
Sent: Thursday, June 6, 2019 7:52 PM
To: user@ignite.apache.org
Subject: RE: [External]Re: Is there any way to force recover the cluster - 
copying running cluster datastore

Thanks for the update Denis.

If one of the WAL disk gets failed, is there any way to start or recover the 
cluster forcefully ?

Thanks and Regards,
Kamlesh Joshi

From: Denis Magda mailto:dma...@apache.org>>
Sent: Thursday, June 6, 2019 4:44 PM
To: user@ignite.apache.org
Subject: [External]Re: Is there any way to force recover the cluster - copying 
running cluster datastore


The e-mail below is from an external source. Please do not open attachments or 
click links from an unknown or suspicious origin.
I would discourage you from doing this if data consistency is prominent for 
you. What you see on the disk of one cluster node might be inconsistent with 
the whole cluster state and the actual/last updates in memory. Snapshots and 
backups can solve your task. Google for a solution provided by GridGain.

-
Denis


On Wed, Jun 5, 2019 at 8:27 AM Kamlesh Joshi 
mailto:kamlesh.jo...@ril.com>> wrote:
Hi Team,

We are trying to start another Ignite cluster by taking a copy 
of the running cluster’s datastore (source cluster’s datastore is getting 
modified in parallel). So, when we try to start the server node with copied 
datastore, it gives error as below. Also, giving cluster configuration for 
reference:

pageSize=#{4 * 1024}
walMode=LOG_ONLY
walFlushFrequency=6
rebalanceThreadPoolSize=8
rebalanceThrottle=100
rebalanceBatchSize=#{32 * 1024 * 1024}
storagePath=/datastore/datastore
walPath=/datastore1/wal
walArchivePath=/datastore1/archive
metadataWorkDir=/datastore/metadataWorkDir


[2019-06-05T12:21:52,943][INFO ][main][GridCacheDatabaseSharedManager] Read 
checkpoint status [startMarker=null, endMarker=null]
[2019-06-05T12:21:52,967][INFO ][main][PageMemoryImpl] Started page memory 
[memoryAllocated=128.0 MiB, pages=31744, tableSize=2.5 MiB, 
checkpointBuffer=100.0 MiB]
[2019-06-05T12:21:52,968][INFO ][main][GridCacheDatabaseSharedManager] Checking 
memory state [lastValidPos=FileWALPointer [idx=0, fileOff=0, len=0], 
lastMarked=FileWALPointer [idx=0, fileOff=0, len=0], 
lastCheckpointId=----]
[2019-06-05T12:21:52,973][ERROR][main][IgniteKernal%EDIFCustomer_DR] Exception 
during start processors, node will be stopped and close connections
org.apache.ignite.IgniteCheckedException: Failed to start processor: 
GridProcessorAdapter []
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1742) 
~[ignite-core-2.6.0.jar:2.6.0]
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980) 
[ignite-core-2.6.0.jar:2.6.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
 [ignite-core-2.6.0.jar:2.6.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
 [ignite-core-2.6.0.jar:2.6.0]
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151) 
[ignite-core-2.6.0.jar:2.6.0]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069) 
[ignite-core-2.6.0.jar:2.6.0]
at org.apache.ignite.internal.IgnitionEx.start(IgnitionE