Re: The system cache size was slowly increased
Hi Justin, If I am not wrong you have a data region of 3GiB and your ignite node heap size is 2GiB. Since data region was started with 512MB I am guessing your container slowly grew from 2.5Gib to where it is now. The problem in your case is both the off-heap and JVM heaps are different and ignite will grow to fill the off heap space when you put more data in off-heap memory. Regards, Prem > On 07-Sep-2018, at 8:25 AM, Justin Ji wrote: > > Who can give me some advice? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: zombie ignite node
Can you check topology in ignite visor console. If you can find the zombie node there you can kill using kill command in visor. Regards, Prem > On 07-Aug-2018, at 11:01 AM, arunkjn wrote: > > Him > > It only shows one process each time which is 'grep ignite' the one I am > running. It does not list any other ignite process. I have tried this before > as well. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Questions about how Ignite SQL Works
Don't know about the first question but if you have persistence enabled ignite will load the data on startup Regards, Prem On Mon, Jul 30, 2018, 1:00 PM Lijun Cao <641507...@qq.com> wrote: > Hi: > > I have referenced *How Ignite SQL Works *document but I still have got 2 > questions. > > The first question is, when I load data to Ignite cluster(3 nodes) in > first time, the data is stored both on RAM and disk(I enabled local > persistence), so which area does Ignite query on in this situation? > > The second question is, when I restart the cluster which I have mentioned > above, the data is still on disk, but not exists in the RAM, so how can I > load the data from disk to RAM in this situation? > > Look for your reply :-). >
Re: SQL to limit number of records per agId
Can you add a temporary rank column add rank for columns for every ageid starting from 1 till number of rows with that ageid then select where rank < configurable_num Regards, Prem On Thu, Jul 26, 2018, 11:05 PM Prasad Bhalerao wrote: > Hi Stephen > Thank you for the solution. > But it is limiting the no. Of record per agid to 1. > > I want to select 2 to 3 ( or some configurable no. Of records) record per > agid. > > Any idea how it can be done? > > > On Thu, Jul 26, 2018, 9:52 PM Stephen Darlington < > stephen.darling...@gridgain.com> wrote: > >> How about: >> >> 0: jdbc:ignite:thin://127.0.0.1/> select * from cache1; >> 'ID','AGID','VAL' >> '1','100','10-15' >> '2','100','17-20' >> '3','100','30-50' >> '4','101','10-15' >> '5','101','17-20' >> 5 rows selected (0.003 seconds) >> 0: jdbc:ignite:thin://127.0.0.1/> select * from cache1 where id in >> (select min(id) from cache1 group by agid); >> 'ID','AGID','VAL' >> '1','100','10-15' >> '4','101','10-15' >> 2 rows selected (0.004 seconds) >> 0: jdbc:ignite:thin://127.0.0.1/> >> >> Regards, >> Stephen >> >> On 26 Jul 2018, at 16:18, Prasad Bhalerao >> wrote: >> >> Hi, >> I have cache CAHE_1 and it has entries as follows. ID is the cache key >> and agID and Val are part the values. >> >> Now I want to query this cache to get the output as shown below(Sample >> output). >> In short I want to limit the number of rows per agId. I just want to >> fetch 1 to 3 rows per agId. >> >> Filter for this sql will be "agid in (100,101)". >> >> I understand that this is H2 Db related question but I did not find any >> working solution for this. >> Can some one please advise? >> >> >> Cache Entries >> ID | agId | Val >> --- >> 1 | 100 |10-15 >> 2 | 100 |17-20 >> 3 | 100 |30-50 >> 4 | 101 |10-15 >> 5 | 101 |17-20 >> >> Sample output: >> ID | Val | Val >> -- >> 1 | 100 | 10-15 >> 4 | 101 | 10-15 >> >> Thanks, >> Prasad >> >> >> >>
Re: Using SQL users to open jdbc connections
Thanks it worked, I missed the conversion to upper case without the quotes
Regards,
Prem
On Thu, Jul 26, 2018, 10:52 PM aealexsandrov
wrote:
> Hi,
>
> Could you please show the command how you create new users?
>
> When you create the user in quotes ("test") using SQL as next:
>
> CREATE USER "test" WITH PASSWORD 'test'
>
> It will be created as it was set (in this case it will be test)
>
> If you create the user without quotes (test) using SQL as next:
>
> CREATE USER test WITH PASSWORD 'test'
>
> then username will be stored in uppercase (TEST).
>
> BR,
> Andrei
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
