Hi Denis,
It's a Android Pad, with 8 cores CPU and 6GB RAM.
We use the Pad to connect servers and some devices with Ubuntu running. It's
only working in a stable LAN environgment.
Is it possible?
thank you
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
What kind of error do you get?
10800 is the default thin client port, are you sure it is open on the
server?
On Mon, Nov 9, 2020 at 8:35 PM ABDumalagan
wrote:
> I am starting a cluster through another computer via PuTTY, and I was
> wondering how to connect a local node started programmatically
Not easily. However, I've managed to solve this issue by setting the
current thread context class loader with the expected one.
final old = Thread.currentThread().getContextClassLoader()
try {
final loader = IgnitePlugin.class.getClassLoader()
Yes Ilya, it worked. Thank you!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
What's the device? Are you planning to start a cluster on those devices? Or
connect from those devices to a cluster deployed on server machines?
-
Denis
On Mon, Nov 9, 2020 at 7:46 PM xingjl6280 wrote:
> Hi team,
>
> Is it possible to integrate ignite into Android?
> My Android device
Hi team,
Is it possible to integrate ignite into Android?
My Android device will only work in LAN environment, I hope it could be
facilitated with the memory sharing and service call function of ignite.
thank you
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello, Asish!
Does it work?
--
Ilya Kazakov
пн, 9 нояб. 2020 г. в 21:26, ashishb888 :
> Thank you Ilya!
>
> I did replace Ignite bean with IgniteSpringBean by using Java configuration
> (and not the XML) as below,
>
> @Slf4j
> @Configuration
> public class
message: because connected host has failed to respond. 171.159.66.12:10800
Ignite would need to be started on 171.159.66.12 in this case.
The discovery section in tells the server where to find other nodes.
see : https://ignite.apache.org/docs/latest/clustering/tcp-ip-discovery
Check
Hi,
Looks like you either did not set the discovery section correctly, there
is a network issue
preventing the C# thin client from connecting, or the server itself has
not started or is not responding.
message: because connected host has failed to respond.
171.159.66.12:10800
Make sure
Also according to the heap dump they aren't cache statistic messages, but
rather, TcpDiscoveryClientMetricsUpdateMessage
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
hi, 6k/sec was a misreading on my part - its more 1mb+ !
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I am starting a cluster through another computer via PuTTY, and I was
wondering how to connect a local node started programmatically with C# to
the cluster?
Right now, I am running into errors with what I have--
I start an ignite server remotely with the script bash
I am starting a cluster through another computer via PuTTY, and I was
wondering how to connect a local node started programmatically with C# to
the cluster?
Right now, I am running into errors with what I have--
I start an ignite server remotely with the script bash
Le lundi 09 novembre 2020 à 19:11 +0300, Ilya Kasnacheev a écrit :
> Hello!
>
> Why Hibernate won't use it for reads of that user, I don't know, it's
> outside of scope of Ignite.
>
> Putting 1,000,000 records in 5 minutes sounds reasonable, especially
> since L2 population is optimized for
interesting! might just work. We will try it out.
E.g. A chance of 500 V's. V has fields a, b, c, (b=foo on all records) and
some client app wants to run a continuous query on all V where b=foo, or was
=foo but now is not following the update.
The writer updates 100 V's, by setting b=bar on all
Did anyone had a chance to look at the code?
Should I make a Java one, or is Kotlin good enough?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Why Hibernate won't use it for reads of that user, I don't know, it's
outside of scope of Ignite.
Putting 1,000,000 records in 5 minutes sounds reasonable, especially since
L2 population is optimized for latency, not throughput (as opposed to e.g.
CacheLoader).
Regards,
--
Ilya
Hello!
You can have a transformer on your data streamer to do something to the old
value (e.g. keep some fields of it in new value V).
Regards,
--
Ilya Kasnacheev
пн, 9 нояб. 2020 г. в 14:52, ssansoy :
> Thanks for this,
>
> We considering this approach - writing all the entries to some
Hello!
I'm actually not convinced that 6k/sec is a lot. Metrics update messages
are passed between nodes to calculate cluster-wide cache metrics.
Have you tried turning them off by setting *IGNITE*_*DISCOVERY*_*DISABLE*
_CACHE_*METRICS*_UPDATE=true, in form of system property or env var?
Hi aealexsandrov respectively igniters,
I would really appreciate to get some answers to my follow-up questions in
particular to 4).
Thanks a lot!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thank you Ilya!
I did replace Ignite bean with IgniteSpringBean by using Java configuration
(and not the XML) as below,
@Slf4j
@Configuration
public class BeansConfig {
@Bean
public IgniteSpringBean igniteSpringBean() {
log.debug("igniteSpringBean service");
Thanks for this,
We considering this approach - writing all the entries to some table V, and
then updating a separate token cache T with a signal, picked up by the
continuous query, which then filters the underlying V records, transforms
them and sends them to the client.
However, one problem we
Hi Vladimir,
I want to limit those threads. I want to control the threads size for
ignite-rest-http.
BR,
Ashish
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Vladimir,
I want to limit those threads. I want to control the threads size for
ignite-rest-http.
BR,
Ashish
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Le lundi 09 novembre 2020 à 14:09 +0300, Ilya Kasnacheev a écrit :
> Hello!
> Putting 1 million entries of a single query in L2 cache does not
> sound like a reasonable use of L2 cache.
Hello.
No one will probably read the whole Event database at once with the
product, but it was a read-speed
Le vendredi 06 novembre 2020 à 11:22 -0800, Evgenii Zhuravlev a écrit :
> Hi,
> How many nodes do you have? Can you check the same scenario with one
> node only? How do you run queries? Is client on the same machine as a
> server node?
>
Hello.
I have 2 nodes, running on differents VMs on the
Hello!
Putting 1 million entries of a single query in L2 cache does not sound like
a reasonable use of L2 cache.
Regards,
--
Ilya Kasnacheev
чт, 5 нояб. 2020 г. в 12:59, Bastien Durel :
> Hello,
>
> I'm using an ignite cluster to back an hibernate-based application. I
> configured L2-cache
Hello!
After you flush the data streamer, you may put a token entry into a small
cache to be picked by continuous query. When query handler is triggered,
all the data will already be available from caches.
The difference with transactional behavior is that transactions promise
(and fail to
Hello!
Do you have a reproducer for this issue for us to try?
Regards,
--
Ilya Kasnacheev
сб, 7 нояб. 2020 г. в 21:27, Paolo Di Tommaso :
> Hello,
>
> I'm experiencing a weird error while launching Ignite with a custom
> classloader.
>
> It fails to join the cluster with the error reported
29 matches
Mail list logo