date:20230413

Re: Ignite configuration using .NET Thick client

2023-04-13 Thread Pavel Tupitsyn

I don't see any issue with this setup. It is a perfectly valid use case.

Make sure to check this doc regarding IIS:
https://ignite.apache.org/docs/latest/net-specific/net-deployment-options#iis-application-pool-lifecycle-appdomains-and-ignite-net

On Thu, Apr 13, 2023 at 3:15 PM satyajit.mandal.barclays.com via user <
user@ignite.apache.org> wrote:

> Hi  Pavel,
>
>
>
> Thanks for  below  information.  One  clarification  needed  from  your
> side . Am  want  to  run  .net WebApi  in three different machines and  it
> will  start  ignite as  server  node and do  cache  operations  ( CRUD
> operations )  using  controller exposed. These webapi’s  will  be  hosted
> in  IIS.  So a  cluster  with  three server  nodes  will  form  and  it
> will  serve  cache  operations.  Do  you  see  any  issue  with  this
> setup?Load  balancing  will be  done  using  .NET frameworks like Dapr etc..
>
>
>
>
>
> Regards
>
> Satyajit
>
>
>
>
>
> *From:* Pavel Tupitsyn 
> *Sent:* Friday, April 7, 2023 10:17 AM
> *To:* Mandal, Satyajit: IT (PUN) 
> *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.
>
> 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  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.:47500..47502",
>
>"zzz.0.0.:47500..47502"
>
>
>
> }
>
> }
>
> },
>
>
>
> Regards
>
> Satyajit
>
>
>
>
>
>
>
> *From:* Pavel Tupitsyn 
> *Sent:* Thursday, April 6, 2023 9:51 PM
> *To:* Mandal, Satyajit: IT (PUN) 
> *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  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

RE: Ignite configuration using .NET Thick client

2023-04-13 Thread satyajit.mandal.barclays.com via user

Hi  Pavel,

Thanks for  below  information.  One  clarification  needed  from  your  side . 
Am  want  to  run  .net WebApi  in three different machines and  it  will  
start  ignite as  server  node and do  cache  operations  ( CRUD operations )  
using  controller exposed. These webapi’s  will  be  hosted  in  IIS.  So a  
cluster  with  three server  nodes  will  form  and  it  will  serve  cache  
operations.  Do  you  see  any  issue  with  this  setup?Load  balancing  will 
be  done  using  .NET frameworks like Dapr etc..


Regards
Satyajit


From: Pavel Tupitsyn 
Sent: Friday, April 7, 2023 10:17 AM
To: Mandal, Satyajit: IT (PUN) 
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.
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 
mailto: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.:47500..47502",
   "zzz.0.0.:47500..47502"

}
}
},

Regards
Satyajit



From: Pavel Tupitsyn mailto:ptupit...@apache.org>>
Sent: Thursday, April 6, 2023 9:51 PM
To: Mandal, Satyajit: IT (PUN) 
mailto: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 
mailto: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 mailto:ptupit...@apache.org>>
Sent: Thursday, April 6, 2023 7:57 PM
To: user@ignite.apache.org; Mandal, Satyajit: IT 
(PUN) mailto: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

Re: Spring (Boot) version

2023-04-13 Thread f cad

we used with springboot 2.6.7. it works fine

Humphrey Lopez  于2023年4月7日周五 14:47写道：

> Currently we are running Ignite with spring boot 2.x version. Is any
> version of Spring (Boot) supported? Can we for example want to upgrade to
> spring boot 3.x ?
>
> Humphrey
>

Re: Ignite configuration using .NET Thick client

RE: Ignite configuration using .NET Thick client

Re: Spring (Boot) version

3 matches

Site Navigation

Mail list logo

Footer information