[jira] [Commented] (HADOOP-16350) Ability to tell Hadoop not to request KMS Information from Remote NN

[ https://issues.apache.org/jira/browse/HADOOP-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863505#comment-16863505 ] Tsz Wo Nicholas Sze commented on HADOOP-16350: -- {code} hadoop distcp

[jira] [Commented] (HADOOP-16350) Ability to tell Hadoop not to request KMS Information from Remote NN

[ https://issues.apache.org/jira/browse/HADOOP-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862537#comment-16862537 ] Tsz Wo Nicholas Sze commented on HADOOP-16350: -- > ... Please provide more details on how

[jira] [Assigned] (HADOOP-16350) Ability to tell Hadoop not to request KMS Information from Remote NN

[ https://issues.apache.org/jira/browse/HADOOP-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze reassigned HADOOP-16350: Assignee: Greg Senia > Ability to tell Hadoop not to request KMS

[jira] [Commented] (HADOOP-16350) Ability to tell Hadoop not to request KMS Information from Remote NN

[ https://issues.apache.org/jira/browse/HADOOP-16350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861658#comment-16861658 ] Tsz Wo Nicholas Sze commented on HADOOP-16350: -- [~gss2002], thanks for filing the JIRA and

[jira] [Commented] (HADOOP-15720) rpcTimeout may not have been applied correctly

[ https://issues.apache.org/jira/browse/HADOOP-15720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783807#comment-16783807 ] Tsz Wo Nicholas Sze commented on HADOOP-15720: -- Hi [~yzhangal], if the bug is no rpc

[jira] [Commented] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779887#comment-16779887 ] Tsz Wo Nicholas Sze commented on HADOOP-16126: -- Thanks [~tasanuma0829]. For this

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.3.0

[jira] [Commented] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16778681#comment-16778681 ] Tsz Wo Nicholas Sze commented on HADOOP-16127: -- Since the 25.patch only has whitespace

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: c16127_20190225.patch > In ipc.Client, put a new connection could

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: (was: c16127_20190225.patch) > In ipc.Client, put a new

[jira] [Commented] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777301#comment-16777301 ] Tsz Wo Nicholas Sze commented on HADOOP-16127: -- c16127_20190225.patch: fixes checkstyle

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: c16127_20190225.patch > In ipc.Client, put a new connection could

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Target Version/s: 3.3.0 (was: 3.1.2) > Just have set target version to 3.1.2.

[jira] [Updated] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16126: - Resolution: Fixed Fix Version/s: 3.3.0 Status: Resolved

[jira] [Commented] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774614#comment-16774614 ] Tsz Wo Nicholas Sze commented on HADOOP-16127: -- [~ste...@apache.org], thanks for reviewing

[jira] [Updated] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16126: - Attachment: c16126_20190221.patch > ipc.Client.stop() may sleep too long to

[jira] [Commented] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773522#comment-16773522 ] Tsz Wo Nicholas Sze commented on HADOOP-16127: -- > L475: include the toString value of the

[jira] [Commented] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773525#comment-16773525 ] Tsz Wo Nicholas Sze commented on HADOOP-16126: -- c16126_20190220.patch: address

[jira] [Commented] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773526#comment-16773526 ] Tsz Wo Nicholas Sze commented on HADOOP-16127: -- > ps: set your version info for where you

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Target Version/s: 3.1.2 > In ipc.Client, put a new connection could happen

[jira] [Updated] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16126: - Attachment: c16126_20190220.patch > ipc.Client.stop() may sleep too long to

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: c16127_20190220.patch > In ipc.Client, put a new connection could

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: (was: c16127_20190220.patch) > In ipc.Client, put a new

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: c16127_20190220.patch > In ipc.Client, put a new connection could

[jira] [Commented] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773424#comment-16773424 ] Tsz Wo Nicholas Sze commented on HADOOP-16126: -- > Why the choice of 10ms? It is because

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Status: Patch Available (was: Open) > In ipc.Client, put a new connection

[jira] [Updated] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

[ https://issues.apache.org/jira/browse/HADOOP-16127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16127: - Attachment: c16127_20190219.patch > In ipc.Client, put a new connection could

[jira] [Commented] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772465#comment-16772465 ] Tsz Wo Nicholas Sze commented on HADOOP-16126: -- Filed HADOOP-16127. > ipc.Client.stop()

[jira] [Created] (HADOOP-16127) In ipc.Client, put a new connection could happen after stop

Tsz Wo Nicholas Sze created HADOOP-16127: Summary: In ipc.Client, put a new connection could happen after stop Key: HADOOP-16127 URL: https://issues.apache.org/jira/browse/HADOOP-16127

[jira] [Updated] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16126: - Status: Patch Available (was: Open) > ipc.Client.stop() may sleep too long to

[jira] [Updated] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-16126: - Attachment: c16126_20190219.patch > ipc.Client.stop() may sleep too long to

[jira] [Commented] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

[ https://issues.apache.org/jira/browse/HADOOP-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772452#comment-16772452 ] Tsz Wo Nicholas Sze commented on HADOOP-16126: -- Tried to change the sleep to wait-notify.

[jira] [Created] (HADOOP-16126) ipc.Client.stop() may sleep too long to wait for all connections

Tsz Wo Nicholas Sze created HADOOP-16126: Summary: ipc.Client.stop() may sleep too long to wait for all connections Key: HADOOP-16126 URL: https://issues.apache.org/jira/browse/HADOOP-16126

[jira] [Commented] (HADOOP-15857) Remove ozonefs class name definition from core-default.xml

[ https://issues.apache.org/jira/browse/HADOOP-15857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651516#comment-16651516 ] Tsz Wo Nicholas Sze commented on HADOOP-15857: -- +1 the patch looks good. > Remove ozonefs

[jira] [Commented] (HADOOP-15725) FileSystem.deleteOnExit should check user permissions

[ https://issues.apache.org/jira/browse/HADOOP-15725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609663#comment-16609663 ] Tsz Wo Nicholas Sze commented on HADOOP-15725: -- [~oshevchenko], thanks for testing it. We

[jira] [Commented] (HADOOP-15725) FileSystem.deleteOnExit should check user permissions

[ https://issues.apache.org/jira/browse/HADOOP-15725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609656#comment-16609656 ] Tsz Wo Nicholas Sze commented on HADOOP-15725: -- [~vinayrpet] is right. We should call

[jira] [Commented] (HADOOP-15725) FileSystem.deleteOnExit should check user permissions

[ https://issues.apache.org/jira/browse/HADOOP-15725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609551#comment-16609551 ] Tsz Wo Nicholas Sze commented on HADOOP-15725: -- bq. root@node:/# hadoop fs -chmod 700

[jira] [Commented] (HADOOP-14854) DistCp should not issue file status calls for files in the filter list

[ https://issues.apache.org/jira/browse/HADOOP-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548264#comment-16548264 ] Tsz Wo Nicholas Sze commented on HADOOP-14854: -- The shouldCopy(..) should be invoked

[jira] [Commented] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388619#comment-16388619 ] Tsz Wo Nicholas Sze commented on HADOOP-14453: -- [~ste...@apache.org], your command works

[jira] [Commented] (HADOOP-14655) Update httpcore version to 4.4.6

[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177631#comment-16177631 ] Tsz Wo Nicholas Sze commented on HADOOP-14655: -- [~elek], thanks a lot for figuring out the

[jira] [Commented] (HADOOP-14655) Update httpcore version to 4.4.6

[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172915#comment-16172915 ] Tsz Wo Nicholas Sze commented on HADOOP-14655: -- The error disappears after reverting the

[jira] [Commented] (HADOOP-14655) Update httpcore version to 4.4.6

[ https://issues.apache.org/jira/browse/HADOOP-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172910#comment-16172910 ] Tsz Wo Nicholas Sze commented on HADOOP-14655: -- It seems that this causes HDFS-12507. >

[jira] [Commented] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027324#comment-16027324 ] Tsz Wo Nicholas Sze commented on HADOOP-14453: -- > ... its what the --pl command does. It

[jira] [Commented] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024057#comment-16024057 ] Tsz Wo Nicholas Sze commented on HADOOP-14453: -- > For the once-per-day cost? ... Why

[jira] [Commented] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023794#comment-16023794 ] Tsz Wo Nicholas Sze commented on HADOOP-14453: -- {{mvn install -DskipTests}} seems taking a

[jira] [Updated] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-14453: - Status: Patch Available (was: Open) > Split the maven modules into several

[jira] [Updated] (HADOOP-14453) Split the maven modules into several profiles

[ https://issues.apache.org/jira/browse/HADOOP-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-14453: - Attachment: c14453_20170524.patch c14453_20170524.patch: splits the modules

[jira] [Created] (HADOOP-14453) Split the maven modules into several profiles

Tsz Wo Nicholas Sze created HADOOP-14453: Summary: Split the maven modules into several profiles Key: HADOOP-14453 URL: https://issues.apache.org/jira/browse/HADOOP-14453 Project: Hadoop

[jira] [Commented] (HADOOP-14405) Fix performance regression due to incorrect use of DataChecksum

[ https://issues.apache.org/jira/browse/HADOOP-14405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005106#comment-16005106 ] Tsz Wo Nicholas Sze commented on HADOOP-14405: -- Thanks [~GeLiXin] for the contribution and

[jira] [Commented] (HADOOP-14217) Object Storage: support colon in object path

[ https://issues.apache.org/jira/browse/HADOOP-14217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965236#comment-15965236 ] Tsz Wo Nicholas Sze commented on HADOOP-14217: -- Yes, we should fix it. We probably should

[jira] [Commented] (HADOOP-14084) Shell.joinThread swallows InterruptedException

[ https://issues.apache.org/jira/browse/HADOOP-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946462#comment-15946462 ] Tsz Wo Nicholas Sze commented on HADOOP-14084: -- We need to decide what is the expected

[jira] [Commented] (HADOOP-14217) Object Storage: support colon in object path

[ https://issues.apache.org/jira/browse/HADOOP-14217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941070#comment-15941070 ] Tsz Wo Nicholas Sze commented on HADOOP-14217: -- Unable to support ':' is a long standing

[jira] [Updated] (HADOOP-10101) Update guava dependency to the latest version

[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-10101: - Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) +1 the

[jira] [Commented] (HADOOP-14214) DomainSocketWatcher::add()/delete() should not self interrupt while looping await()

[ https://issues.apache.org/jira/browse/HADOOP-14214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939179#comment-15939179 ] Tsz Wo Nicholas Sze commented on HADOOP-14214: -- The

[jira] [Commented] (HADOOP-10101) Update guava dependency to the latest version

[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938962#comment-15938962 ] Tsz Wo Nicholas Sze commented on HADOOP-10101: -- Patch looks good. Thanks for working on

[jira] [Commented] (HADOOP-10101) Update guava dependency to the latest version

[ https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923348#comment-15923348 ] Tsz Wo Nicholas Sze commented on HADOOP-10101: -- > I think it is high time we bump up the

[jira] [Issue Comment Deleted] (HADOOP-5052) Add an example for computing exact digits of Pi

[ https://issues.apache.org/jira/browse/HADOOP-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-5052: Comment: was deleted (was: Very useful example visit here for more information.

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use an event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Resolution: Fixed Fix Version/s: 2.8.0 Status: Resolved (was:

[jira] [Updated] (HADOOP-13249) RetryInvocationHandler need wrap InterruptedException in IOException when call Thread.sleep

[ https://issues.apache.org/jira/browse/HADOOP-13249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13249: - Fix Version/s: (was: 2.9.0) 2.8.0 Merged this to

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use an event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Hadoop Flags: Reviewed Summary: AsyncCallHandler should use an event

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160624.patch c13227_20160624.patch: fixes a compilation

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160621.patch c13227_20160621.patch: sync'ed with trunk. >

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160616.patch c13227_20160616.patch: sync'ed with trunk. >

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323775#comment-15323775 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- Chaining/callbacks are nonessential in the

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322273#comment-15322273 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- After some thought, copying CompletionStage

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1531#comment-1531 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- Sorry, please forgive my bad wording. I

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320902#comment-15320902 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- Some other ideas: # Use ListenableFuture.

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320839#comment-15320839 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- > Why the insistence on doing the async

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160608b.patch c13227_20160608b.patch: checkEmpty() should

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160608.patch c13227_20160608.patch: - uses RetryDecision

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15318065#comment-15318065 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- > One of the key things that Deferred and

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15318041#comment-15318041 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- > As to your FutureWithCallback, where does

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317739#comment-15317739 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- It seems we all agree that we should use

[jira] [Commented] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317646#comment-15317646 ] Tsz Wo Nicholas Sze commented on HADOOP-13227: -- > Can we use ConcurrentLinkedQueue's

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160607.patch > AsyncCallHandler should use a event driven

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160606.patch > In RetryInfo#newRetryInfo, looks like

[jira] [Updated] (HADOOP-13226) Support async call retry and failover

[ https://issues.apache.org/jira/browse/HADOOP-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13226: - Fix Version/s: (was: HDFS-9924) 2.8.0 > Support async

[jira] [Updated] (HADOOP-12957) Limit the number of outstanding async calls

[ https://issues.apache.org/jira/browse/HADOOP-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-12957: - Fix Version/s: (was: HDFS-9924) 2.8.0 > Limit the number

[jira] [Updated] (HADOOP-13168) Support Future.get with timeout in ipc async calls

[ https://issues.apache.org/jira/browse/HADOOP-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13168: - Fix Version/s: (was: HDFS-9924) 2.8.0 > Support

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Status: Patch Available (was: In Progress) > AsyncCallHandler should use a

[jira] [Work started] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-13227 started by Tsz Wo Nicholas Sze. > AsyncCallHandler should use a event driven architecture to

[jira] [Work started] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-13227 started by Tsz Wo Nicholas Sze. > AsyncCallHandler should use a event driven architecture to

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Attachment: c13227_20160602.patch c13227_20160602.patch: uses an event driven

[jira] [Work stopped] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-13227 stopped by Tsz Wo Nicholas Sze. > AsyncCallHandler should use a event driven architecture to

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Description: This JIRA is to address [Jing

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Description: This JIRA is to address [Jing's

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Description: This JIRA is to address Jing comments in HADOOP-13226. >

[jira] [Issue Comment Deleted] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - Comment: was deleted (was: This JIRA is to address [Jing

[jira] [Updated] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

[ https://issues.apache.org/jira/browse/HADOOP-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13227: - This JIRA is to address [Jing

[jira] [Created] (HADOOP-13227) AsyncCallHandler should use a event driven architecture to handle async calls

Tsz Wo Nicholas Sze created HADOOP-13227: Summary: AsyncCallHandler should use a event driven architecture to handle async calls Key: HADOOP-13227 URL: https://issues.apache.org/jira/browse/HADOOP-13227

[jira] [Updated] (HADOOP-13226) Support async call retry and failover

[ https://issues.apache.org/jira/browse/HADOOP-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13226: - Resolution: Fixed Fix Version/s: 2.8.0 Status: Resolved (was:

[jira] [Updated] (HADOOP-13146) Refactor RetryInvocationHandler

[ https://issues.apache.org/jira/browse/HADOOP-13146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13146: - Fix Version/s: (was: 2.9.0) 2.8.0 Merged to 2.8. >

[jira] [Updated] (HADOOP-13226) Support async call retry and failover

[ https://issues.apache.org/jira/browse/HADOOP-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13226: - Summary: Support async call retry and failover (was: Make retry also works

[jira] [Moved] (HADOOP-13226) Make retry also works well for Async DFS

[ https://issues.apache.org/jira/browse/HADOOP-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze moved HDFS-10433 to HADOOP-13226: - Component/s: (was: hdfs) ipc

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306059#comment-15306059 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- It seems that people really want Future

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306058#comment-15306058 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- It would be less work if we could

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303008#comment-15303008 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- > Can we introduce our own ListenableFuture

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302850#comment-15302850 ] Tsz Wo Nicholas Sze commented on HADOOP-12910: -- Okay, let's replay it. > ... . It's not

[jira] [Updated] (HADOOP-13168) Support Future.get with timeout in ipc async calls

[ https://issues.apache.org/jira/browse/HADOOP-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13168: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0

[jira] [Updated] (HADOOP-13168) Support Future.get with timeout in ipc async calls

[ https://issues.apache.org/jira/browse/HADOOP-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HADOOP-13168: - Attachment: c13168_20160519.patch c13168_20160519.patch: address Xiaobing's

  1   2   3   4   5   6   7   8   9   10   >