Tim,
Sounds like some bottleneck that holds Ignite from scaling vertically. I’ll
appreciate if you ask the team to connect with Ignite dev community (via
Ignite dev list). Probably, we can reproduce the bottleneck with their help.
Denis
On Monday, July 22, 2019, tim shea wrote:
> Anecdotally
Anecdotally I can tell you that another team I work with is running an
Ignite cluster with 5 JVM instances, each running one Ignite server, per
machine. A dozen ore so machines last I heard. They settled on 5 per
machine after doing performance testing on various topologies, and got
the best
I’m aware of that, that’s what I was saying… the problem is, then it skips my
inbox and doesn’t come up on my phone. So leaving it in the “inbox” folder so I
can read it make it super disorganized to look at when I’m trying to scan
through my emails to read, or later to sort back into a folder.
I'm not a Docker expert and we'll defer this question to the rest of the
community.
However, from an architecture perspective, what's the reason for deploying
multiple Ignite instances per container? If those instances are server
nodes than you are risking to lose them all and have data loss if
Alexandr,
If .WithExecute is not planned to be made available in the C# client, what
is the plan to support custom thread pools from the C# side of things?
Thanks,
Raymond.
On Thu, Jul 18, 2019 at 9:28 AM Raymond Wilson
wrote:
> The source of inbound requests into Server A is from client
Huzzah!
From: Dmitriy Pavlov
Sent: Monday, July 22, 2019 6:54 AM
To: dev ; user ;
annou...@apache.org
Subject: [ANNOUNCE] Apache Ignite 2.7.5 Released
The Apache Ignite Community is pleased to announce the release of Apache Ignite
2.7.5.
Apache Ignite [1] is a memory-centric distributed
Hi,
I am trying to run Ignite Cluster in Docker. I am running Docker Desktop
2.0.0.3 and I downloaded apacheignite image from Docker Hub. I am able to
start multiple Ignite Nodes from Windows Power shell, on e container at a
time.
docker run --rm --name myignite -p 47500:47500 -p 47501:47501 -p
please see client and server configs.
<>
Stephen,
Thanks for your quick response.
It's my bad and I have added below entry and resolved the issue.
Thanks,
Raja.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
How many nodes in your cluster? How many keys in your dataset?
Regards,
Stephen
> On 22 Jul 2019, at 16:16, raja24 wrote:
>
> Hi,
>
> I haven below configuration and partitioned cache didn't distributed for all
> the server nodes.
>
>
Hi,
I haven below configuration and partitioned cache didn't distributed for all
the server nodes.
Hi, could you please share your configurations of both server and client?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
It seems this is a known issue
https://issues.apache.org/jira/browse/IGNITE-11438 which was recently fixed
and will be available in AI 2.8.
Thanks,
S.
пн, 22 июл. 2019 г. в 15:02, ales :
> Hello,
>
> Our company is currently facing an issue with Ignite expired entries that
> remains in
Hello,
Our company is currently facing an issue with Ignite expired entries that
remains in the cache.
Here is the setup to reproduce:
create an ignite client (in client mode false) and put some data (10k
entries/values) to it with very small expiration time (~20s) and TTL
enabled. Each time the
The Apache Ignite Community is pleased to announce the release of Apache
Ignite 2.7.5.
Apache Ignite [1] is a memory-centric distributed database, caching,
and processing platform for transactional, analytical, and streaming
workloads delivering in-memory speeds at petabyte scale.
This release
15 matches
Mail list logo
