Hi ASF infrastructure team,
Could you answer the following questions?
* Is it an atomic move? Or will both repos live at the same time?
* Do we need a stop-the-world period and messaging sent out?
* When do the git-wip repos get deleted and/or stop getting updates?
Regards,
Akira
2018年12月14日(金)
Akira Ajisaka created YARN-9122:
---
Summary: Add table of contents to YARN Service API document
Key: YARN-9122
URL: https://issues.apache.org/jira/browse/YARN-9122
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved YARN-8839.
-
Resolution: Fixed
No change the proposed protocol for a while, and this has been implemented for
Agree, it isn't productive this way.
I can't seem to find it, but was there a DISCUSS thread for this branch-merge?
I usually recommend addressing issues on a DISCUSS thread instead of fighting
things over a VOTE.
+Vinod
> On Dec 13, 2018, at 10:09 AM, Konstantin Shvachko
> wrote:
>
> This
Hi Yongjun,
Good suggestion. This is essentially what HDFS-13873 is implementing to
mitigate the concern.
Thanks,
--Konstantin
On Wed, Dec 12, 2018 at 10:35 PM Yongjun Zhang wrote:
> Hi Konstantin,
>
> Thanks for addressing my other question about failover.
>
> Some thought to share about the
This vote failed due to Daryn Sharp's veto.
The concern is being addressed by HDFS-13873. I will start a new vote once
this is committed.
Note for Daryn. Your non-responsive handling of the veto makes a bad
precedence and is a bad example of communication on the lists from a
respected member of
Szilard Nemeth created YARN-9121:
Summary: Users of GpuDiscoverer.getInstance() are not possible to
test as instance is a static field
Key: YARN-9121
URL: https://issues.apache.org/jira/browse/YARN-9121
We need to write up the stages of the process and put a concrete timeline first.
Is it an atomic move? Or will both repos live at the same time? Do we need a
stop-the-world period and messaging sent out?
When do the git-wip repos get deleted and/or stop getting updates?
Things I can think of
On 12/12/18 12:27 PM, Akira Ajisaka wrote:
> Thank you for your positive feedback! I'll file a jira to INFRA in this
> weekend.
>
>> If I understood well the only bigger task here is to update all the jenkins
>> jobs. (I am happy to help/contribute what I can do)
> Thank you Elek for the
Szilard Nemeth created YARN-9120:
Summary: Need to have a way to turn off GPU auto-discovery in
GpuDiscoverer
Key: YARN-9120
URL: https://issues.apache.org/jira/browse/YARN-9120
Project: Hadoop YARN
Szilard Nemeth created YARN-9119:
Summary: Clean up testcase
TestGpuDiscoverer.testLinuxGpuResourceDiscoverPluginConfig
Key: YARN-9119
URL: https://issues.apache.org/jira/browse/YARN-9119
Project:
Szilard Nemeth created YARN-9118:
Summary: Handle issues with parsing user defined GPU devives in
GpuDiscoverer
Key: YARN-9118
URL: https://issues.apache.org/jira/browse/YARN-9118
Project: Hadoop
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/986/
[Dec 12, 2018 8:49:49 AM] (sunilg) YARN-9114. [UI2] log service redirect url
need to support user name.
[Dec 12, 2018 1:16:21 PM] (elek) HDDS-889. MultipartUpload: Support uploading a
part file in ozone.
13 matches
Mail list logo
