Nikolay Izhikov created IGNITE-11677:
Summary: LOCAL cache on client node can't be created if
persistence enabled
Key: IGNITE-11677
URL: https://issues.apache.org/jira/browse/IGNITE-11677
Pr
Ilya Kasnacheev created IGNITE-11547:
Summary: ClassCastException when creating LOCAL cache on client in
Data Region which is considered persistent
Key: IGNITE-11547
URL: https://issues.apache.org/jira/browse
Dmitry,
I don't think we need to show warnings until there is an attempt to create
a local cache. This is a very rare use case, not worth it. We should
properly document it though.
-Val
On Fri, Feb 2, 2018 at 12:18 AM, Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:
> Sounds pretty rea
Sounds pretty reasonable for me, so fix will entail just in proper
exception.
Maybe it worth to show warning that says that's no data region
configured and it's not possible to create LOCAL cache?
Thanks!
02.02.2018 00:08, Valentin Kulichenko пишет:
I meant "they should *explicitly* provide d
I meant "they should *explicitly* provide data region configuration", of
course.
-Val
On Thu, Feb 1, 2018 at 10:58 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Agree with Mike. I don't think it's a good idea to implicitly create data
> regions on client node. If one wants to
Agree with Mike. I don't think it's a good idea to implicitly create data
regions on client node. If one wants to have a local there, they should
implicitly provide data region configuration (default or otherwise). If
data region is not configured, then we should throw proper exception
instead of N
Hi Dmitry,
I think we should make a user to explicitly create data region on a client.
Client nodes aren't supposed to be used for data storing, so if someone
what to use a local cache on a client node, let's make him/her create data
region explicitly. Just to make sure that user knows what he/sh
Hello everyone!
We have an erroneous use case when client tries to create LOCAL cache,
but by default it does not initiates default data region. So client gets
NPE. [1]
I think it should be a lazy data region initialization on client. Do you
have any concerns about this approach or other pro
pts to create a local cache
> on client node will result in exception.
>
> This solution allows users to have local caches on client nodes (with all
> appropriate capacity planning; so we are talking about experienced users);
> at the same time it allows starting lightweight client
default MemoryPolicy is allocated and any attempts to create a local cache
on client node will result in exception.
This solution allows users to have local caches on client nodes (with all
appropriate capacity planning; so we are talking about experienced users);
at the same time it allows starting
It's abdolutely fine to have local caches on client nodes if an application
needs to cache data locally in hashtable like data structure and talk to it
using Ignite APIs.
The upshot is that this kind of cache can be started on any node and we
should keep supporting this capability in 2.0.
--
Deni
Hello Igniters,
Participating in big effort of reworking cache storage structures
(IGNITE-3477 [1]) I came across a test that looks strange to me:
*CacheStopAndDestroySelfTest::testLocalClose*.
It is very simple: it starts two server nodes and one client node (with
forceServerMode flag set to tru
nt it may be very useful in some cases, because LOCAL
> >> cache is a kind of HashMap on "steroids" (it has transactions,
> evictions,
> >> and more).
> >>
> >> So we should throw exception or describe in documentation.
> >&g
t;>
>> But from user point it may be very useful in some cases, because LOCAL
>> cache is a kind of HashMap on "steroids" (it has transactions, evictions,
>> and more).
>>
>> So we should throw exception or describe in documentation.
>>
>> Th
ay be very useful in some cases, because LOCAL
cache is a kind of HashMap on "steroids" (it has transactions, evictions,
and more).
So we should throw exception or describe in documentation.
Thoughs?
Code that show local cache on client node:
public class LocalCacheOnClient {
pub
ses, because LOCAL
cache is a kind of HashMap on "steroids" (it has transactions, evictions,
and more).
So we should throw exception or describe in documentation.
Thoughs?
Code that show local cache on client node:
public class LocalCacheOnClient {
public static void main(String[]
16 matches
Mail list logo
