why the records not zero after execute "cache -clear"

[huzx]

Hello everybody,


   I'm just using ignite(data grid). In my use case, After "cache -clear" I
found the count of the cache not consistent with the real count of record in
IgniteCache, my operation is as follows:
   1. I create the cache by transaction mode (backup 3),  persist mode by
SSD
   2. Using spark IgniteContext to put about 1000w record (has two fields
both are string)
   key: string
   value: string
   3. when all the data have put to the cache, then I use sqlline, execute
"select count(*) from recordCache", then I get the record is 1000w
   4. then I use visorcmd connect to the grid, and do "cache -clear ", to
clear all the records of cache, when the count is zero, I use sqlline to
check the count, and the result is as expected.
   5.  I stop all the Ignite server node, when all the node has started, I
use visorcmd to check the count of the cache, I found the count is not
zero!


   questions:
   1. how "cache -clear" works? is this operation only clear cache in
memory or can clear records both in the disk and in memory?
2. In persist mode, how does ignite do persist? will ignite persist
all data to disk or ignite persist partial data to disk, partial data to
memory?
3. when ignite node has gone, how rebalance will be executed? will
all the data in the gone node all be rebalanced? 

   thanks for your reply!



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

Apache Ignite Web Consol Monitor

[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: Cache clear through IgniteVisor console

[Nikolai Tikhonov]

Hello,

Can you share thread dumps from all nodes. You can take them by jstack tool.

On Fri, Dec 8, 2017 at 3:04 PM, Naveen  wrote:

> Hi
>
> I am using Ignite 2.3, trying to clear the cache, issued clear commands for
> the space which has 10M, dont anything happening, neither clearing the
> cache
> nor came out, it was in hung state.
>
> This is the command I issued
>
> cache -clear -c=Customer
>
> What could have gone wrong.
>
> Thanks
> naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Redis problem with values > 8kb

[Alexey Popov]

Hi Wolfram,

I reproduced the issue at my env and created a ticket
https://issues.apache.org/jira/browse/IGNITE-7153.
Unfortunately, I did not find any workaround with Redis client you use.

Thank you,
Alexey




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

Re: Enabling REST api for a apache client node

[slava.koptilin]

Hi Naveen,

Yes, you can use Apache Ignite in that way.
Additional information about Clients/Servers is available here:
https://apacheignite.readme.io/docs/clients-vs-servers

Thanks!



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

Cache clear through IgniteVisor console

[Naveen]

Hi

I am using Ignite 2.3, trying to clear the cache, issued clear commands for
the space which has 10M, dont anything happening, neither clearing the cache
nor came out, it was in hung state.

This is the command I issued

cache -clear -c=Customer

What could have gone wrong.

Thanks
naveen



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

Re: ODBC insert of decimal value throws an exception

[Igor Sapego]

Hi,

Do you still observe the issue? I've created a ticket for it - [1].
It would still help if you provide a brief code snippet of how you are
passing
decimal number to Ignite.

[1] - https://issues.apache.org/jira/browse/IGNITE-7143

Best Regards,
Igor

On Tue, Nov 21, 2017 at 3:50 PM, Kenn Thompson 
wrote:

> You bet, thanks for looking.
>
>
>
> [06:48:40] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8,
> heap=1.0GB]
>
> [06:49:18,662][SEVERE][client-connector-#52][ClientListenerNioListener]
> Failed to parse client request.
>
> java.lang.ArrayIndexOutOfBoundsException: 0
>
> at org.apache.ignite.internal.binary.BinaryUtils.
> doReadDecimal(BinaryUtils.java:1277)
>
> at org.apache.ignite.internal.processors.odbc.
> SqlListenerUtils.readObject(SqlListenerUtils.java:78)
>
> at org.apache.ignite.internal.processors.odbc.odbc.
> OdbcMessageParser.readParameterRow(OdbcMessageParser.java:185)
>
> at org.apache.ignite.internal.processors.odbc.odbc.
> OdbcMessageParser.decode(OdbcMessageParser.java:97)
>
> at org.apache.ignite.internal.processors.odbc.
> ClientListenerNioListener.onMessage(ClientListenerNioListener.java:115)
>
> at org.apache.ignite.internal.processors.odbc.
> ClientListenerNioListener.onMessage(ClientListenerNioListener.java:39)
>
> at org.apache.ignite.internal.util.nio.GridNioFilterChain$
> TailFilter.onMessageReceived(GridNioFilterChain.java:279)
>
> at org.apache.ignite.internal.util.nio.GridNioFilterAdapter.
> proceedMessageReceived(GridNioFilterAdapter.java:109)
>
> at org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.
> body(GridNioAsyncNotifyFilter.java:97)
>
> at org.apache.ignite.internal.util.worker.GridWorker.run(
> GridWorker.java:110)
>
>at org.apache.ignite.internal.util.worker.GridWorkerPool$1.
> run(GridWorkerPool.java:70)
>
> 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)
>
>
>
>
>
>
> * Kenn Thompson  |  Solutions Architect, QAT Global*
> *402.478.8818 (mobile) | *402.391.9200 x1021
>
>
>
> *From:* Igor Sapego [mailto:isap...@apache.org]
> *Sent:* Tuesday, November 21, 2017 2:21 AM
> *To:* user 
> *Subject:* Re: ODBC insert of decimal value throws an exception
>
>
>
> Hi, can you provide full stack trace for the error?
>
>
> Best Regards,
>
> Igor
>
>
>
> On Tue, Nov 21, 2017 at 12:41 AM, kenn_thomp...@qat.com <
> kenn_thomp...@qat.com> wrote:
>
> I have a table defined as such and created via passing to an ODBC
> Connection:
>
> CREATE TABLE IF NOT EXISTS TestTable (RecId varchar PRIMARY KEY, RecValue
> DECIMAL(4,2))
> WITH "template=replicated, cache_name=TestTable_Cache";
>
> I then do an ODBC insert:
>
> INSERT INTO TestTable (RecId, RecValue) VALUES ('1', ?)
> (using the OdbcParameter with the OdbcCommand object)
>
> The Odbc error is "The connection has been disabled." however the JVM is
> throwing this error:
> [SEVERE][client-connector-#47][ClientListenerNioListener] Failed to parse
> client request.
> java.lang.ArrayIndexOutOfBoundsException: 0
>  at org.apache.ignite.internal.binary.BinaryUtils.doReadDecimal
>
> Everything works out ok until the actual value set on the parameter is 0.
> Null works fine, values other than 0 work fine. I've verified Precision and
> Scale are set appropriately. I've also tried an insert with actual values
> instead of using the Parameters collection, but that seems to work as well.
>
> Thoughts?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

Re: Affinity - Join query on the collocated data taking 90 seconds

[Nikolai Tikhonov]

Can you share your configuration and model? It would be great if you can
provide simple maven project on Github.

On Thu, Dec 7, 2017 at 10:10 PM, Naveen  wrote:

> I have created an index on partyId of Account cache, after that query is
> responding in milli seconds.
>
> However, my basic affinity and collation does not seems to be working.
>
> I have created records with Ids from P10100 to P10101.
> If you see below, some of the records are not  returned, does that means
> they are not collacated.
>
> 0: jdbc:ignite:thin://127.0.0.1> select P.PARTY_ID, A.PARTY_ID,
> P.ACCOUNT_ID_LIST from "Customer".Customer P, "Account".Account  A where
> P.PARTY_ID='P10116' and P.PARTY_ID= A.PARTY_ID;
> ++--
> --++
> |PARTY_ID|PARTY_ID|
> ACCOUNT_ID_LIST |
> ++--
> --++
> ++--
> --++
> No rows selected (0.01 seconds)
> 0: jdbc:ignite:thin://127.0.0.1> select P.PARTY_ID, A.PARTY_ID,
> P.ACCOUNT_ID_LIST from "Customer".Customer P, "Account".Account  A where
> P.PARTY_ID='P10123' and P.PARTY_ID= A.PARTY_ID;
> ++--
> --++
> |PARTY_ID|PARTY_ID|
> ACCOUNT_ID_LIST |
> ++--
> --++
> | P10123 | P10123 |
> A10123 |
> ++--
> --++
> 1 row selected (0.011 seconds)
> 0: jdbc:ignite:thin://127.0.0.1> select P.PARTY_ID, A.PARTY_ID,
> P.ACCOUNT_ID_LIST from "Customer".Customer P, "Account".Account  A where
> P.PARTY_ID='P10124' and P.PARTY_ID= A.PARTY_ID;
> ++--
> --++
> |PARTY_ID|PARTY_ID|
> ACCOUNT_ID_LIST |
> ++--
> --++
> ++--
> --++
> No rows selected (0.022 seconds)
>
> What could be the reason
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>