Hi,
You can choose to run the kafka connector in a separate machine as long as
it is able to connect to Kafka cluster and Ignite cluster within the network
Regards,
Saikat
On Mon, Jun 14, 2021 at 10:34 AM shubhamshirur
wrote:
> Where I should run my connector if Kafka and ignite are running
Problem: Ignite client hangs forever when performing a cache operation. We
have 6 ignite servers running, the problem goes away when reducing this to
3. What effect does expanding/reducing the server cluster have that could
cause this?
See attached for sample stack trace of hanging client thread,
Hey all
We see continual very large growth to data with ignite native. We have a
very chatty use case that's creating and deleting stuff often. The data on
disk just keeps growing at an explosive rate. So much so we ported this to
a DB to see the difference and the DB is much smaller. I was
Where I should run my connector if Kafka and ignite are running over two
different machines. On the same node as that Kafka running or ignite
running?
Thank you in advance.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes it`s possible, but one data region can`t be mixed = persistent on one node
and in mem on another.
>Background on Use case: We have around 1 tasks that we want to run across
>ignite cluster. These tasks will be submitted by multiple independent client
>nodes. Each task will have a
I think you’d want to have at least two persistent nodes, or the loss of a
single node could take down your whole service.
> On 14 Jun 2021, at 15:51, Krish wrote:
>
> Background on Use case: We have around 1 tasks that we want to run across
> ignite cluster. These tasks will be submitted
Background on Use case: We have around 1 tasks that we want to run across
ignite cluster. These tasks will be submitted by multiple independent client
nodes. Each task will have a priority and task key. Two tasks with the same
taskKey should not be running in parallel. Execution of all the
Yes, but why? What’s the use case?
(Server nodes in your baseline topology will use the persistent store. Other
nodes will be memory-only.)
> On 14 Jun 2021, at 13:45, Krish wrote:
>
> Is it possible to have a cluster topology where native persistence is enabled
> only for one node and all
As long as you only have persistent caches on the persistent nodes it
should be fine, you cannot have a persistent cache on a non persistent
node as far as I am aware of.
On 2021-06-14 14:45, Krish wrote:
Is it possible to have a cluster topology where native persistence is enabled
only for
Is it possible to have a cluster topology where native persistence is enabled
only for one node and all other nodes use in-memory cache store *without
*native persistence?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
10 matches
Mail list logo
