Hrishikesh Gadre created HDFS-13956:
---
Summary: iNotify should include information to identify a file as
either replicated or erasure coded
Key: HDFS-13956
URL: https://issues.apache.org/jira/browse/HDFS-13956
Wei-Chiu Chuang created HDFS-13040:
--
Summary: Kerberized inotify client fails despite kinit properly
Key: HDFS-13040
URL: https://issues.apache.org/jira/browse/HDFS-13040
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-12413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huafeng Wang resolved HDFS-12413.
-
Resolution: Not A Problem
> Inotify should support erasure coding policy op as replica m
Kai Zheng created HDFS-12413:
Summary: Inotify should support erasure coding policy op as
replica meta change
Key: HDFS-12413
URL: https://issues.apache.org/jira/browse/HDFS-12413
Project: Hadoop HDFS
seem appropriate. As I
explained earlier, the correct fix for this problem should be at the client
side, which is supposed to renew Kerberos credential before it expires.
> NameNode should use loginUser(hdfs) to serve iNotify
this off.
> Include event for AddBlock in Inotify Event Stream
> --
>
> Key: HDFS-10608
> URL: https://issues.apache.org/jira/browse/HDFS-10608
> Project: Hadoop HDFS
>
Wei-Chiu Chuang created HDFS-10799:
--
Summary: NameNode should use loginUser(hdfs) to serve iNotify
requests
Key: HDFS-10799
URL: https://issues.apache.org/jira/browse/HDFS-10799
Project: Hadoop HDFS
churro morales created HDFS-10608:
-
Summary: Include event for AddBlock in Inotify Event Stream
Key: HDFS-10608
URL: https://issues.apache.org/jira/browse/HDFS-10608
Project: Hadoop HDFS
I was thinking we provided the blockId, blockPoolId, path thats enough for
the client to get an ExtendedBlock and they can do the rest?
Agree on the snapshot operations for Inotify.
I'll create a jira ticket.
thanks for the feedback
rahul
On Tue, Jul 5, 2016 at 11:36 AM, Colin McCabe
s the client will write. Would you mind filing a JIRA for this?
We should also set up inotify events for the snapshot operations at some
point as well.
regards,
Colin
On Fri, Jul 1, 2016, at 10:28, rahul gidwani wrote:
> Hello kind folks,
>
> I was wondering if anyone would be interest
Hello kind folks,
I was wondering if anyone would be interested in adding a AddBlock Event to
the inotify pipeline? We were thinking about using Inotify for hdfs
replication to another datacenter.
Right now the problem is with the appends. We get a notification when an
append starts with an
Hello Rahul,
I don't believe there is any fundamental difference in the handling of the
atime update for HDFS inotify. I'd expect you to receive an event with
EventType.METADATA and MetadataUpdateEvent.TIMES, and I wouldn't expect
that you'd need to save a new fsimage to trig
I was testing Inotify locally and noticed that unless I save the FSImage I
can't get a MetadataUpdateEvent to get fired.
The test is pretty basic:
I setup a minicluster with
conf.setLong("dfs.access.time.precision", 1);
create a file (verify I get a EventType.Create)
I rea
, September 22, 2015 9:29 AM, Colin P. McCabe
wrote:
Hi Mohammad,
Like ATM said, HDFS-8965 is an important fix in this area. We have
found that it prevents cases where INotify tries to read invalid
sequences of bytes (sometimes because the edit log was truncated or
corrupted; other times because
Hi Mohammad,
Like ATM said, HDFS-8965 is an important fix in this area. We have
found that it prevents cases where INotify tries to read invalid
sequences of bytes (sometimes because the edit log was truncated or
corrupted; other times because it is in the middle of a write).
HDFS-8964 fixes the
x27;s suggestion of getting a heap dump would almost certainly let you get to
the bottom of this, but I'll just throw out there that it sounds like you may
have been hitting https://issues.apache.org/jira/browse/HDFS-8965, which indeed
can be triggered by use of inotify. That's fixed now, and
Hey Mohammad,
Ravi's suggestion of getting a heap dump would almost certainly let you get
to the bottom of this, but I'll just throw out there that it sounds like
you may have been hitting https://issues.apache.org/jira/browse/HDFS-8965,
which indeed can be triggered by use of inoti
Hi Mohammad!
Thanks for reporting the issue. Could you please take a heap dump of the NN and
analyze it to see where the memory is being spent?
ThanksRavi
On Tuesday, September 15, 2015 11:53 AM, Mohammad Islam
wrote:
Hi,We were using INotify feature in one of our internal service
any help or pointer?
On Tuesday, September 15, 2015 11:52 AM, Mohammad Islam
wrote:
Hi,We were using INotify feature in one of our internal service. Looks like it
creates a lot of memory pressure on NN. Memory usage goes very high and remains
the same causing expensive GC.
Did
Hi,We were using INotify feature in one of our internal service. Looks like it
creates a lot of memory pressure on NN. Memory usage goes very high and remains
the same causing expensive GC.
Did anyone use this feature in any service? Is there any con to setup? We are
using latest CDH.
Regards
Ming Ma created HDFS-8940:
-
Summary: Support for large-scale multi-tenant inotify service
Key: HDFS-8940
URL: https://issues.apache.org/jira/browse/HDFS-8940
Project: Hadoop HDFS
Issue Type
Surendra Singh Lilhore created HDFS-8933:
Summary: Inotify : Support Event-based filtering
Key: HDFS-8933
URL: https://issues.apache.org/jira/browse/HDFS-8933
Project: Hadoop HDFS
Surendra Singh Lilhore created HDFS-8742:
Summary: Inotify: Support event for OP_TRUNCATE
Key: HDFS-8742
URL: https://issues.apache.org/jira/browse/HDFS-8742
Project: Hadoop HDFS
Surendra Singh Lilhore created HDFS-8735:
Summary: Inotify : All events classes should implement toString()
API.
Key: HDFS-8735
URL: https://issues.apache.org/jira/browse/HDFS-8735
Project
Colin Patrick McCabe created HDFS-8305:
--
Summary: HDFS INotify: the destination argument to RenameOp should
always end with the file name
Key: HDFS-8305
URL: https://issues.apache.org/jira/browse/HDFS-8305
Zhe Zhang created HDFS-7929:
---
Summary: inotify unable fetch pre-upgrade edit log segments once
upgrade starts
Key: HDFS-7929
URL: https://issues.apache.org/jira/browse/HDFS-7929
Project: Hadoop HDFS
Colin Patrick McCabe created HDFS-7513:
--
Summary: HDFS inotify: add defaultBlockSize to CreateEvent
Key: HDFS-7513
URL: https://issues.apache.org/jira/browse/HDFS-7513
Project: Hadoop HDFS
Colin Patrick McCabe created HDFS-7446:
--
Summary: HDFS inotify should have the ability to determine what
txid it has read up to
Key: HDFS-7446
URL: https://issues.apache.org/jira/browse/HDFS-7446
James Thomas created HDFS-6939:
--
Summary: Support path-based filtering of inotify events
Key: HDFS-6939
URL: https://issues.apache.org/jira/browse/HDFS-6939
Project: Hadoop HDFS
Issue Type: Sub
James Thomas created HDFS-6634:
--
Summary: inotify in HDFS
Key: HDFS-6634
URL: https://issues.apache.org/jira/browse/HDFS-6634
Project: Hadoop HDFS
Issue Type: New Feature
Components
Colin Patrick McCabe created HDFS-3608:
--
Summary: fuse_dfs: use inotify to detect changes in UID ticket
cache
Key: HDFS-3608
URL: https://issues.apache.org/jira/browse/HDFS-3608
Project: Hadoop
31 matches
Mail list logo
