I'm askin in separate question so people can search for it if they ever
come across this...
My server nodes are started as and I also connect the client as such.
foo:47500
...
If the client subscribed for data-change updates through continuous queries
APIs, then any server can start opening a connection with the client to
deliver an update once the time comes. There might be some other APIs that
work similarly.
If the server can't reach out client it won't shut down its
Thanks! By the way in what cases, does the server need to connect back to
the client? And does that in any way affect the server state and topology?
Like if a server couldn't reach a thick client for any reason would it take
itself offline somehow?
On Fri, 26 Jun 2020 at 12:46, Denis Magda wrote
John, Stephen,
Just for your reference, soon we'll introduce a configuration option that
will prevent servers from initiating a connection with thick clients. The
clients will be required to open the connection:
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-f
Good point. In some cases I use near cache. Maybe for the ones that don't
need it, I can use the thin client.
I'm looking to see what port and I.Ps are made available to the container
and see if I can set up address forwarding or whatever it's called.
On Fri, 26 Jun 2020 at 11:35, Stephen Darling
Yes, thick client nodes are peers, and so can both accept and initiate
connections to and from other nodes.
It’s often easier to get a thin-client to work under these circumstances, as
they behave in a more traditional client-server manner. Is that a viable option?
Regards,
Stephen
> On 26 Jun
Hi, I have 3 server nodes deployed on VMs as far as they are concerned it's
practically bare metal installation.
My client nodes CLIENT=TRUE connect from within DC/OS Cluster using docker
in either bridged network or closed DC/OS network. I.e: They are not
visible to the network.
In TCP/IP Discov
Hello!
If both tbl_a and tbl_c use tbl_b.id == tbl_a.fk_id == tbl_c.fk_id as
affinity key, then I assume it would.
Regards,
--
Ilya Kasnacheev
чт, 25 июн. 2020 г. в 19:17, manueltg89 :
> With the following structure, and partitioned cache in the three tables:
>
> tbl_a tbl_b tbl_c
Hello!
Make sure user's login is "in quotes", otherwise it will be
case-insensitive, i.e. ALLCAPS login.
Regards,
--
Ilya Kasnacheev
пт, 26 июн. 2020 г. в 05:02, marble.zh...@coinflex.com <
marble.zh...@coinflex.com>:
> thanks a lot, with statement works.
>
> Btw, created a new user , but can
Hello!
Please write to user-unsubscr...@ignite.apache.org, etc,
to unsubscribe from lists.
Regards,
--
Ilya Kasnacheev
чт, 25 июн. 2020 г. в 22:16, Sriveena Mattaparthi <
sriveena.mattapar...@ekaplus.com>:
>
> “Confidentiality Notice: The contents of this email message and any
> attachments a
Hello!
You can put protobuf values as byte[] into our cache. SQL will not be able
to index these.
Regards,
--
Ilya Kasnacheev
чт, 25 июн. 2020 г. в 22:17, abhi2703 :
> Hi All,
>
> I want to use protobuf end to end.. Java -> Ignite -> Cassandra.
>
> Is it possible?
>
> Please help.
>
> Regards
Hello!
In Apache Ignite, data is held in Durable Memory regardless whether you
have persistence enabled or not.
https://apacheignite.readme.io/docs/durable-memory-tuning
I guess these classes are in the 'persistence' package for historical
reasons.
Regards,
--
Ilya Kasnacheev
пт, 26 июн. 2020
The discussion is moved to the security channel. Please don’t respond here.
Denis
On Friday, June 26, 2020, Jinny Ramsmark wrote:
> Hello!
>
> I have a client who has designed an application where the user can input
> SQL directly in the browser and send it to the application.
> The application
I am not able to understand why below methods are hot methods in my
application. And I do not use persistence for my application yet.
- org.apache.ignite.internal.processors.cache.persistence.tree.io
-
org.apache.ignite.internal.processors.cache.persistence.tree.io.CacheVersionIO.read(long,
bool
Hello!
I have a client who has designed an application where the user can input SQL
directly in the browser and send it to the application.
The application will then use the H2 database in Ignite to join data taken from
a Mongo database for analytical purposes which will then be displayed in the
15 matches
Mail list logo