You said you wanted 4 nodes in 1 process. Sorry, I'm not sure I understand
the question.
TcpDiscoveryMulticastIpFinder uses multicast, you don't need to specify
endpoints. Nodes will find each other in the same subnet, no matter if on
one machine or different ones.
However, it is not recommended for production use.
For proper setup, use TcpDiscoveryStaticIpFinder (same as
TcpDiscoveryVmIpFinder in Java)
DiscoverySpi = new TcpDiscoverySpi
{
IpFinder = new TcpDiscoveryStaticIpFinder
{
Endpoints = new[]
{
"machine1:47500..47505",
"machine2:47500..47505",
"machine3:47500..47505",
}
}
}
https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery
On Thu, Apr 6, 2023 at 7:39 PM <satyajit.man...@barclays.com> wrote:
> Hi Pavel,
>
>
>
> Below code snippet doesn’t mentions the IP address of 4
> different nodes( different machines) so how will this make the cache
> run in different node and form a cluster of 4 nodes.
>
>
>
> Do we need to start the thick client in all nodes one by one
> with the same server cfg and add this in server cfg. .
>
>
>
> DiscoverySpi = new TcpDiscoverySpi
>
> {
>
> IpFinder = new TcpDiscoveryMulticastIpFinder
>
> {
>
> Endpoints = new[]
>
> {
>
> "xxx.0.0.xxx:47500..47502",
>
> "yyy.0.0.yyyy:47500..47502",
>
> "zzz.0.0.zzzz:47500..47502"
>
>
>
> }
>
> }
>
> },
>
>
>
> Regards
>
> Satyajit
>
>
>
>
>
>
>
> *From:* Pavel Tupitsyn <ptupit...@apache.org>
> *Sent:* Thursday, April 6, 2023 9:51 PM
> *To:* Mandal, Satyajit: IT (PUN) <satyajit.man...@barclays.com>
> *Cc:* user@ignite.apache.org
> *Subject:* Re: Ignite configuration using .NET Thick client
>
>
>
> CAUTION: This email originated from outside our organisation -
> ptupit...@apache.org Do not click on links, open attachments, or respond
> unless you recognize the sender and can validate the content is safe.
>
> using Apache.Ignite.Core;
> using Apache.Ignite.Core.Deployment;
> using Apache.Ignite.Core.Log;
>
> var serverCfg = new IgniteConfiguration
> {
> Localhost = "127.0.0.1",
> JvmOptions = new[]
> {
> "-DIGNITE_QUIET=true",
> "-DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true"
> },
> Logger = new ConsoleLogger
> {
> MinLevel = LogLevel.
> *Error *},
> PeerAssemblyLoadingMode = PeerAssemblyLoadingMode.*CurrentAppDomain*,
> AutoGenerateIgniteInstanceName = true
> };
>
> var clientCfg = new IgniteConfiguration(serverCfg)
> {
> ClientMode = true
> *// Thick client. *};
>
>
> *// Start 3 server nodes. *var servers = Enumerable.*Range*(1, 3).Select(_
> => Ignition.*Start*(serverCfg)).ToList();
>
>
> *// Start a thick client node. *var client = Ignition.*Start*(clientCfg);
>
> Console.*WriteLine*("Total nodes: " + client.GetCluster().GetNodes().Count
> );
>
>
>
> On Thu, Apr 6, 2023 at 5:39 PM <satyajit.man...@barclays.com> wrote:
>
> Hi Pavel,
>
>
>
> I need to start cache in 4 different nodes using .NET Thick
> client in one process. Can you share me the sample Ignite
> Configuration and steps to do that.
>
>
>
> Previously I was using thin client and that time I used to
> start Ignite nodes using Spring.xml one by one in each node.
>
>
>
> Regards
>
> Satyajit
>
>
>
> *From:* Pavel Tupitsyn <ptupit...@apache.org>
> *Sent:* Thursday, April 6, 2023 7:57 PM
> *To:* user@ignite.apache.org; Mandal, Satyajit: IT (PUN) <
> satyajit.man...@barclays.com>
> *Subject:* Re: Ignite configuration using .NET Thick client
>
>
>
> CAUTION: This email originated from outside our organisation -
> ptupit...@apache.org Do not click on links, open attachments, or respond
> unless you recognize the sender and can validate the content is safe.
>
> Hi Satyajit,
>
>
>
> 1. You don't need to use Spring XML unless you have to set a property that
> is not exposed in .NET API
>
> 2. Do you want to start 4 nodes in one process? Or multiple processes on
> the same machine? What's your desired setup?
>
>
>
> Pavel
>
>
>
> On Thu, Apr 6, 2023 at 4:40 PM satyajit.mandal.barclays.com
> <https://clicktime.symantec.com/15sLvSJyuA6fEjRJ369u2?h=LSypiaGaE8p6-HR8_7rXGT-aHM5RsH9EHUzLHQuAzSc=&u=http://satyajit.mandal.barclays.com>
> via user <user@ignite.apache.org> wrote:
>
> Hi Pavel,
>
>
>
> Need to understand one thing from you. Am using .NET thick
> client. What’s the best way to put the Ignite configuration . Should
> this be put on code or in spring xml. If we put on code and
> lets say I need 4 nodes as part of cluster then do I need to
> start this service in all 4 nodes and put those 4 ip address in
> code ? Don’t want to use spring.xml.
>
>
>
> return new IgniteConfiguration
>
> {
>
> Localhost = "127.0.0.1",
>
> DiscoverySpi = new TcpDiscoverySpi
>
> {
>
> IpFinder = new TcpDiscoveryMulticastIpFinder
>
> {
>
> Endpoints = new[]
>
> {
>
> "127.0.0.1:47500..47502"
>
> }
>
> }
>
> },
>
> JvmOptions = new[]
>
> {
>
> "-DIGNITE_QUIET=true",
>
> "-DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true"
>
> },
>
> Logger = new ConsoleLogger
>
> {
>
> MinLevel = LogLevel.Error
>
> },
>
> PeerAssemblyLoadingMode =
> PeerAssemblyLoadingMode.CurrentAppDomain
>
> };
>
> }
>
>
>
>
>
> Regards
>
> Satyajit
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
