Re: 3rd party persistence: Mapping with RDBMS tables that don't have primary keys

2020-07-24 Thread Denis Magda
Hi Alex,


> I'm not going to write any new records or update existing ones for such
> tables through Ignite. So I can skip the overrides in CacheStore
> implementation, right? (I'm using default implementation at the moment)


That's right.

https://apacheignite.readme.io/docs/id-generator
> Thi may work. Can you point me to the example where Ignite config is in XML
> file


I don't have any XML example that shows how to create an AtomicSequence
bean. I tend to initialize it programmatically in code. Anyway, just create
it as a standard bean if it needs to be defined in the XML format.

-
Denis


On Wed, Jul 22, 2020 at 12:46 AM Alex Panchenko 
wrote:

> Hi Denis,
> thanks for your reply
>
> >>How will you access such records in Ignite? SQL lookups?
> Yes, using SQL lookups
>
> >>The default CacheStore implementation that writes down changes to a
> relational database needs to be overridden.
> I'm not going to write any new records or update existing ones for such
> tables through Ignite. So I can skip the overrides in CacheStore
> implementation, right? (I'm using default implementation at the moment)
>
> >>Obviously, Ignite still requires a primary key and that can be an integer
> number incremented by your application:
> https://apacheignite.readme.io/docs/id-generator
> Thi may work. Can you point me to the example where Ignite config is in XML
> file
>
> Also at the moment I'm using the following workaround. It seems like
> working, but I'm still testing it
>
> "keyType"="com.some.package.KeyValuesTableKey"
>
> KeyValuesTableKey {
> key: UUID
> value: String
> }
>
>
> Thank you
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Enabling swapPath causes invoking shutdown hook

2020-07-24 Thread 38797715

Hi,

https://apacheignite.readme.io/docs/swap-space

According to the above document, if the physical memory is small, you 
can solve this problem by opening the swap space,The specific method is 
to configure maxSize to a larger value (i.e. larger than the physical 
memory), and the swapPath property needs to be configured.


But from the test results, the node is terminated.

I think the correct result should be that even if the amount of data 
exceeds the physical memory, the node should still be able to run 
normally, but the data is exchanged to the disk.


I want to know what parameters affect the behavior of this 
configuration? *vm.swappiness* or others?


在 2020/7/24 下午9:55, aealexsandrov 写道:

Hi,

Can you please clarify your expectations? You expected that JVM process will
be killed instead of gracefully stopping? What you are going to achieve?

BR,
Andrei



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


Re: Are CPU Metrics logged by Ignite correct?

2020-07-24 Thread Raymond Wilson
We see the same things on Windows/Linux, Coretto v11, and in K8s
containers. Ignite 2.8.0

On Sat, Jul 25, 2020 at 7:44 AM Evgenii Zhuravlev 
wrote:

> Hi,
>
> What OS and java version do you use?
>
> Evgenii
>
> пт, 24 июл. 2020 г. в 12:32, Mat :
>
>> Ignite is logging "strange" CPU metrics for me:
>>
>> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
>> ^-- Node [id=c2a76580, name=embedded, uptime=00:01:00.153]
>> ^-- H/N/C [hosts=1, nodes=1, CPUs=12]
>> ^-- *CPU [cur=-100%, avg=-96.15%, GC=0%]*
>> ^-- PageMemory [pages=200]
>> ^-- Heap [used=337MB, free=95.84%, comm=508MB]
>> ^-- Off-heap [used=0MB, free=99.89%, comm=592MB]
>> ^--   DefaultDataRegion region [used=0MB, free=100%, comm=512MB]
>> ^--   sysMemPlc region [used=0MB, free=99.21%, comm=40MB]
>> ^--   TxLog region [used=0MB, free=100%, comm=40MB]
>> ^-- Outbound messages queue [size=0]
>> ^-- Public thread pool [active=0, idle=0, qSize=0]
>> ^-- System thread pool [active=0, idle=2, qSize=0]
>>
>>
>> I have tested 2.8.1, 2.8.0 and 2.7.0 as well as multiple environment and
>> bottom line CPU always show negative values that cannot be correlated with
>> the real cpu usage. Am I missing something?
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

-- 

Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wil...@trimble.com




Re: Are CPU Metrics logged by Ignite correct?

2020-07-24 Thread Evgenii Zhuravlev
Hi,

What OS and java version do you use?

Evgenii

пт, 24 июл. 2020 г. в 12:32, Mat :

> Ignite is logging "strange" CPU metrics for me:
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c2a76580, name=embedded, uptime=00:01:00.153]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=12]
> ^-- *CPU [cur=-100%, avg=-96.15%, GC=0%]*
> ^-- PageMemory [pages=200]
> ^-- Heap [used=337MB, free=95.84%, comm=508MB]
> ^-- Off-heap [used=0MB, free=99.89%, comm=592MB]
> ^--   DefaultDataRegion region [used=0MB, free=100%, comm=512MB]
> ^--   sysMemPlc region [used=0MB, free=99.21%, comm=40MB]
> ^--   TxLog region [used=0MB, free=100%, comm=40MB]
> ^-- Outbound messages queue [size=0]
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=2, qSize=0]
>
>
> I have tested 2.8.1, 2.8.0 and 2.7.0 as well as multiple environment and
> bottom line CPU always show negative values that cannot be correlated with
> the real cpu usage. Am I missing something?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Odd behavior/bug with DataRegion

2020-07-24 Thread Evgenii Zhuravlev
Hi,

There is a couple of known issues related to the small data region. I saw
this behavior before and you shouldn't see this issue for regions with
bigger sizes. Also, if you have really big objects, you might need to
change the emptyPagesPoolSize, to make sure that there are no objects
bigger than this value * 4k(default page size).

Best Regards,
Evgenii

чт, 23 июл. 2020 г. в 23:40, Victor :

> Update,
>
> Interestingly, i took the value to the wire, setting 'emptyPagesPoolSize'
> to
> 510 (< 512) and that seems to have done the trick. Atleast in my past 5
> test
> run's the preload has gone through fine.
>
> Right now i have set it to pretty much the max value, since there is no
> good
> way to identify what would be the runtime max value of an instance while
> creating a cache.
>
> Any other ideas around how to go about setting a safe value for this
> property.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Are CPU Metrics logged by Ignite correct?

2020-07-24 Thread Mat
Ignite is logging "strange" CPU metrics for me:

Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=c2a76580, name=embedded, uptime=00:01:00.153]
^-- H/N/C [hosts=1, nodes=1, CPUs=12]
^-- *CPU [cur=-100%, avg=-96.15%, GC=0%]*
^-- PageMemory [pages=200]
^-- Heap [used=337MB, free=95.84%, comm=508MB]
^-- Off-heap [used=0MB, free=99.89%, comm=592MB]
^--   DefaultDataRegion region [used=0MB, free=100%, comm=512MB]
^--   sysMemPlc region [used=0MB, free=99.21%, comm=40MB]
^--   TxLog region [used=0MB, free=100%, comm=40MB]
^-- Outbound messages queue [size=0]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=2, qSize=0]


I have tested 2.8.1, 2.8.0 and 2.7.0 as well as multiple environment and
bottom line CPU always show negative values that cannot be correlated with
the real cpu usage. Am I missing something?



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


[MEETUP] Apache Ignite Best Practices for Native Persistence and Data Recovery

2020-07-24 Thread Ivan Rakov
Hi,

Next Tuesday on meetup [1] I'll make a presentation about Ignite Native
Persistence.
I'll share insights how it works under the hood. Also I'll give some advice
on how to configure it and tune its performance.

TIME ZONES
5:30 AM Pacific Daylight Time
8:30 AM Eastern Daylight Time
1:30 PM British Summer Time
2:20 PM Central European Summer Time
3:30 PM Moscow Standard Time
6:00 PM India Standard Time
8:30 PM Singapore Time
8:30 PM China Standard Time

Please attend if you are interested.

[1]:
https://www.meetup.com/ru-RU/Apache-Ignite-Virtual-Meetup/events/271602652/


-- 
Best Regards,
Ivan Rakov


Re: Load balanced CQ listener/Catch up missed events

2020-07-24 Thread Devakumar J
Hi Denis, 

Thanks for the reply.

I mean to ask, is it possible to create distributed queue at client node and
if so where it will be persisted when native persistence enabled.

Should it be under server folder's work folder?

Thanks,
Devakumar J



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


Re: Load balanced CQ listener/Catch up missed events

2020-07-24 Thread Devakumar J
Any thoughts on this pls?



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


Re: apache-ignite compatibility with armhf(32-bit arm linux)

2020-07-24 Thread Stanislav Lukyanov
It should work fine. I ran Ignite on various platforms non-Intel platforms,
including arm. There were some issues in the past but modern versions work
well. But you do have to keep in mind that release testing for Ignite is
done on Intel platforms. Also arm can bring some surprises in terms of
performance.

I haven't tried the debian package myself. On one hand, it should work - I
believe there is no platform-dependent code in the package. On the other
hand, I believe debian packages are bound to CPU architecture, aren't they?
So it probably won't allow you to install it.

Stan



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


Re: Enabling swapPath causes invoking shutdown hook

2020-07-24 Thread aealexsandrov
Hi,

Can you please clarify your expectations? You expected that JVM process will
be killed instead of gracefully stopping? What you are going to achieve?

BR,
Andrei



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


Re: A question regarding cluster groups

2020-07-24 Thread aealexsandrov
Hi,

1)No, at the moment there is no such implementation out of the box. You
should create your own implementation of data moving tool.

2)At the moment there is no such implementation too. However, I see that
there is the discussion about it on developer user list:

http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Hot-cache-backup-td41034.html

BR,
Andrei



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


Re: Too much network latency issue

2020-07-24 Thread aealexsandrov
Hi,

I guess that some of your operations were slow because of load balancer
work. Two ways of affinity calculation exist:

1)If readFromBackup = false then the node with primary partition will be
chosen. Primary can be on different nodes.
2)If readFromBackup = true then the random node will be chosen because of a
load balancer.

Ignite doesn't have data center awareness functionality.

As a WA you can use computes that will be started on some required node.
This compute can use localPeek mode for cache operations:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#localPeek-K-org.apache.ignite.cache.CachePeekMode...-

For SQL you can use local queries:

https://apacheignite-sql.readme.io/docs/local-queries

BR,
Andei





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


Re: apache-ignite compatibility with armhf(32-bit arm linux)

2020-07-24 Thread Stephen Darlington
Not sure about the packages, but I do occasionally run Ignite on my Raspberry 
Pi. It’s running Raspian rather than Debian, but they’re pretty similar. It’s 
not fast (as you might imagine!) but it does work.

Regards,
Stephen

> On 23 Jul 2020, at 18:56, rakshita04  wrote:
> 
> I need to use apache-ignite for my armf(2-bit arm) linux application.
> Is apache-ignite compatible with 32-bit arm(armhf) linux?
> can i use apache-ignite debian package present on the website for armhf?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/




Re: third-party persistance and junction table

2020-07-24 Thread Bastien Durel
Hello,

OK, so I'll stick with my "dummy char(1) column as value" hack.

Thanks,

Le jeudi 23 juillet 2020 à 17:41 +0300, Andrei Aleksandrov a écrit :
> Hi,
> 
> Unfortunately, Ignite doesn't support such kind of relations out of
> the 
> box. Ignite just translates it to third party data storage that used
> as 
> cache-store.
> 
> It's expected that inserts and updates will be rejected in case if
> they 
> break some rules.
> 
> BR,
> Andrei
> 7/21/2020 11:16 AM, Bastien Durel пишет:
> > Hello,
> > 
> > I have a junction table in my model, and used the web console to
> > generate ignite config and classes from my SQL database
> > 
> > -> There is a table user with id (long) and some data
> > -> There is a table role with id (long) and some data
> > -> There is a table user_role with user_id (fk) and role_id (fk)
> > 
> > Reading cache from table works, I can query ignite with jdbc and I
> > get
> > my relations as expected.
> > 
> > But if I want to add a new relation, the query :
> > insert into "UserRoleCache".user_role(USER_ID, ROLE_ID)
> > values(6003, 2)
> > is translated into this one, sent to postgresql :
> > UPDATE public.user_role SET  WHERE (user_id=$1 AND role_id=$2)
> > 
> > Which obviously is rejected.
> > 
> > The web console generated a cache for this table, with UserRole
> > & UserRoleKey types, which each contains userId and roleId Long's.
> > 
> > Is there a better (correct) way to handle these many-to-many
> > relations
> > in ignite (backed by RDBMS) ?
> > 
> > Regards,
> > 
-- 
Bastien Durel
DATA
Intégration des données de l'entreprise,
Systèmes d'information décisionnels.

bastien.du...@data.fr
tel : +33 (0) 1 57 19 59 28
fax : +33 (0) 1 57 19 59 73
12 avenue Raspail, 94250 GENTILLY France
www.data.fr