C# client not able to connect to cluster using IP address
Hi team,
I have started an ignite server with the below command on my local machine
ignite.bat C:\..\\..\config\Ignite-config.xml
My config looks like
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
MyHostName:47500..47502
I am running the client code as follows
Running client code as follows
class Program
{
public static IIgniteClient IgniteThinClient;
private static IgniteClientConfiguration
GetIgniteClientConfiguration()
{
return new IgniteClientConfiguration
{
Host = "MyHostName",
Port = 47500
};
}
static void Main(string[] args)
{
try
{
Ignition.ClientMode = true;
IgniteThinClient =
Ignition.StartClient(GetIgniteClientConfiguration());
}
catch(Exception ex)
{
//Log Ex
}
}
}
I cannot see my client connected and instead see the following logs
>>> VM name: 195616@MyHostName
>>> Local node [ID=5032DC52-0036-3BDF5136903, order=1, clientMode=false]
>>> Local node addresses: [MyHostName/0:0:0:0:0:0:0:1, /127.0.0.1,
>>> /10.10.17.82]
>>> Local ports: TCP:10800 TCP:11211 TCP:47500 TCP:48100
[20:29:43,699][INFO][main][GridDiscoveryManager] Topology snapshot [ver=1,
locNode=5032dc52, servers=1, clients=0, state=ACTIVE, CPUs=8, offheap=3.2GB,
heap=1.0GB]
[20:30:00,233][INFO][tcp-disco-srvr-#3][TcpDiscoverySpi] TCP discovery
accepted incoming connection [rmtAddr=/10.10.17.82, rmtPort=60732]
[20:30:00,243][INFO][tcp-disco-srvr-#3][TcpDiscoverySpi] TCP discovery
spawning a new thread for connection [rmtAddr=/10.10.17.82, rmtPort=60732]
[20:30:00,244][INFO][tcp-disco-sock-reader-#4][TcpDiscoverySpi] Started
serving remote node connection [rmtAddr=/10.10.17.82:60732, rmtPort=60732]
[20:30:00,245][WARNING][tcp-disco-sock-reader-#4][TcpDiscoverySpi] Unknown
connection detected (is some other software connecting to this Ignite port?
missing SSL configuration on remote node?) [rmtAddr=/10.10.17.82]
[20:30:00,245][INFO][tcp-disco-sock-reader-#4][TcpDiscoverySpi] Finished
serving remote node connection [rmtAddr=/10.10.17.82:60732, rmtPort=60732
If instead I replace MyHostName with localhost, i see the client getting
connected on the server. Can you help me out with the issue ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Service grid webinar
Prasad, Sorry, I’ve only noticed your message just now. You can find the recording of the webinar on YouTube: https://www.youtube.com/watch?v=MZzkkIHGMtI Denis On 7 Nov 2019, 21:05 +0300, Prasad Bhalerao , wrote: > Can you please share the recording of webinar in case if you have it? > > > On Wed 6 Nov, 2019, 3:30 AM Denis Mekhanikov > > Hi Igniters! > > > > > > I’ve been working on the Service Grid functionality in Apache Ignite for > > > a while, and at some point I've decided to make a webinar with a > > > high-level overview of this part of the project. > > > > > > If you want to learn more about services, look at some use-cases or just > > > ask a few questions somebody who takes part in the development, please > > > feel free to join the presentation on November 6th, at 10 AM PST. > > > > > > You can sign up by the following link: > > > https://www.gridgain.com/resources/webinars/best-practices-microservices-architecture-apache-ignite > > > > > > Denis
JVM metrics for Prometheus are not getting populated for Ignite 2.6.0
Hi Igniters, I am using Spring Boot app to fetch data from Ignite 2.6.0 and have enabled actuators as well for monitoring purpose. Unfortunately, when am using Spring Boot app with Ignite 2.6.0, JVM related metrics (for Prometheus) are not getting produced. But when I use it with ignite 2.7.6 metrics are produced properly. Not sure why there is a difference between these 2 versions? is this a defect or am I missing something? Any pointers on this are appreciated ! Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
Visor plugin
Hello team, I would like to add a new feature to the existing visor commands. Could you give me some direction on how to achieve this if its possible? Do we need a visor plugin ? if so,please provide any example of this plugin . Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re:Re: Problems "query lookup strategy" with Spring Boot 2.1.x and Ignite 2.7.0
in my project, ignite with spring boot 2.1.x cause some problems like you.
please use spring boot 2.0.9 h2-version:1.4.197
At 2019-12-24 09:01:29, "Denis Magda" wrote:
Michele,
If wasn't checking the source code of the Ignite integration but believe you
need to pass on the whole SQL query into @Query annotation. Here are some
samples:
https://apacheignite-mix.readme.io/docs/spring-data#section-apache-ignite-repository
Generally, what's the reason for setting @Query("subscriberId = ?") if the
signature of the method (getPresenceBySubscriberId(long subscriberId) already
assumes the data will be filtered by the parameter? Can't you just remove
@Query("subscriberId = ?") and get the same effect?
-
Denis
On Mon, Jun 10, 2019 at 3:06 AM Pedrotti Michele
wrote:
Hi, I have a SpringBoot’s application 2.1.X and a simple local installation of
ignite 2.7.0.
I have problems when I add to my Repository two simple query methods (without
this methods I don’t have problems, the simple call to “repo.findById” works
correctly) like this:
@RepositoryConfig(cacheName = IgniteConfig.CACHE_NAME)
publicinterface PresenceRepository extends
IgniteRepository {
@Query("subscriberId = ?")
List getPresenceBySubscriberId(longsubscriberId);
@Query("brasIp = ?")
List getPresenceByBrasIp(String brasIp);
}
I am using ignite-spring-data_2.0 , spring-data-commons: 2.0.9 , ignite-spring
2.7.0…
The exception is :
Caused by: java.lang.IllegalStateException: You have defined query method in
the repository but you don't have any query lookup strategy defined. The
infrastructure apparently does not support query methods!
at
org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.(RepositoryFactorySupport.java:545)
at
org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324)
at
org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297)
at org.springframework.data.util.Lazy.getNullable(Lazy.java:211)
at org.springframework.data.util.Lazy.get(Lazy.java:94)
at
org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.afterPropertiesSet(RepositoryFactoryBeanSupport.java:300)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1804)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1741)
... 58 more
Thanks
Michele
| Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla
conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate
ricevuto questo documento per errore siete cortesemente pregati di darne
immediata comunicazione al mittente e di provvedere alla sua distruzione,
Grazie.
This e-mail and any attachments is confidential and may contain privileged
information intended for the addressee(s) only. Dissemination, copying,
printing or use by anybody else is unauthorised. If you are not the intended
recipient, please delete this message and any attachments and advise the sender
by return e-mail, Thanks.
Rispetta l'ambiente. Non stampare questa mail se non è necessario. |
Re: Slow startup with extra 30-40s after integrating ignite
Have you tried to run the same project on a different machine? It takes a
couple of seconds to start any example from Ignite repo on mine.
Try this experiment. Use ExampleNodeStartup from Ignite examples [1] to
start a server node (feel free to switch to TcpIpFinder in the config used
by the examples). Measure. Then run any other example that will connect to
this server node. Measure. It takes a couple of seconds on my Mac. Should
not be that different on Windows.
[1]
https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples
-
Denis
On Sat, Dec 21, 2019 at 6:43 AM xingjl6280 wrote:
> thanks for the reply.
>
> that's what i tried, with a range of port or specified one port only
>
> tcpDiscoveryMulticastIpFinder.setAddresses(Collections.singletonList("
> 127.0.0.1:47500"));
>
> i also tried given one static ip
> tcpDiscoveryVmIpFinder.setAddresses(Collections.singletonList("
> 127.0.0.1:47500"));
>
> but why the discovery still need 40 seconds,
>
> please kindly advise.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Connection from Ignite Client in Docker container to Ignite Server in another Docker container Issues
Do you use Ignite .NET anyhow? By some reason I see the following as part
of the stacktrace:
Caused by: class org.apache.ignite.binary.BinaryObjectException: Failed to
find empty constructor for class:
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
at
deployment.StreamsApp.ear//org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:981)
at
deployment.StreamsApp.ear//org.apache.ignite.internal.binary.BinaryClassDescriptor.(BinaryClassDescriptor.java:267)
at
deployment.StreamsApp.ear//org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1063)
at
deployment.StreamsApp.ear//org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1048)
at
deployment.StreamsApp.ear//org.apache.ignite.internal.binary.BinaryContext.(BinaryContext.java:350)
at
deployment.StreamsApp.ear//org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:208)
-
Denis
On Fri, Dec 20, 2019 at 6:55 AM heavyjax wrote:
> I have installed Ignite server running inside Docker container based on
> CentOS 7.
>
> All my configuration with sources, Dockerfiles and server config avialable
> on GitHub:
> github.com/heavyjax/ignitedemo
>
> I`m usind this command to run Ignite Server Docker image:
> docker run -dit --net=streams-net --name=ignite -p 47100:47100 -p
> 47500:47500 -p 47501:47501 -p 47502:47502 -p 47503:47503 -p 47504:47504 -p
> 47505:47505 -p 47506:47506 -p 47507:47507 -p 47508:47508 -p 47509:47509 -p
> 11211:11211 -p 49112:49112 ignite:latest
>
> And this command to run Ignite Client Docker image:
> docker run -dit --name streams_wf -v
> ~/tmp/app:/opt/jboss/wildfly/standalone/deployments/:rw -v
> ~/tmp/logs:/opt/jboss/wildfly/standalone/log/:rw --network=streams-net -p
> 9990:9990 -p : -p 8090:8080 wf18:latest
>
> Here is my server config:
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd";>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
>
>
>
> 172.20.0.3:47500..47509
>
>
>
>
>
>
>
>
>
> Connection from host machine (Mac OS) to Ignite server in Docker is working
> fine, but when I`m trying to run my client application in another Docker
> container (based on Jboss/Wildfly image) I have exception. Telnet from
> Wildfly container to Ignite container is successfully connected.
>
> Here is client code:
>
> package org.example;
>
> import javax.annotation.PostConstruct;
> import javax.ejb.Singleton;
> import javax.ejb.Startup;
>
> @Singleton
> @Startup
> public class Main {
>
> @PostConstruct
> private void startup(){
> try {
> IgniteInitializer initializer = new IgniteInitializer();
> initializer.init();
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> }
> }
>
> package org.example;
>
> import org.apache.ignite.*;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import
> org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
>
> import java.util.Arrays;
>
> public class IgniteInitializer {
>
> public void init() throws InterruptedException {
> TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
> ipFinder.setAddresses(Arrays.asList("172.20.0.3:47500..47509"));
>
> TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
> discoverySpi.setLocalPort(47500);
> discoverySpi.setLocalPortRange(9);
> discoverySpi.setIpFinder(ipFinder);
>
> TcpCommunicationSpi commSpi = new TcpCommunicationSpi();
> commSpi.setLocalPort(47100);
>
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setDiscoverySpi(discoverySpi);
> cfg.setCommunicationSpi(commSpi);
> cfg.setWorkDirectory("/home/apache-ignite-2.7.6-bin/work");
> cfg.setIgniteHo
Re: Problems "query lookup strategy" with Spring Boot 2.1.x and Ignite 2.7.0
Michele,
If wasn't checking the source code of the Ignite integration but believe
you need to pass on the whole SQL query into @Query annotation. Here are
some samples:
https://apacheignite-mix.readme.io/docs/spring-data#section-apache-ignite-repository
Generally, what's the reason for setting @Query("subscriberId = ?") if the
signature of the method (getPresenceBySubscriberId(long subscriberId)
already assumes the data will be filtered by the parameter? Can't you just
remove @Query("subscriberId = ?") and get the same effect?
-
Denis
On Mon, Jun 10, 2019 at 3:06 AM Pedrotti Michele <
michele.pedro...@telecomitalia.it> wrote:
> Hi, I have a SpringBoot’s application 2.1.X and a simple local
> installation of ignite 2.7.0.
>
> I have problems when I add to my Repository two simple query methods
> (without this methods I don’t have problems, the simple call to
> “repo.findById”
> works correctly ) like this:
>
> @RepositoryConfig(cacheName = IgniteConfig.*CACHE_NAME*)
>
> *public* *interface* PresenceRepository *extends*
> IgniteRepository {
>
> @Query("subscriberId = ?")
>
> List getPresenceBySubscriberId(*long*
> subscriberId);
>
> @Query("brasIp = ?")
>
> List getPresenceByBrasIp(String brasIp);
>
> }
>
> I am using ignite-spring-data_2.0 , spring-data-commons: 2.0.9 ,
> ignite-spring 2.7.0…
>
> The exception is :
>
> Caused by: java.lang.IllegalStateException: You have defined query method
> in the repository but you don't have any query lookup strategy defined. The
> infrastructure apparently does not support query methods!
>
> at
> org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.(RepositoryFactorySupport.java:545)
>
> at
> org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:324)
>
> at
> org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:297)
>
> at org.springframework.data.util.Lazy.getNullable(Lazy.java:211)
>
> at org.springframework.data.util.Lazy.get(Lazy.java:94)
>
> at
> org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.afterPropertiesSet(RepositoryFactoryBeanSupport.java:300)
>
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1804)
>
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1741)
>
> ... 58 more
>
>
>
> Thanks
>
> Michele
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
> abbiate ricevuto questo documento per errore siete cortesemente pregati di
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
>
> * This e-mail and any attachments is confidential and may contain
> privileged information intended for the addressee(s) only. Dissemination,
> copying, printing or use by anybody else is unauthorised. If you are not
> the intended recipient, please delete this message and any attachments and
> advise the sender by return e-mail, Thanks. *
>
> *Rispetta l'ambiente. Non stampare questa mail se non è necessario.*
>
回复: Number of backups of the cache named [ignite sys cache]
In chinese 这个ignite系统缓存，需要在每个节点上都用到，所以设置成最大值。保证每启动一个节点，系统缓存都有且一致 发送自 Windows 10 版邮件应用 发件人: 李玉珏@163 发送时间: 2019年12月23日 22:01 收件人: user@ignite.apache.org 主题: Number of backups of the cache named [ignite sys cache] hi, In the 2.7.6 version, start an ignite node through ignite.sh with the fully default configuration, and then execute the following command: ./control.sh --cache list [.]* The following output will be found: [cacheName=ignite-sys-cache, cacheId=-2100569601, grpName=null, grpId=-2100569601, prim=100, mapped=100, mode=REPLICATED, atomicity=TRANSACTIONAL, backups=2147483647, affCls=RendezvousAffinityFunction] It shows: backups = 2147483647 This is a huge number of backups. Why?
Re: Number of backups of the cache named [ignite sys cache]
Hi! It is not the number of backups, I am not sure why it say that value but you always get that for any replicated cache, quick guess is that it is set max integer value when you use replicated instead of partitioned cache. Mikael Den 2019-12-23 kl. 15:00, skrev 李玉珏@163: hi, In the 2.7.6 version, start an ignite node through ignite.sh with the fully default configuration, and then execute the following command: ./control.sh --cache list [.]* The following output will be found: [cacheName=ignite-sys-cache, cacheId=-2100569601, grpName=null, grpId=-2100569601, prim=100, mapped=100, mode=REPLICATED, atomicity=TRANSACTIONAL, backups=2147483647, affCls=RendezvousAffinityFunction] It shows: backups = 2147483647 This is a huge number of backups. Why?
Re: Number of backups of the cache named [ignite sys cache]
Hi, this is default value for backups for REPLICATED cache mode. This is Ignite internal system cache and it is stored on each node. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Number of backups of the cache named [ignite sys cache]
hi, In the 2.7.6 version, start an ignite node through ignite.sh with the fully default configuration, and then execute the following command: ./control.sh --cache list [.]* The following output will be found: [cacheName=ignite-sys-cache, cacheId=-2100569601, grpName=null, grpId=-2100569601, prim=100, mapped=100, mode=REPLICATED, atomicity=TRANSACTIONAL, backups=2147483647, affCls=RendezvousAffinityFunction] It shows: backups = 2147483647 This is a huge number of backups. Why?
