Hi,
let's look at configuration of LevelDB in Infinispan Server:
https://gist.github.com/mgencur/6520948
After investigating what the configuration element is good
for, I think it's an implementation detail and should be removed.
Every time a mortal entry is stored in the cache, it's put (in i
Hi infinispan-dev,
i'm having a basic issue with infinispan and i wonder if i can get
some lead on what to look next. I have a cache configured in
replicated/sync mode on a cluster made of 3 nodes.
- Node1 writes a key/value in the cache
- Node2 gets it because i have registered a listener for it
Is it because you are doing update in non transcriptional mode?
Is it always the same node which is missing the replicated value?
Meena
On Wed, Sep 11, 2013 at 7:44 PM, Giovanni Meo wrote:
> Hi infinispan-dev,
>
> i'm having a basic issue with infinispan and i wonder if i can get
> some lead o
Hi Tristan,
the remote-query dependencies are now optional in this PR:
https://github.com/infinispan/infinispan/pull/2059
Cheers
On 09/10/2013 03:25 PM, Adrian Nistor wrote:
> I'll solve the ones that result from remote query immediately.
>
> On 09/10/2013 12:40 PM, Tristan Tarrant wrote:
>> Hi
Adding Ray.
Ray, can you please comment on this?
Thanks
Martin
On 11.9.2013 11:34, Martin Gencur wrote:
> Hi,
> let's look at configuration of LevelDB in Infinispan Server:
> https://gist.github.com/mgencur/6520948
>
> After investigating what the configuration element is good
> for, I think it
On 11-Sep-13 12:30, Meena Rajani wrote:
> Is it because you are doing update in non transcriptional mode?
Yeap, as soon as i changed the cache to be transactional the issue is gone.
Problem is that i need this cache to be non-transactional so even while a
transaction is open the updates are sync
Hi,
With the new store API it is possible to iterate over the entries in a store in
parallel. Also the purging of the expired entries happen in parallel as well.
I' like to add a persistenceExecutor (global component) to define the thread
pool that would be used for these parallel operations.
H
Oh, and I didn't go down this path in the lib mode configuration was
because I thought maybe it's useful to be able to configure it to 2
different paths...
On Wed, Sep 11, 2013 at 10:01 AM, Ray Tsang wrote:
> Martin,
>
> While those are implementation details, I think some adjustment should be
+1 to add configuration
I'm not sure if it should be a global component. Having a single
instance would help to reuse some threads and keep the overall amount
of threads under control, but also one would not be able to cap
processing on a single store, and in some use cases if a job is
loading fro
Martin,
While those are implementation details, I think some adjustment should be
allowed for tuning purposes. There should be some reasonable values. On
the other hand, I think that, for the expiration db directory, and data
directory - perhaps we should default somehow. Eg.,
...
A data dire
Mircea,
I saw I could use CacheLoaderException for load()... But what should be
used for write()? Should errors occurred during write() continue to throw
CacheLoaderException? or, can it throw any RuntimeException?
Thanks,
On Fri, Sep 6, 2013 at 9:38 AM, Ray Tsang wrote:
> I'd be happy to ta
On 11.9.2013 19:01, Ray Tsang wrote:
Martin,
While those are implementation details, I think some adjustment should
be allowed for tuning purposes. There should be some reasonable
values. On the other hand, I think that, for the expiration db
directory, and data directory - perhaps we shoul
12 matches
Mail list logo
