Thanks, Dmitry,
we seem to have maxed out the performance we can get out of a single ignite
node on a DL380 / whats the best option to scale out and make all replicas
also serve data over get requests?
-Ani
On Fri, Aug 31, 2018 at 12:34 PM dkarachentsev
wrote:
> Hi,
>
> get() operation from
thanks!
On Fri, Aug 31, 2018 at 12:28 PM dkarachentsev
wrote:
> Hi,
>
> You can, for example, set SYNC rebalance mode for your replicated cache
> [1].
> In that case all cache operations will be blocked unless rebalance is
> finished, and when it's done you'll get a fully replicated cache.
>
Ignite 2.5
Is there a way to ensure grid nodes don't serve any requests until they are
caught up with the replicated state in the cluster?
Thanks
--
Anirudha P. Jadhav
Ignite 2.5 - fully replicated 8 node cluster
When running load tests with 1 unique key, only one of the servers gets all
the requests.
Is there something to be enabled in configuration for balancing load
between all machines.
Thanks
--
Anirudha P. Jadhav
// Do you //
Love Ignite
Breathe in-Memory compute..
Work on a diverse set of challenging problems, while contributing to open
source.
please contact me at ajadh...@bloomberg.net
NYC based position
Ani
we are just in the works of using a separate zk cluster to provide an
implementation for segmentation resolution. If anyone else is working on it
we could collaborate.
or create a separate jira for a design review? what do you guys think? i
think we could also make zk itself pluggable
-Ani
On
egards,
> Igor
>
> On Wed, Oct 18, 2017 at 6:06 AM, Anirudha Jadhav <aniru...@nyu.edu> wrote:
>
>> i went through this,
>>
>> having a JNI dependency is a no-go our our apps. (quoted below from the
>> link you gave above ).
>>
>> hence want to kn
;
> On Wed, Oct 18, 2017 at 9:54 AM, Anirudha Jadhav <aniru...@nyu.edu> wrote:
>
>> I need a way to access ignite IMDG/DB from c/c++.
>>
>> The JNI c++ clients is not an option for us.
>>
>> i am currently exploring performance between redis / memchached c/c++
I need a way to access ignite IMDG/DB from c/c++.
The JNI c++ clients is not an option for us.
i am currently exploring performance between redis / memchached c/c++
clients
Q: does ignite ODBC drivers also have a JNI dependency?
Q: what the best approach to access remote ignite grids from c++
