Hello @frankie,
Guess I faced the same issue when was trying to mount a directory on Windows
host. Are you using Windows too? Can you please provide some logs using the
way which @Vasiliy Sisko proposed.
As I know, mounting volumes from a Windows directory is done using by SMB.
This way mongodb m
Hi Michael
Pls find my response
Does that mean Ignite cannot scale well against Berkley dB Incase of single
node?
Could you please clarify, what your question means?
(Rajesh) Our application currently uses Berkley dB and we are using it as
key value dB ie storing object as value as bytes, we a
Hi Mansoor,
in general, there're two approaches:
1. get data to a client, update and send it back
2. send code to data and make the update there
Both can work, which one is faster depends on your case, it depends on data
model size, backup count, your network speed.
So this is something that you
Rajesh,
>Does that mean Ignite cannot scale well against Berkley dB Incase of
single node?
Could you please clarify, what your question means?
Ignite can scale from a single node to hundreds(or even thousands, I have
seen the only cluster of 300 nodes, but this definitely not a limit).
It was des
Any pointers please
Thanks
Rajesh
On 5 Feb 2018 10:53 p.m., "Rajesh Kishore" wrote:
> Hi Christos
>
> Does that mean Ignite cannot scale well against Berkley dB Incase of
> single node?
>
> Regards
> Rajesh
>
> On 5 Feb 2018 10:08 p.m., "Christos Erotocritou"
> wrote:
>
>> Hi Rajesh,
>>
>> Ign
Hi Luqman,
you're right, peer class loading is exactly what you need, isolated or
shared mode fit your case and will automatically deploy a new compute
classes,
but unfortunately, there's no way to enable peer class loading without
cluster restart.
So you need to plan a maintenance for your cluste
Hey guys,
I am new to Ignite and trying to implement a custom counter. I read the
document and it seems like I can implement my counter in three different
ways so need some help figuring out which approach to take.
//business logic in pseudo code
Ignite ignite = Ignition.ignite();
IgniteTransact
Hey guys,
I am new to Ignite and trying to implement a custom counter. I read the
document and it seems like I can implement my counter in three different
ways so need some help figuring out which approach to take.
//business logic in pseudo code
Ignite ignite = Ignition.ignite();
IgniteTransact
Val,
Yes, that definitely makes sense regarding not being able to move a
directory into one of its descendants.
However, it's not just that the example is wrong but also these sentences:
You are free to rename/move data files as you wish, but directories can be
only renamed.
You cannot move the
Hi Christos
Does that mean Ignite cannot scale well against Berkley dB Incase of single
node?
Regards
Rajesh
On 5 Feb 2018 10:08 p.m., "Christos Erotocritou"
wrote:
> Hi Rajesh,
>
> Ignite is a distributed system, testing with one node is really not the
> way.
>
> You need to consider having m
Hi Rajesh,
Ignite is a distributed system, testing with one node is really not the way.
You need to consider having multiple nodes and portion and collocate your data
before.
Thanks,
C
> On 5 Feb 2018, at 16:36, Rajesh Kishore wrote:
>
> Hi,
>
> We are in the process of evaluating Ignite na
Hi,
We are in the process of evaluating Ignite native persistence against
berkely db. For some reason Ignite query does not seem to be performant the
way application code behaves against berkley db
Background:
Berkley db - As of now, we have berkley db for our application and the data
is stored a
Sorry, it was a mistake in my previous answer, I meant that you should stop
all nodes of version 2.1 at first.
Evgenii
2018-02-05 17:35 GMT+03:00 Evgenii Zhuravlev :
> Hi,
>
> You witnessed his issue because you have node of the previous version in
> the cluster on the address abcd-lapp0003.mgmt
Hi,
You witnessed his issue because you have node of the previous version in
the cluster on the address abcd-lapp0003.mgmt..org/xx.xx.21.26. You
should start all nodes of version 2.1 at first and then start nodes with a
new version.
Evgenii
2018-02-05 17:31 GMT+03:00 aMark :
> Hi
>
>
> We a
Hi
We are using Ignite cache version 2.1. We are using it as persistent store
in Partitioned Mode having 6 data node running. Atomicity mode is
ATOMIC, and Rebalance mode is ASYNC while CacheWriteSynchronizationMode is
FULL_SYNC.
We are upgrading the env to latest Ignite version 2.3. As we a
Hi,
We are using Ignite cache version 2.1 . We are using it as persistent store
in Partitioned Mode having 6 data node running. Atomicity mode is
ATOMIC, and Rebalance mode is ASYNC while CacheWriteSynchronizationMode is
FULL_SYNC.
We have ignite client which does read/write to ignite data gri
Hi there,
We have several hundred ignite server nodes and few clients which are
loading classes to ignite on demand.
Now from time to time we need to redeploy the client with some new changes,
which could include changes in the classes which are already loaded to
ignite worker nodes through ignite
Hi,
Previously, in real applications, I needed such information about what is
the remaining lifetime for the object (at least for debug and monitoring).
So I am also +1 for providing such information in the API. Otherwise, user
have to duplicate this information in an entry field.
Sincerely,
Dmi
18 matches
Mail list logo