timmylicheng commented on a change in pull request #1112:
URL: https://github.com/apache/hadoop-ozone/pull/1112#discussion_r444683525
##
File path:
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/ha/TestSCMRatisRequest.java
##
@@ -0,0 +1,74 @@
+/**
+ * Licensed
timmylicheng commented on a change in pull request #1112:
URL: https://github.com/apache/hadoop-ozone/pull/1112#discussion_r444683471
##
File path:
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/ha/TestSCMRatisRequest.java
##
@@ -0,0 +1,74 @@
+/**
+ * Licensed
[
https://issues.apache.org/jira/browse/HDDS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee reassigned HDDS-3853:
-
Assignee: (was: Shashikant Banerjee)
> Container marked as missing on datanod
[
https://issues.apache.org/jira/browse/HDDS-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee reassigned HDDS-3853:
-
Assignee: Shashikant Banerjee
> Container marked as missing on datanode while con
[
https://issues.apache.org/jira/browse/HDDS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle reassigned HDDS-3486:
-
Assignee: (was: Vivek Ratnavel Subramanian)
> Recon cannot track missing containers t
[
https://issues.apache.org/jira/browse/HDDS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia resolved HDDS-3847.
-
Fix Version/s: 0.6.0
Resolution: Fixed
> Change OMNotLeaderException logging to DEB
[
https://issues.apache.org/jira/browse/HDDS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated HDDS-3851:
Issue Type: Bug (was: Improvement)
> Reduce lock contention in RaftServerImpl::replyPending
[
https://issues.apache.org/jira/browse/HDDS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143498#comment-17143498
]
Jitendra Nath Pandey edited comment on HDDS-3851 at 6/24/20, 4:10 AM:
--
[
https://issues.apache.org/jira/browse/HDDS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143498#comment-17143498
]
Jitendra Nath Pandey commented on HDDS-3851:
cc [~szetszwo]
> Reduce lock con
dineshchitlangia merged pull request #1118:
URL: https://github.com/apache/hadoop-ozone/pull/1118
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
[
https://issues.apache.org/jira/browse/HDDS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh reassigned HDDS-3851:
---
Assignee: Tsz-wo Sze
> Reduce lock contention in RaftServerImpl::replyPendingRequest
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648540995
> So, what is the harm in extending the line limit to 120 characters, when
users can always consume it the way they want to? Wouldn't it be more
accommodative to a
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648540995
> So, what is the harm in extending the line limit to 120 characters, when
users can always consume it the way they want to? Wouldn't it be more
accommodative to a
anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648540995
> So, what is the harm in extending the line limit to 120 characters, when
users can always consume it the way they want to? Wouldn't it be more
accommodative to a wider
maobaolong commented on pull request #:
URL: https://github.com/apache/hadoop-ozone/pull/#issuecomment-648522473
@runzhiwang Thank you for this improvement, it make code more clear and easy
to understand.
This is an
maobaolong commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648521788
+1, it will make Ozone repo clearly.
This is an automated message from the Apache Git Service.
To respon
maobaolong edited a comment on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648490053
@bharatviswa504 Thank you for your reply, can get the debug screenshot from
the related Jira ticket, the result is complete auth header missing, and after
i new t
[
https://issues.apache.org/jira/browse/HDDS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3847:
-
Labels: pull-request-available (was: )
> Change OMNotLeaderException logging to DEBUG
> -
hanishakoneru opened a new pull request #1118:
URL: https://github.com/apache/hadoop-ozone/pull/1118
## What changes were proposed in this pull request?
In a OM HA setup, client tries the OM's in a round robin fashion to find the
leader OM. It is not required to log the retry informa
[
https://issues.apache.org/jira/browse/HDDS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3860:
-
Description:
Right now getServiceInfo is used only for the secure clusters to getCaCert in
maobaolong edited a comment on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648490053
@bharatviswa504 Thank you for your reply, can get the debug screenshot from
the related Jira ticket, the result is complete auth header missing, and after
i new t
[
https://issues.apache.org/jira/browse/HDDS-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3860:
-
Summary: Remove usage of getServiceInfo in RpcClient in non-secure env
(was: Remove usage
Bharat Viswanadham created HDDS-3860:
Summary: Remove usage of getServiceInfo in RpcClient
Key: HDDS-3860
URL: https://issues.apache.org/jira/browse/HDDS-3860
Project: Hadoop Distributed Data Store
bharatviswa504 commented on pull request #1031:
URL: https://github.com/apache/hadoop-ozone/pull/1031#issuecomment-648494388
Thank You @runzhiwang for the contribution and @elek and @xiaoyuyao for the
review.
This is an auto
[
https://issues.apache.org/jira/browse/HDDS-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HDDS-3745.
--
Fix Version/s: 0.6.0
Resolution: Fixed
> Improve OM and SCM performance with 64%
bharatviswa504 edited a comment on pull request #1031:
URL: https://github.com/apache/hadoop-ozone/pull/1031#issuecomment-648492855
Fine with me. In this Jira let's focus on removing datanode part.
I will open a new Jira for removing the usage of getServiceInfo.
+1 LGTM.
bharatviswa504 merged pull request #1031:
URL: https://github.com/apache/hadoop-ozone/pull/1031
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
bharatviswa504 commented on pull request #1031:
URL: https://github.com/apache/hadoop-ozone/pull/1031#issuecomment-648492855
Fine with me. In this Jira let's focus on removing datanode part.
+1 LGTM.
This is an automat
maobaolong commented on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648490053
@bharatviswa504 Thank you for your reply, can get the debug screenshot from
the related Jira ticket, the result is complete auth header missing, and after
i new the ~/.a
vivekratnavel commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648479528
@anuengineer I get your argument that we must be inclusive and the source
code should be readable by visually challenged and
https://accessibility.digital.gov/ recommen
xiaoyuyao commented on pull request #1099:
URL: https://github.com/apache/hadoop-ozone/pull/1099#issuecomment-648471487
bq. Do you know any good tool which can manage the translations (even if
external).
Not as far as I know. How about we generate a md5 of each english document
and
[
https://issues.apache.org/jira/browse/HDDS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao resolved HDDS-3286.
--
Fix Version/s: 0.6.0
Resolution: Fixed
Thanks [~micahzhao] for the contribution and all for the r
[
https://issues.apache.org/jira/browse/HDDS-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDDS-3286:
-
Target Version/s: 0.6.0 (was: 0.7.0)
> BasicOzoneFileSystem support batchDelete
> --
xiaoyuyao merged pull request #814:
URL: https://github.com/apache/hadoop-ozone/pull/814
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to g
xiaoyuyao commented on a change in pull request #1112:
URL: https://github.com/apache/hadoop-ozone/pull/1112#discussion_r444515403
##
File path:
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/ha/TestSCMRatisRequest.java
##
@@ -0,0 +1,74 @@
+/**
+ * Licensed to
xiaoyuyao commented on a change in pull request #1112:
URL: https://github.com/apache/hadoop-ozone/pull/1112#discussion_r444515306
##
File path:
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/ha/TestSCMRatisRequest.java
##
@@ -0,0 +1,74 @@
+/**
+ * Licensed to
xiaoyuyao commented on pull request #814:
URL: https://github.com/apache/hadoop-ozone/pull/814#issuecomment-648430915
Thanks @captainzmc for the update. The latest change LGTM, +1.
This is an automated message from the Apach
xiaoyuyao commented on a change in pull request #1087:
URL: https://github.com/apache/hadoop-ozone/pull/1087#discussion_r444507606
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1583,11 +1583,11 @@ private void checkA
bharatviswa504 commented on pull request #706:
URL: https://github.com/apache/hadoop-ozone/pull/706#issuecomment-648411610
@nilotpalnandi
Please rebase this on top of the latest master, this is targeted for 0.6.0
release, we can get this in once CI and rebase issues are addressed.
---
[
https://issues.apache.org/jira/browse/HDDS-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143292#comment-17143292
]
Xiaoyu Yao commented on HDDS-1714:
--
[~Huachao] I tried om restart with both HA and non-HA
bharatviswa504 commented on pull request #1083:
URL: https://github.com/apache/hadoop-ozone/pull/1083#issuecomment-648409228
My point here is just deleting a column family and assuming everything works
with any incompatible change is wrong.
>This is what we have now. If this were th
bharatviswa504 commented on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648405855
Thank You @maobaolong for the fix and @dineshchitlangia for tagging me.
@maobaolong
>Start a goofy without Authorization related setting.
Can you elabora
bharatviswa504 edited a comment on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648405855
Thank You @maobaolong for the fix and @dineshchitlangia for tagging me.
>Start a goofy without Authorization related setting.
Can you elaborate this s
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 ch
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 ch
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 ch
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 ch
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 ch
cxorm commented on pull request #958:
URL: https://github.com/apache/hadoop-ozone/pull/958#issuecomment-648377207
Rebased latest master-branch (#1109 ) and fixed conflict.
This is an automated message from the Apache Git Serv
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
This is an automated message from the Apache Git Service.
To respond to the message, please log on
anuengineer removed a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375979
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 c
anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375813
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 chars.
anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648375979
> The longest line is 7434 characters long. Even if you remove the
`docker-compose`-specific prefix, which does not appear in real clusters, we
still have 7420 chars.
adoroszlai commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648371279
> Log files generally have no carriage return and therefor formats to
whatever size you want.
Can you please clarify this?
Example log:
```
datanode
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648358212
> I feel we would be better to accept the consensuses rather than veto the
decision, and I would hope Anu would take onboard the direction the community
desires ov
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648358212
> I feel we would be better to accept the consensuses rather than veto the
decision, and I would hope Anu would take onboard the direction the community
desires ov
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648358212
> I feel we would be better to accept the consensuses rather than veto the
decision, and I would hope Anu would take onboard the direction the community
desires ov
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648364625
>https://accessibility.digital.gov/ is about accessible websites
(layout, navigation, etc.). It does not talk about making the source of these
websites accessi
anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648364625
>https://accessibility.digital.gov/ is about accessible websites
(layout, navigation, etc.). It does not talk about making the source of these
websites accessible.
anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648358212
> I feel we would be better to accept the consensuses rather than veto the
decision, and I would hope Anu would take onboard the direction the community
desires over his
anuengineer edited a comment on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648358212
> I feel we would be better to accept the consensuses rather than veto the
decision, and I would hope Anu would take onboard the direction the community
desires ov
[
https://issues.apache.org/jira/browse/HDDS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143222#comment-17143222
]
Attila Doroszlai edited comment on HDDS-3859 at 6/23/20, 7:02 PM:
--
[
https://issues.apache.org/jira/browse/HDDS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143222#comment-17143222
]
Attila Doroszlai commented on HDDS-3859:
[~elek], I would like to propose a new Oz
arp7 commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648338641
+1 for documenting that this is not supported.
This is an automated message from the Apache Git Service.
To re
jnp commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648338154
> Given the fact that it is broken currently, it makes sense to remove the
document saying it is supported.
I agree.
---
Attila Doroszlai created HDDS-3859:
--
Summary: Create docker image for running upgrade steps
Key: HDDS-3859
URL: https://issues.apache.org/jira/browse/HDDS-3859
Project: Hadoop Distributed Data Store
smengcl commented on a change in pull request #1087:
URL: https://github.com/apache/hadoop-ozone/pull/1087#discussion_r05600
##
File path:
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/om/TestOzoneManagerListVolumes.java
##
@@ -146,7 +146,6 @@ private
[
https://issues.apache.org/jira/browse/HDDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDDS-3545:
Labels: (was: TriagePending)
> MR Jobhistory cannot work well with o3fs hadoop compatible file sys
[
https://issues.apache.org/jira/browse/HDDS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143164#comment-17143164
]
Arpit Agarwal commented on HDDS-3545:
-
I see thanks for the link [~maobaolong] and for
elek commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648310628
/pending "Blocking merge ability as we definitely need an agreement first.
Possible topic for Community Meeting."
elek edited a comment on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648309355
> The option to run them in same JVM was allowed, to support in-place
upgrade from HDFS to Ozone in future
@jnp Base on the last design in-place upgrade can work
elek commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648309355
> The option to run them in same JVM was allowed, to support in-place
upgrade from HDFS to Ozone in future
@jnp Base on the last design in-place upgrade can work with di
xiaoyuyao commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648306954
@elek thanks for bringing this up. Given the fact that it is broken
currently, it makes sense to remove the document saying it is supported. Let's
open a separate JIRA to
bshashikant commented on pull request #1083:
URL: https://github.com/apache/hadoop-ozone/pull/1083#issuecomment-648289443
I agree with @elek here.
This is an automated message from the Apache Git Service.
To respond to the me
jnp commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648287597
The option to run them in same JVM was allowed, to support in-place upgrade
from HDFS to Ozone in future. It was assumed that having the two Datanodes in
the same JVM will cert
[
https://issues.apache.org/jira/browse/HDDS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143111#comment-17143111
]
Jitendra Nath Pandey commented on HDDS-3858:
The option to run them in same JV
dineshchitlangia edited a comment on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648265724
This is a double edged sword :)
Some of my customers that I speak to have indicated they would not directly
go to Ozone in an independent fashion and a f
dineshchitlangia commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648265724
This is a double edged sword :)
Some of my customers that I speak to have indicated they would not directly
go to Ozone in an independent fashion and a few of t
elek commented on pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117#issuecomment-648247605
Ping everybody (especially @jnp @arp7 @xiaoyuyao @mukul1987 @nandakumar131 )
This is an automated message from
[
https://issues.apache.org/jira/browse/HDDS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3858:
-
Labels: pull-request-available (was: )
> Remove support to start Ozone and HDFS datanodes in the
elek opened a new pull request #1117:
URL: https://github.com/apache/hadoop-ozone/pull/1117
## What changes were proposed in this pull request?
With a few thousands issues ago Ozone was integral part of Hadoop/HDFS
project. At that time there were two options to start datanode:
Marton Elek created HDDS-3858:
-
Summary: Remove support to start Ozone and HDFS datanodes in the
same JVM
Key: HDDS-3858
URL: https://issues.apache.org/jira/browse/HDDS-3858
Project: Hadoop Distributed Da
[
https://issues.apache.org/jira/browse/HDDS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3857:
-
Labels: pull-request-available (was: )
> Datanode in compose/ozonescripts can't be started
> ---
elek opened a new pull request #1116:
URL: https://github.com/apache/hadoop-ozone/pull/1116
## What changes were proposed in this pull request?
Datanode in compose/ozonscripts can't be started due to an old configuration
(OzoneHddsDatanodeService is removed in HDDS-738)
## Wha
Marton Elek created HDDS-3857:
-
Summary: Datanode in compose/ozonescripts can't be started
Key: HDDS-3857
URL: https://issues.apache.org/jira/browse/HDDS-3857
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3632:
-
Labels: Triaged newbie pull-request-available (was: Triaged newbie)
> HddsDatanodeService cannot
elek opened a new pull request #1115:
URL: https://github.com/apache/hadoop-ozone/pull/1115
…
since the service names are same and they both referring to same location
for pid files, we can not start both services at once.
Tweak is to export HADOOP_PID_DIR to different location af
[
https://issues.apache.org/jira/browse/HDDS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek reassigned HDDS-1127:
-
Assignee: (was: Marton Elek)
> Fix failing and intermittent Ozone unit tests
> --
[
https://issues.apache.org/jira/browse/HDDS-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek resolved HDDS-1157.
---
Resolution: Cannot Reproduce
> TestOzoneContainerWithTLS is failing due to the missing native librarie
dineshchitlangia commented on pull request #1110:
URL: https://github.com/apache/hadoop-ozone/pull/1110#issuecomment-648216389
@bharatviswa504 Could you review this? The change itself is very simple
however I am not a fan of eliminating the PreCondition checks. Your thoughts
are appreciate
Ethan Rose created HDDS-3856:
Summary: Add DatanodeDBDefinition to define structure of
*-dn-container.db
Key: HDDS-3856
URL: https://issues.apache.org/jira/browse/HDDS-3856
Project: Hadoop Distributed Dat
[
https://issues.apache.org/jira/browse/HDDS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek resolved HDDS-2695.
---
Resolution: Cannot Reproduce
> SCM is not able to start under certain conditions
> ---
[
https://issues.apache.org/jira/browse/HDDS-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142997#comment-17142997
]
Marton Elek commented on HDDS-2695:
---
{quote}I am open to close this issue
{quote}
Sure.
[
https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142996#comment-17142996
]
Marton Elek commented on HDDS-3354:
---
Moved the target.version=0.6.0 flag to the sub issu
[
https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-3354:
--
Target Version/s: (was: 0.6.0)
> OM HA replay optimization
> -
>
>
[
https://issues.apache.org/jira/browse/HDDS-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-3685:
--
Target Version/s: 0.6.0
> Remove replay logic from actual request logic
> --
[
https://issues.apache.org/jira/browse/HDDS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-3342:
--
Target Version/s: 0.7.0 (was: 0.6.0)
> Ozone admin shell commands do not print or log exceptions on fai
[
https://issues.apache.org/jira/browse/HDDS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142992#comment-17142992
]
Marton Elek commented on HDDS-3342:
---
Thanks to report this problem [~vivekratnavel]
Ca
[
https://issues.apache.org/jira/browse/HDDS-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142979#comment-17142979
]
Marton Elek commented on HDDS-2871:
---
Tested with docker-compose based cluster and worked
[
https://issues.apache.org/jira/browse/HDDS-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-2871:
--
Target Version/s: 0.7.0 (was: 0.6.0)
> Ozone documentation redirection in S3 Gateway webpage doesn't wo
1 - 100 of 170 matches
Mail list logo
