Hi Raymond,
You will not come across any internode-communication issues with your
deployment configuration as long as the servers and clients are running
withing the K8 environment.
The issue, discussed here, takes place if one of the following happens:
- The clients are deployed in K8 while
Hi Igniters,
I'm looking for a technique that can provide SQL clauses for an external
observer. There is an event 'CacheQueryExecutedEvent' (maps to
EVT_CACHE_QUERY_EXECUTED) that contains the clause. But as I can see it's
produced only for success queries and there is no any event if a query
Andrew created IGNITE-13196:
---
Summary: Greater than Where condition on secondary column in
Primary key does not work when also filtering on primary column in primary key
Key: IGNITE-13196
URL:
Alexey Goncharuk created IGNITE-13195:
-
Summary: Allow skipping autotools invocation when building Ignite
release
Key: IGNITE-13195
URL: https://issues.apache.org/jira/browse/IGNITE-13195
Surkov Aleksandr created IGNITE-13192:
-
Summary: Get value after INSERT and put
Key: IGNITE-13192
URL: https://issues.apache.org/jira/browse/IGNITE-13192
Project: Ignite
Issue Type: Bug
Vladimir Steshin created IGNITE-13194:
-
Summary: Fix
testNodeWithIncompatibleMetadataIsProhibitedToJoinTheCluster()
Key: IGNITE-13194
URL: https://issues.apache.org/jira/browse/IGNITE-13194
Vyacheslav Koptilin created IGNITE-13193:
Summary: Implement fallback to full partition rebalancing in case
historical supplier failed to read all necessary data updates from WAL
Key: IGNITE-13193
URL:
+1 to Alex G.
>From my experience, the most interesting cases with Ignite rebalancing
happen exactly in production. According to the fact that we already have
detailed rebalancing logging, adding info about rebalance performance looks
like a reasonable improvement. With new logs we'll be able to
Hi igniters, Hi Raymond,
that was a really good point. I will try to address it as much as I can.
First of all, this new mode will be configurable for now. As Val suggested,
"TcpCommunicationSpi#forceClientToServerConnections" will be a new
setting to trigger this behavior. Disabled by default.
You're now at the "Ignite Release Managers" group.
Please check you gain access.
On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov
wrote:
> Guys,
>
> I've created the 2.9 release confluence page [1].
> Also, I found that I don't have permission to Team City release tasks. Can
> anyone give me such
Hi Ivan,
Sorry for a possibly naive question. As I understand we are talking
about order of establishing client-server connections. And I suppose
that in some environments (e.g. cloud) servers cannot directly
establish connections with clients. But TCP connections are
bidirectional and we still
Hi Ivan,
sure, TCP connections are lazy. So, if a connection is not already opened
then node (trying to send a message) will initiate connection opening.
It's also possible that the opened connection is spontaneously closed for
some reason. Otherwise you are right, everything is as you described.
Hi, Apache enthusiast!
(You’re receiving this because you’re subscribed to one or more dev or
user mailing lists for an Apache Software Foundation project.)
The ApacheCon Planners and the Apache Software Foundation are pleased to
announce that ApacheCon @Home will be held online, September
Dmitry, hi.
Here is the ticket [1] and PR [2]. Looks trivial. Waiting for the test
completed.
[1] https://issues.apache.org/jira/browse/IGNITE-13194
[2] https://github.com/apache/ignite/pull/7969
29.06.2020 03:43, dpavlov.ta...@gmail.com пишет:
Hi Igniters,
I've detected some new issue
Ivan,
Currently we have no requirement to maintain all possible connections
opened. Every node can have arbitrary number of connections to every
other node (it's configurable with "connectionsPerNode" setting).
Also, we can't expect that client would magically open connection when
we need it,
Hi Igniters!
Probably the only good thing about quarantine is that we realized that our
community spans the globe. And, we would like to keep these connections,
even after our offline, in-person activities resume. So we created Apache
Ignite Virtual Meetup[1].
Join the Virtual Meetup group to
Ivan,
It seems that if a server notices that an existing connection to a
client cannot be used anymore then the server can expect that the
client will establish a new one. Is it just out of current iteration
scope? Or are there still other fundamental problems?
2020-06-29 16:32 GMT+03:00, Ivan
17 matches
Mail list logo
