Re: Spelling and grammar check of subtitles for Ignite videos
Hi Max! While choosing the videos for translation, please note that some meetup talks were transformed already into webinars in English. Like the talk "How Apache Ignite Powers Real-Time Subscriber Offers for a Leading Telecommunications Company" by Alexey Bednov & Fedor Loginov. It was first presented on Apache Ignite Moscow Meetup and already scheduled as a global webinar on June 3d[1]. It makes sense to discuss the choice first and take only up to date materials that were never translated into English. [1] https://www.gridgain.com/resources/webinars/apache-ignite-powers-real-time-subscriber-offers-at-telecommunications-company ср, 8 апр. 2020 г. в 00:46, Maksim Stepachev : > Unfortunately, someone did not respond, I will do it on my own. > > пт, 3 апр. 2020 г., 17:07 Ilya Kasnacheev : > >> Hello! >> >> I could proof read them if nobody with native English will step in. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пт, 3 апр. 2020 г. в 13:58, Maksim Stepachev > >: >> >>> Hi, everyone! >>> >>> I'm going to translate Russian perfect videos about Apache Ignite in >>> English and dubbing them after that. They will be loaded to my youtube >>> channel. I need to help with grammar checking. >>> >>> If somebody wants to take part, please let me know. >>> >>> >>>
Re: prometheus jmx scrape failed
Hello, Zipporah.
AFAIK Zabbix doesn’t support scraping of the tabular data JMX beans.
We add this kind of beans in 2.8.
It’s a system view beans [1]
By default, system views exported in the form of JMX beans and SQL views.
You can:
a. Disable system view JMX exporter via configuration
IgniteConfiguration#setSystemViewExporterSpi
You may want to keep SQL exporter to be able to observe system views via an SQL
interface.
This can be done like that
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setSystemViewExporterSpi(new SqlViewExporterSpi());
b. You can filter system views bean in Zabbix exporter [2]
[1] https://apacheignite.readme.io/docs/system-views
[2]
https://www.zabbix.com/documentation/current/manual/discovery/low_level_discovery/jmx
> 8 апр. 2020 г., в 00:52, zipporah написал(а):
>
> Hi,
>
> I am new to Ignite and have a question regarding prometheus jmx exporter.
>
> So I'm integrating Apache ignite with Apache Spark to accelerate the
> performance of Spark applications. As part of monitoring, I'm using
> prometheus jmx exporter to export metrics to prometheus.
>
> My prometheus and metrics configurations are like this:
> https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/blob/master/spark-docker/conf/prometheus.yaml
>
> This is working fine with ignite 2.7.x. Starting from ignite 2.8, in spark
> application log I'm seeing following errors:
>
> 2020-04-06T16:26:01.595 [pool-1-thread-2hread] ERROR
> prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector - JMX scrape failed:
> java.lang.IllegalArgumentException: Not an Attribute:
> javax.management.openmbean.TabularDataSupport(tabularType=javax.management.openmbean.TabularType(name=*org.apache.ignite.spi.systemview.view.ClientConnectionView*,rowType=javax.management.openmbean.CompositeType(name=org.apache.ignite.spi.systemview.view.ClientConnectionView,items=((itemName=connectionId,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=localAddress,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=remoteAddress,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=systemViewRowId,itemType=javax.management.openmbean.SimpleType(name=java.lang.Integer)),(itemName=type,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=user,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=version,itemType=javax.management.openmbean.SimpleType(name=java.lang.String,indexNames=(systemViewRowId)),contents={})
> at javax.management.AttributeList.adding(AttributeList.java:328)
> at javax.management.AttributeList.adding(AttributeList.java:335)
> at javax.management.AttributeList.asList(AttributeList.java:165)
> at
> io.prometheus.jmx.shaded.io.prometheus.jmx.JmxScraper.scrapeBean(JmxScraper.java:156)
> at
> io.prometheus.jmx.shaded.io.prometheus.jmx.JmxScraper.doScrape(JmxScraper.java:117)
> at
> io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.collect(JmxCollector.java:468)
> at
> io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.findNextElement(CollectorRegistry.java:183)
> at
> io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.nextElement(CollectorRegistry.java:216)
> at
> io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.nextElement(CollectorRegistry.java:137)
> at
> io.prometheus.jmx.shaded.io.prometheus.client.exporter.common.TextFormat.write004(TextFormat.java:22)
> at
> io.prometheus.jmx.shaded.io.prometheus.client.exporter.HTTPServer$HTTPMetricHandler.handle(HTTPServer.java:59)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:79)
> at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:83)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82)
> at
> sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:675)
> at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:79)
> at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:647)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
>
> I have no clue why this is happening. Is there anything wrong with the mbean
> exposed by ignite?
>
> Thanks,
> Zippo
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Concept Question about Ignite
Anthony,
Sorry, looks like I missed it. Here is the link:
https://apacheignite.readme.io/docs/cache-configuration
Evgenii
вт, 7 апр. 2020 г. в 14:48, Anthony :
> Hello Evgenii,
>
> I foud that the link for More information on CacheConfiguration can be
> found here: is missing, could you please resend it to me?
>
> Also,is there a way to find out which setting is the fastest and minimal
> overhead?
>
> Thanks,
>
> Anthony
>
> On Tue, Apr 7, 2020 at 11:46 AM Anthony wrote:
>
>> Thanks for your help Evgenii!
>>
>> On Tue, Apr 7, 2020 at 10:38 AM Evgenii Zhuravlev <
>> e.zhuravlev...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> If these nodes are combined into one cluster, then it will be the same
>>> cache. By default, it will be Partitioned cache without backups and both
>>> nodes will have part of the data. If you want to replicate data fully, you
>>> can set backups to 1 or create cache as Replicated instead of Partitioned.
>>> More information on CacheConfiguration can be found here:
>>>
>>> Best Regards,
>>> Evgenii
>>>
>>> вт, 7 апр. 2020 г. в 10:25, Anthony :
>>>
Hello,
I am new to Ignite and have a few questions.
If I have two process running the following code:
Process 1:
Ignite grid = Ignition::Start(cfg);
Cache cache = grid.GetOrCreateCache>>> std::string>("myCache");
Process 2:
Ignite grid = Ignition::Start(cfg);
Cache cache = grid.GetCache>>> std::string>("myCache");
Will Cache be duplicated to the grid in process 2?
Thanks,
Anthony
>>>
prometheus jmx scrape failed
Hi,
I am new to Ignite and have a question regarding prometheus jmx exporter.
So I'm integrating Apache ignite with Apache Spark to accelerate the
performance of Spark applications. As part of monitoring, I'm using
prometheus jmx exporter to export metrics to prometheus.
My prometheus and metrics configurations are like this:
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/blob/master/spark-docker/conf/prometheus.yaml
This is working fine with ignite 2.7.x. Starting from ignite 2.8, in spark
application log I'm seeing following errors:
2020-04-06T16:26:01.595 [pool-1-thread-2hread] ERROR
prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector - JMX scrape failed:
java.lang.IllegalArgumentException: Not an Attribute:
javax.management.openmbean.TabularDataSupport(tabularType=javax.management.openmbean.TabularType(name=*org.apache.ignite.spi.systemview.view.ClientConnectionView*,rowType=javax.management.openmbean.CompositeType(name=org.apache.ignite.spi.systemview.view.ClientConnectionView,items=((itemName=connectionId,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=localAddress,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=remoteAddress,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=systemViewRowId,itemType=javax.management.openmbean.SimpleType(name=java.lang.Integer)),(itemName=type,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=user,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=version,itemType=javax.management.openmbean.SimpleType(name=java.lang.String,indexNames=(systemViewRowId)),contents={})
at javax.management.AttributeList.adding(AttributeList.java:328)
at javax.management.AttributeList.adding(AttributeList.java:335)
at javax.management.AttributeList.asList(AttributeList.java:165)
at
io.prometheus.jmx.shaded.io.prometheus.jmx.JmxScraper.scrapeBean(JmxScraper.java:156)
at
io.prometheus.jmx.shaded.io.prometheus.jmx.JmxScraper.doScrape(JmxScraper.java:117)
at
io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.collect(JmxCollector.java:468)
at
io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.findNextElement(CollectorRegistry.java:183)
at
io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.nextElement(CollectorRegistry.java:216)
at
io.prometheus.jmx.shaded.io.prometheus.client.CollectorRegistry$MetricFamilySamplesEnumeration.nextElement(CollectorRegistry.java:137)
at
io.prometheus.jmx.shaded.io.prometheus.client.exporter.common.TextFormat.write004(TextFormat.java:22)
at
io.prometheus.jmx.shaded.io.prometheus.client.exporter.HTTPServer$HTTPMetricHandler.handle(HTTPServer.java:59)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:79)
at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:83)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82)
at
sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:675)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:79)
at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:647)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
I have no clue why this is happening. Is there anything wrong with the mbean
exposed by ignite?
Thanks,
Zippo
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Concept Question about Ignite
Hello Evgenii,
I foud that the link for More information on CacheConfiguration can be
found here: is missing, could you please resend it to me?
Also,is there a way to find out which setting is the fastest and minimal
overhead?
Thanks,
Anthony
On Tue, Apr 7, 2020 at 11:46 AM Anthony wrote:
> Thanks for your help Evgenii!
>
> On Tue, Apr 7, 2020 at 10:38 AM Evgenii Zhuravlev <
> e.zhuravlev...@gmail.com> wrote:
>
>> Hi,
>>
>> If these nodes are combined into one cluster, then it will be the same
>> cache. By default, it will be Partitioned cache without backups and both
>> nodes will have part of the data. If you want to replicate data fully, you
>> can set backups to 1 or create cache as Replicated instead of Partitioned.
>> More information on CacheConfiguration can be found here:
>>
>> Best Regards,
>> Evgenii
>>
>> вт, 7 апр. 2020 г. в 10:25, Anthony :
>>
>>> Hello,
>>>
>>> I am new to Ignite and have a few questions.
>>> If I have two process running the following code:
>>>
>>> Process 1:
>>> Ignite grid = Ignition::Start(cfg);
>>> Cache cache = grid.GetOrCreateCache>> std::string>("myCache");
>>>
>>> Process 2:
>>> Ignite grid = Ignition::Start(cfg);
>>> Cache cache = grid.GetCache>> std::string>("myCache");
>>>
>>> Will Cache be duplicated to the grid in process 2?
>>>
>>> Thanks,
>>>
>>> Anthony
>>>
>>
Re: Spelling and grammar check of subtitles for Ignite videos
Unfortunately, someone did not respond, I will do it on my own. пт, 3 апр. 2020 г., 17:07 Ilya Kasnacheev : > Hello! > > I could proof read them if nobody with native English will step in. > > Regards, > -- > Ilya Kasnacheev > > > пт, 3 апр. 2020 г. в 13:58, Maksim Stepachev : > >> Hi, everyone! >> >> I'm going to translate Russian perfect videos about Apache Ignite in >> English and dubbing them after that. They will be loaded to my youtube >> channel. I need to help with grammar checking. >> >> If somebody wants to take part, please let me know. >> >> >>
Re: Concept Question about Ignite
Thanks for your help Evgenii!
On Tue, Apr 7, 2020 at 10:38 AM Evgenii Zhuravlev
wrote:
> Hi,
>
> If these nodes are combined into one cluster, then it will be the same
> cache. By default, it will be Partitioned cache without backups and both
> nodes will have part of the data. If you want to replicate data fully, you
> can set backups to 1 or create cache as Replicated instead of Partitioned.
> More information on CacheConfiguration can be found here:
>
> Best Regards,
> Evgenii
>
> вт, 7 апр. 2020 г. в 10:25, Anthony :
>
>> Hello,
>>
>> I am new to Ignite and have a few questions.
>> If I have two process running the following code:
>>
>> Process 1:
>> Ignite grid = Ignition::Start(cfg);
>> Cache cache = grid.GetOrCreateCache> std::string>("myCache");
>>
>> Process 2:
>> Ignite grid = Ignition::Start(cfg);
>> Cache cache = grid.GetCache> std::string>("myCache");
>>
>> Will Cache be duplicated to the grid in process 2?
>>
>> Thanks,
>>
>> Anthony
>>
>
Re: Concept Question about Ignite
Hi,
If these nodes are combined into one cluster, then it will be the same
cache. By default, it will be Partitioned cache without backups and both
nodes will have part of the data. If you want to replicate data fully, you
can set backups to 1 or create cache as Replicated instead of Partitioned.
More information on CacheConfiguration can be found here:
Best Regards,
Evgenii
вт, 7 апр. 2020 г. в 10:25, Anthony :
> Hello,
>
> I am new to Ignite and have a few questions.
> If I have two process running the following code:
>
> Process 1:
> Ignite grid = Ignition::Start(cfg);
> Cache cache = grid.GetOrCreateCache std::string>("myCache");
>
> Process 2:
> Ignite grid = Ignition::Start(cfg);
> Cache cache = grid.GetCache std::string>("myCache");
>
> Will Cache be duplicated to the grid in process 2?
>
> Thanks,
>
> Anthony
>
Concept Question about Ignite
Hello,
I am new to Ignite and have a few questions.
If I have two process running the following code:
Process 1:
Ignite grid = Ignition::Start(cfg);
Cache cache = grid.GetOrCreateCache("myCache");
Process 2:
Ignite grid = Ignition::Start(cfg);
Cache cache = grid.GetCache("myCache");
Will Cache be duplicated to the grid in process 2?
Thanks,
Anthony
Re: Ignite Restart takes long time
I don’t think you should be activating the cluster every time you restart a node. Generally it’s best to activate the cluster once and manage the baseline topology “manually” after that. > On 7 Apr 2020, at 17:20, krkumar24061...@gmail.com wrote: > > Hi Gianluca Bonetti - Thanks for the help. I actually have that JVM parameter > and now I have removed that. Looks like its working and I will do few more > rounds of testing and then update you. > > Also any idea why ignite.active(true) taking almost 5 minutes whenever i > restart the node? > > Again a big thanks, > > KR Kumar > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite Restart takes long time
Hello Krumar Full explanation about the slowness when using AlwaysPreTouch comes from this article https://access.redhat.com/solutions/2685771 Is it still taking 5 minutes to start, after removing the AlwaysPreTouch parameter? Cheers Gianluca Il giorno mar 7 apr 2020 alle ore 18:20 krkumar24061...@gmail.com < krkumar24061...@gmail.com> ha scritto: > Hi Gianluca Bonetti - Thanks for the help. I actually have that JVM > parameter > and now I have removed that. Looks like its working and I will do few more > rounds of testing and then update you. > > Also any idea why ignite.active(true) taking almost 5 minutes whenever i > restart the node? > > Again a big thanks, > > KR Kumar > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Ignite Restart takes long time
Hi Gianluca Bonetti - Thanks for the help. I actually have that JVM parameter and now I have removed that. Looks like its working and I will do few more rounds of testing and then update you. Also any idea why ignite.active(true) taking almost 5 minutes whenever i restart the node? Again a big thanks, KR Kumar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: PluginProvider method contracts
Hi Alex, Thank you for the reply . I guess I was looking for this >> the createComponent API is called internally by Ignite to create components inside your plugin So if your plugin has only one component, you can as well implement the createComponent and return the right processor. The plugin method is dummy in such a case ( for eg : https://github.com/apache/ignite/blob/ignite-2.5/modules/compatibility/src/test/java/org/apache/ignite/compatibility/testframework/plugins/TestCompatibilityPluginProvider.java ) regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Surrogate Keys and Ignite
Hi, How do you want to access it? Do you want to use SQL or Key-Value API? If KV API, then, you can't use indexes there and solution with additional table should work for you. Also, from performance standpoint, it should be a little bit faster than SQL joins. Best Regards, Evgenii вт, 31 мар. 2020 г. в 03:06, narges saleh : > Hi All, > I also have a general question. Is it a good idea to have a surrogate key > table in ignite? I want to avoid joins, and I don't want to use secondary > indexes. I want to look up this surrogate key table (which should be very > small in terms of volume and is replicated across all the nodes), to find a > dependent key that can be used to quickly to search in a cache? Is having a > secondary index and/or doing a join quicker? > > thanks. > >
Re: Ignite Restart takes long time
Hello Kumar
It seems a problem similar to the one I had in the past.
Please check that you are running the JVM *without* the
"-XX:+AlwaysPreTouch" parameter.
Also, in my experience, using /dev/random as entropy source could block
startup for long time, hence I prefer using /dev/urandom
(set securerandom.source=file:/dev/random in
/etc/java-8-openjdk/security/java.security for Debian-like systems)
Cheers
Gianluca
Il giorno mar 7 apr 2020 alle ore 14:33 krkumar24061...@gmail.com <
krkumar24061...@gmail.com> ha scritto:
> Hi Guys - I have this problem that's very recent and nothing significant
> changed in the system but all of a sudden still takes lot of time to
> restart. I do a graceful shutdown of one of the nodes and restart the node
> after some updates. Now the ignite takes almost 30 minutes to initiate and
> that's killing us.
>
> Here is the snippet of my ignite configuration:
>
> depends-on="dataSource">
>
> class="org.apache.ignite.configuration.IgniteConfiguration">
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> name="connectTimeout" value="1">
> name="socketWriteTimeout" value="3">
>
>
> value="12">
> value="8">
> value="64" />
> value="32" />
>
> class="org.apache.ignite.configuration.DataStorageConfiguration">
> name="writeThrottlingEnabled" value="true">
> name="defaultDataRegionConfiguration">
> class="org.apache.ignite.configuration.DataRegionConfiguration">
> name="initialSize" value="#{512L * 1024 *
> 1024}">
> name="maxSize" value="#{20L * 1024 * 1024 * 1024}" />
> name="persistenceEnabled" value="true" />
>
>
> name="dataRegionConfigurations">
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
>
>
>
>
>
>
> value="#{4 * 1024}" />
> name="storagePath" value="${grid.data}" />
> value="${grid.wal}" />
> name="walArchivePath" value="${grid.wal}" />
> value="BACKGROUND" />
> name="walFlushFrequency" value="1">
>
>
>
> Here is the code snippet of how we create the cache
>
> CacheConfiguration cacheConfig = new
> CacheConfiguration<>();
> cacheConfig.setCacheMode(CacheMode.PARTITIONED);
> cacheConfig.setRebalanceMode(CacheRebalanceMode.ASYNC);
> cacheConfig.setRebalanceDelay(6);
> cacheConfig.setName("eventCache-" + xxx + "-" + xxx);
> cacheConfig.setBackups(1);
> cacheConfig.setAtomicityMode(CacheAtomicityMode.ATOMIC);
>
>
> cacheConfig.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
>
> We start the ignite like the following
>
> context = new ClassPathXmlApplicationContext("xxx.xml");
>
> logger.info("Cluster kernel is initializing ...Done");
> engine = (Ignite) context.getBean("igniteContainer");
> engine.cluster().active(true);
>
>
> Thanx and Regards,
> KR Kumar
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Ignite Restart takes long time
Hi Guys - I have this problem that's very recent and nothing significant
changed in the system but all of a sudden still takes lot of time to
restart. I do a graceful shutdown of one of the nodes and restart the node
after some updates. Now the ignite takes almost 30 minutes to initiate and
that's killing us.
Here is the snippet of my ignite configuration:
Here is the code snippet of how we create the cache
CacheConfiguration cacheConfig = new
CacheConfiguration<>();
cacheConfig.setCacheMode(CacheMode.PARTITIONED);
cacheConfig.setRebalanceMode(CacheRebalanceMode.ASYNC);
cacheConfig.setRebalanceDelay(6);
cacheConfig.setName("eventCache-" + xxx + "-" + xxx);
cacheConfig.setBackups(1);
cacheConfig.setAtomicityMode(CacheAtomicityMode.ATOMIC);
cacheConfig.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
We start the ignite like the following
context = new ClassPathXmlApplicationContext("xxx.xml");
logger.info("Cluster kernel is initializing ...Done");
engine = (Ignite) context.getBean("igniteContainer");
engine.cluster().active(true);
Thanx and Regards,
KR Kumar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Unable to perform handshake within timeout..
Hello! I think that maybe that's your balancer from earlier posts tries to talk HTTP (or some other protocol) to our client port, confusing it. Regards, -- Ilya Kasnacheev вт, 7 апр. 2020 г. в 05:23, kay : > I have two nodes at remote server.. > I found a log > > [WARN] [grid-timeout-worker-#39][ClientListenerNioListener] Unable to > perform handshake within timeout > > Why this logs appear?? > and How can i fix it?? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: C++ ODBC Example Question
Hello! Please take a look at this example, it will store Organization from C++: https://github.com/apache/ignite/blob/56975c266e7019f307bb9da42333a6db4e47365e/modules/platforms/cpp/examples/put-get-example/src/put_get_example.cpp Some additional configuration will be needed to access data using SQL: https://apacheignite-cpp.readme.io/docs/cross-platform-interoperability https://www.gridgain.com/docs/latest/developers-guide/SQL/sql-key-value-storage Regards, -- Ilya Kasnacheev вт, 7 апр. 2020 г. в 02:08, Anthony : > Hello, > > For the following example, instead of storing the "Person" using ODBC, is > it possible to build the "Person" in c++ and store to in the server? > > I still want to use ODBC to retrieve the data. > > > https://github.com/apache/ignite/blob/56975c266e7019f307bb9da42333a6db4e47365e/modules/platforms/cpp/examples/odbc-example/src/odbc_example.cpp > > > Thanks, > > Anthony >
Re: CPP: Query timeout
Hello! Can you please provide logs and thread dumps (collectible with jstack ) of all your Apache Ignite nodes? Hard to pinpoint it otherwise. Thanks, -- Ilya Kasnacheev пн, 6 апр. 2020 г. в 13:22, nidhinms : > I tried to execute an INSERT query to my ignite cluster. It was working > fine. > After they update the ignite server instance with some new jars the query > is > not returning. Can some one guide me to rectify this issue. > > 1. Does peerLoadingEnabled=true has omething to do with this issue. Or does > peerClassLoading work with CPP and Java ignite mixed setup. > 2. Can I set timeout in my query with CPP. > 3. Where I can find info about why a query is getting stalled. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Run apache ignite container on Rpi
It looks like you could build your own image without any code changes. The official Dockerfile is here: https://github.com/apache/ignite/tree/master/docker/apache-ignite I just looked on Dockerhub and it seems that there’s an ARM version of the Linux distribution that it’s based on. Regards, Stephen > On 7 Apr 2020, at 08:47, bribridnl wrote: > > Thank you for your help stephan. > As I'm getting started with docker container do you think I should start > with a java 8 docker image and try work around the issue or use a linux > container in which I'll download all ignite binaries and other stuff ? > Regards, > Brieg > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Run apache ignite container on Rpi
Thank you for your help stephan. As I'm getting started with docker container do you think I should start with a java 8 docker image and try work around the issue or use a linux container in which I'll download all ignite binaries and other stuff ? Regards, Brieg -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
