Hi, Please point to some reference on the below questions.
Thanks & Regards, Sriveena From: Sriveena Mattaparthi Sent: Friday, August 31, 2018 4:24 PM To: user@ignite.apache.org Subject: RE: Example for server client configuration in ignite Hi Evgenii, In the document mentioned on Result Set Lazy Load, if result set is too big to fit in the available memory, then it can lead to prolonged GC pauses and even OutOfMemoryError. 1. Is it referring to the on heap memory of the client application or the off heap memory? 2. Is it referring to prolonged GC of client application and how? Thanks & Regards, Sriveena From: Evgenii Zhuravlev [mailto:e.zhuravlev...@gmail.com] Sent: Wednesday, August 29, 2018 2:03 PM To: user@ignite.apache.org Subject: Re: Example for server client configuration in ignite Join performed on the server nodes where data placed. To reduce the overall size of the reduce set on the client you can use lazy flag for result set: https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-result-set-lazy-load<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheignite-sql.readme.io%2Fdocs%2Fperformance-and-debugging%23section-result-set-lazy-load&data=02%7C01%7CSriveena.Mattaparthi%40ekaplus.com%7C4e5e1807d5f84dc0076008d60d8a2493%7C2a5b4e9716be4be4b2d40f3fcb3d373c%7C1%7C0%7C636711284345864800&sdata=8DmrZhMEkuqhh1d6BDjGOBoYtRYJjCXo04YlBMeZTVg%3D&reserved=0> Evgenii пн, 27 авг. 2018 г. в 19:44, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Thanks Evgenii.. Now the question is code for client ignite start is deployed in an application server. Any data join performed on the client node cache is utilizing jvm heap memory assigned to the application resulting in outofmemory on the application server. Is there a way to limit the client node memory utilization of application server heap memory or run client node on separate ibn? Please note that persistence is enabled on the ignite configuration. ________________________________ From: Evgenii Zhuravlev <e.zhuravlev...@gmail.com<mailto:e.zhuravlev...@gmail.com>> Sent: 27 August 2018 21:41:41 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Example for server client configuration in ignite Yes, you start client node, not a server. I'd recommend you to read about differences between client and server nodes: https://apacheignite.readme.io/docs/clients-vs-servers<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheignite.readme.io%2Fdocs%2Fclients-vs-servers&data=02%7C01%7CSriveena.Mattaparthi%40ekaplus.com%7C646c52d9b3064b05272f08d60c37ce47%7C2a5b4e9716be4be4b2d40f3fcb3d373c%7C1%7C0%7C636709831174713298&sdata=DOLZ7OkBxVhNOpcb0la%2F3lmFeifM8ptU%2B0R5iXFajOc%3D&reserved=0> 2018-08-27 19:06 GMT+03:00 Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Thanks Evgenii.. To reframe my question ..server is started on a separate host...client node is setup using java connecting to remote server as mentioned in the below mail... Does invoking ignition.start on client node means starting ignite once more? Thanks & Regards, Sriveena ________________________________ From: Evgenii Zhuravlev <e.zhuravlev...@gmail.com<mailto:e.zhuravlev...@gmail.com>> Sent: 27 August 2018 19:54:16 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Example for server client configuration in ignite >1.Do we have to start Ignite again on client node as Ignition.start(cfg)? What >does this imply? Sorry, I didn't get it, what do you mean by "start again"? >2.Will the client node uses the JVM heap memory Ignite runs inside JVM, so yes, it will use JVM heap. Could you specify your question? Evgenii пн, 27 авг. 2018 г. в 14:36, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Thanks Evgenii Started remote server, using the default configuration given as part of the ignite disctribution using $ bin\ignite.bat examples\config\example-ignite.xml And client node started in java as pointed below using Ignition.setClientMode(true); TcpDiscoverySpi spi = new TcpDiscoverySpi(); TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(); ipFinder.setAddresses(Arrays.asList("1.2.3.4", "1.2.3.5:47500..47509")); spi.setIpFinder(ipFinder); IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setDiscoverySpi(spi); // Start Ignite node. Ignition.start(cfg); My question is 1.Do we have to start Ignite again on client node as Ignition.start(cfg)? What does this imply? 2.Will the client node uses the JVM heap memory Thanks & Regards, Sriveena From: Evgenii Zhuravlev [mailto:e.zhuravlev...@gmail.com<mailto:e.zhuravlev...@gmail.com>] Sent: Monday, August 27, 2018 4:52 PM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Example for server client configuration in ignite Hi, The default configuration will work with the remote server, because it uses multicast. It will work if you want to check some examples, etc. For production usage, I'd recommend using static Ip Finder instead of multicast, here is the simplest configuration that will work with remote server: https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheignite.readme.io%2Fdocs%2Ftcpip-discovery%23section-static-ip-finder&data=02%7C01%7CSriveena.Mattaparthi%40ekaplus.com%7Cdf036d2b84054674a91608d60c0f4ee2%7C2a5b4e9716be4be4b2d40f3fcb3d373c%7C1%7C0%7C636709657237020433&sdata=0H8nUrwx%2BmNG4bRr9v150MRZTLdwdxS4G2j4cJ5waYU%3D&reserved=0> There you will need just to replace address in IpFinder with the address of your remote server. You don't need to place client address there. Yo start client instead of the server node, you have to add clientMode=true property in this configuration. Evgenii пн, 27 авг. 2018 г. в 13:47, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Hi, What is the recommended configuration for remote Server and one client node setup? Can someone point to the relevant examples? Thanks & Regards, Sriveena “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.” “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.” “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.”
