Unsubscribe

2021-07-12 Thread Martin 



| |
Martin
|
|
邮箱：ghx02...@126.com
|

签名由 网易邮箱大师 定制

Apache Ignite DataRegion Swap

2021-03-12 Thread Martin Lund Askøe 
Hi

If I have an ignite node running on a machine with 16GB of physical memory
and I want to create a data-region that may hold 5GB of data but only
consume 1GB of memory on the off-heap, then how do I configure my cluster
node to use swap when exceeding 1GB off-heap memory?

I'm trying to get my head around this example from GridGain https://www.gridgain.com/docs/latest/developers-guide/persistence/swap;>
https://www.gridgain.com/docs/latest/developers-guide/persistence/swap

Where is the 500MB specified (besides in the name)?
It seems to me that the size of the data-region is set to 5GB and not 500MB?

Re:Ignite .NET - Delete statement

2017-12-12 Thread Martin 


I am using java driver, and also i am seeing this problem. if delete statement 
delete only one row data, there is no errors. and if the delete statement 
delete multi-row data, the below exception occurs.
cloud you please take a look at this ASAP?




thanks,
Martin





At 2017-12-04 17:38:00, "jerpic" <jerome.pic...@misterfly.com> wrote:
Hello, I try to delete some records according to the DELETE statement (see 
below). Unfortunately, I got every time an exception (see the attached file). 
Exception.txt Do you have an idea about the origin of this issue ? Here is the 
code :
 public void deleteOneWayProposals(string _route, DateTime _searchDate, string 
_provider)
{
try
{
var query = buildSqlDeleteOneWayProposals(_route, _searchDate, 
_provider);

Console.WriteLine("QUERY : " + query);

var res = cacheOneWayProposals.QueryFields(query);

  
} catch (Exception exp)
{
Console.WriteLine(exp.Message);
}
}

 private SqlFieldsQuery buildSqlDeleteOneWayProposals(string _route, DateTime 
_searchDate, string _provider)
{

string delete = "DELETE " +
"FROM \"" + ONEWAY_PROPOSALS_CACHE + "\".ONEWAYPROPOSAL as 
ONEWAY " +
"WHERE " +
"ONEWAY.ROUTE = ? " +
"AND " +
"ONEWAY.SEARCHDEPARTUREDATE = PARSEDATETIME 
(?,'-MM-dd') " +
"AND " +
"ONEWAY.PROVIDER = ? ";


var fieldsQuery = new SqlFieldsQuery(delete);
fieldsQuery.EnableDistributedJoins = true;

fieldsQuery.Arguments = new Object[] { _route, 
_searchDate.ToString("-MM-dd"), _provider};

if (log.IsDebugEnabled)
{
log.Debug("QUERY = " + fieldsQuery.ToString());
}

return fieldsQuery;
}
Regards, Jérôme.

Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re:Re: About the xml configuration

2017-07-25 Thread Martin 

Thanks for your support, thanks very much




At 2017-07-25 07:32:10, "vkulichenko" <valentin.kuliche...@gmail.com> wrote:
>Hi Martin,
>
>1. Generally yes, I would recommend to use the same configuration. Even if
>you do otherwise, you need to make sure that discovery configuration is
>correct everywhere.
>1.1. Classes that are part of configuration like cache store implementation,
>must be explicitly deployed on all nodes including clients. Peer class
>loading works only with Compute Grid to deploy closures and remote jobs.
>1.2. This is probably caused by misconfiguration. Make the configuration
>consistent on all nodes first, and the check if issue persists or not.
>2. See 1.1. Cache store can be invoked on client for transactional caches.
>For atomic caches this is not the case, but validity checks are the same, so
>you still have to deploy classes.
>
>-Val
>
>
>
>--
>View this message in context: 
>http://apache-ignite-users.70518.x6.nabble.com/About-the-xml-configuration-tp15269p15524.html
>Sent from the Apache Ignite Users mailing list archive at Nabble.com.

About the xml configuration

2017-07-21 Thread Martin 
(AspectJAfterThrowingAdvice.java:62)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673)
at 
com.cootf.cloudsim.oms.ignite.api.impl.SimPoolServiceImpl$$EnhancerBySpringCGLIB$$8481f95f.enabledTheSimpool()
at 
com.cootf.cloudsim.oms.ignite.test.SimPoolApiTest.enableOrDisableSimPool(SimPoolApiTest.java:175)
at 
com.cootf.cloudsim.oms.ignite.test.SimPoolApiTest.Should_Be_Able_To_Enable_The_Simpool(SimPoolApiTest.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at 
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at 
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at 
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)


Thanks,
Martin

Re:Re: encountering a character encoding problem when DML SQL is used

2017-07-19 Thread Martin 



I called it from Java, and i am using Ignite 2.0.
seems many chinese developer are encountering this problem. 
is there any configuration that can set as encoding? or is there any API method 
can do this?






thanks,
Martin







At 2017-07-20 00:34:45, "afedotov" <alexander.fedot...@gmail.com> wrote:

Hi Martin,

I've checked the same with 2.0 and it works on my side.

Which version of Ignite do you use?
Do you call it from Java, .NET or C++ ?
Please check that source files encoding is consistent. It's better to stick 
with UTF-8.


Kind regards,
Alex.


On Wed, Jul 19, 2017 at 4:47 AM, Martin [via Apache Ignite Users] <[hidden 
email]> wrote:

Hi guys,


I am now encountering a character encoding problem when DML SQL is used.
For example, if i run the DML SQL like the following sentence:
 update tableA set columnA="测试" and columnB="你好" where _key=1
it can works, but when i get it(_key=1) from the cache , i get the messy word. 


any ideas about this? is there any way to set character encoding?




thanks for your help






Thanks,
Martin






 




If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/encountering-a-character-encoding-problem-when-DML-SQL-is-used-tp15094.html
To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML




View this message in context: Re: encountering a character encoding problem 
when DML SQL is used
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

encountering a character encoding problem when DML SQL is used

2017-07-18 Thread Martin 
Hi guys,


I am now encountering a character encoding problem when DML SQL is used.
For example, if i run the DML SQL like the following sentence:
 update tableA set columnA="测试" and columnB="你好" where _key=1
it can works, but when i get it(_key=1) from the cache , i get the messy word. 


any ideas about this? is there any way to set character encoding?




thanks for your help






Thanks,
Martin