file blocks
on-heap.
It looks like option "1) deprecate/remove IgfsPerBlockLruEvictionPolicy "
is the way to go. Please let me know if there are any objections.
On Thu, May 25, 2017 at 9:25 PM, Denis Magda <dma...@apache.org> wrote:
>
> > On May 25, 2017, at 5:17
Hi, colleagues,
as Ignite caches moved to paged offheap memory , the
IgfsPerBlockLruEvictionPolicy does not seem to work as expected any more,
because
1) interface org.apache.ignite.cache.eviction.EvictionPolicy now only
defines "eviction from on-heap", not a real eviction, because each on-heap
Hi, dev,
one of Ignite users discovered that IGFS does not correctly work with
secondary HDFS file system if that HDFS is "kerberised". The issue is
described in https://issues.apache.org/jira/browse/IGNITE-2195 (This may
also be close to this issue:
:
On Thu, Dec 17, 2015 at 10:14 PM, Ivan V. <iveselovs...@gridgain.com> wrote:
> Hi, dev,
> one of Ignite users discovered that IGFS does not correctly work with
> secondary HDFS file system if that HDFS is "ke
anges and edit them whenever
> required.
>
> In addition I noted that we have a disabled and empty article for BigTop
> distribution. Is this OK?
>
> —
> Denis
>
> > On 15 дек. 2015 г., at 12:10, Ivan V. <iveselovs...@gridgain.com> wrote:
> >
> > Denis, g
Hi, Valentin,
1) first of all note that the author of the question uses not the latest
doc page, namely
http://apacheignite.gridgain.org/v1.0/docs/igfs-secondary-file-system .
This is version 1.0, while the latest is 1.5:
https://apacheignite.readme.io/docs/hadoop-accelerator. Besides, it
Cos
>
> P.S. I have a hunch though it is 0022
>
> On Mon, Nov 23, 2015 at 02:01PM, Ivan V. wrote:
> > Hi, Konstantin,
> >
> > >Perhaps more logical would be to do what Unix does: if permissions
> aren't
> > explicitly set during creation, those should be in
Hi, Konstantin,
>Perhaps more logical would be to do what Unix does: if permissions aren't
explicitly set during creation, those should be inherited from the parent.
as per my observations on Linux, the implicitly created directories take
default permissions 0777 & ~umask but not inherit them
, Nov 20, 2015 at 10:45 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> On Fri, Nov 20, 2015 at 11:08 AM, Ivan V. <iveselovs...@gridgain.com>
> wrote:
>
> > Hi, Dmitriy,
> > to wait for memory freeing we have
> > method
> > org.apache.ignite.inte
Hi, dev,
need opinions on the question discussed in
https://issues.apache.org/jira/browse/IGNITE-1679 (IGFS: Purge event is
inconsistent).
In short: in Igfs we have "soft" delete that moves the deleted file or
folder to special "TRASH" folder.
Special async worker walks inside TRASH and removes
aking the PURGE behavior consistent between
> directory and file deletions?
>
> D
>
> On Fri, Nov 20, 2015 at 8:15 AM, Ivan V. <iveselovs...@gridgain.com>
> wrote:
>
> > Hi, dev,
> > need opinions on the question discussed in
> > https://issues.apach
er should have minimal chance to do a mistake in common scenarios.
> >
> > On Wed, Nov 11, 2015 at 1:47 PM, Ivan V. <iveselovs...@gridgain.com>
> > wrote:
> >
> > > Hi, dev,
> > > currently IGFS URI has form
> > > igfs://[igfs-name[:grid-name]]@[h
Hi, dev,
currently IGFS URI has form
igfs://[igfs-name[:grid-name]]@[host[:port]]/[path] .
This connection can be established with "in-process" routine (used mostly
in tests), or with SHMEM, or with TCP protocol.
Current logic of "igfs-name" and "grid-name" handling is as follows.
In case of
13 matches
Mail list logo
