[jira] [Created] (HDDS-4392) Add Recon architecture to docs
Vivek Ratnavel Subramanian created HDDS-4392: Summary: Add Recon architecture to docs Key: HDDS-4392 URL: https://issues.apache.org/jira/browse/HDDS-4392 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 1.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Recon Architecture and details are missing in the docs - https://ci-hadoop.apache.org/view/Hadoop%20Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/concept/ozonemanager.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4348) Performance evaluation for Ozone trash emptier
[ https://issues.apache.org/jira/browse/HDDS-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4348: - Description: Current trash removal is leveraging HDFS trash removal. This subtask can be used to evaluate performance impact. specifically, evaluate * key removal in presence of a large number of buckets vs few buckets * key removal in presence of a large number of keys vs few keys was: Current trash removal is leveraging HDFS trash removal. This subtrask can be used to evaluate performance impact. specifically evaluate * key removal in presence of large number of buckets vs few buckets * key removal in presence of large number of keys vs few keys > Performance evaluation for Ozone trash emptier > -- > > Key: HDDS-4348 > URL: https://issues.apache.org/jira/browse/HDDS-4348 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Prashant Pogde >Assignee: Sadanand Shenoy >Priority: Major > > Current trash removal is leveraging HDFS trash removal. This subtask can be > used to evaluate performance impact. > specifically, evaluate > * key removal in presence of a large number of buckets vs few buckets > * key removal in presence of a large number of keys vs few keys -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4348) Performance evaluation for Ozone trash emptier
[ https://issues.apache.org/jira/browse/HDDS-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4348: - Summary: Performance evaluation for Ozone trash emptier (was: Perf evaluation fopr Ozone trash emptier) > Performance evaluation for Ozone trash emptier > -- > > Key: HDDS-4348 > URL: https://issues.apache.org/jira/browse/HDDS-4348 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Prashant Pogde >Assignee: Sadanand Shenoy >Priority: Major > > Current trash removal is leveraging HDFS trash removal. This subtrask can be > used to evaluate performance impact. > specifically evaluate > * key removal in presence of large number of buckets vs few buckets > * key removal in presence of large number of keys vs few keys -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4301) SCM CA certificate does not encode KeyUsage extension properly
[
https://issues.apache.org/jira/browse/HDDS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-4301:
-
Summary: SCM CA certificate does not encode KeyUsage extension properly
(was: SCM CA certificate does not encode KeyUsage extension propertly)
> SCM CA certificate does not encode KeyUsage extension properly
> --
>
> Key: HDDS-4301
> URL: https://issues.apache.org/jira/browse/HDDS-4301
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Security
>Affects Versions: 1.0.0
>Reporter: Xiaoyu Yao
>Assignee: Xiaoyu Yao
>Priority: Major
> Labels: pull-request-available
>
> This could be problematic with strict security provider such as FIPS. The
> default non-FIPS provider such as SunJCE and BC provider work fine though.
> This ticket is opened to fix it.
> {code:java}
> 2020-09-30 12:01:52,962 ERROR
> org.apache.hadoop.hdds.security.x509.certificate.authority.DefaultCAServer:
> Unable to initialize CertificateServer.
> org.apache.hadoop.hdds.security.exception.SCMSecurityException:
> java.security.cert.CertificateParsingException: cannot construct KeyUsage:
> java.lang.IllegalArgumentException: illegal object in getInstance:
> com.safelogic.cryptocomply.asn1.DEROctetString
> at
> org.apache.hadoop.hdds.security.x509.certificate.utils.CertificateCodec.getPEMEncodedString(CertificateCodec.java:105)
> at
> org.apache.hadoop.hdds.security.x509.certificate.utils.CertificateCodec.writeCertificate(CertificateCodec.java:182)
> at
> org.apache.hadoop.hdds.security.x509.certificate.authority.DefaultCAServer.generateRootCertificate(DefaultCAServer.java:495)
> at
> org.apache.hadoop.hdds.security.x509.certificate.authority.DefaultCAServer.generateSelfSignedCA(DefaultCAServer.java:303)
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4309) Fix inconsistent Recon config keys that start with "recon.om."
[
https://issues.apache.org/jira/browse/HDDS-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian resolved HDDS-4309.
--
Fix Version/s: 1.1.0
Resolution: Fixed
> Fix inconsistent Recon config keys that start with "recon.om."
> --
>
> Key: HDDS-4309
> URL: https://issues.apache.org/jira/browse/HDDS-4309
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
>Affects Versions: 1.0.0
>Reporter: Aravindan Vijayan
>Assignee: François Risch
>Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 1.1.0
>
>
> {code}
> hadoop-hdds/common/src/main/resources/ozone-default.xml
> 2318:recon.om.connection.request.timeout
> 2327:recon.om.connection.timeout
> 2336:recon.om.socket.timeout
> 2345:recon.om.snapshot.task.initial.delay
> 2353:recon.om.snapshot.task.interval.delay
> 2361:recon.om.snapshot.task.flush.param
> {code}
> These need to be deprecated and changed to "ozone.recon.om.<>".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4316) Upgrade to angular 1.8.0 due to CVE-2020-7676
[ https://issues.apache.org/jira/browse/HDDS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4316: - Status: Patch Available (was: Open) > Upgrade to angular 1.8.0 due to CVE-2020-7676 > - > > Key: HDDS-4316 > URL: https://issues.apache.org/jira/browse/HDDS-4316 > Project: Hadoop Distributed Data Store > Issue Type: Task >Affects Versions: 1.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Angular versions < 1.8.0 are vulnerable to cross-site scripting > [https://nvd.nist.gov/vuln/detail/CVE-2020-7676] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4316) Upgrade to angular 1.8.0 due to CVE-2020-7676
Vivek Ratnavel Subramanian created HDDS-4316: Summary: Upgrade to angular 1.8.0 due to CVE-2020-7676 Key: HDDS-4316 URL: https://issues.apache.org/jira/browse/HDDS-4316 Project: Hadoop Distributed Data Store Issue Type: Task Affects Versions: 1.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Angular versions < 1.8.0 are vulnerable to cross-site scripting [https://nvd.nist.gov/vuln/detail/CVE-2020-7676] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4292) OMFailoverProxyProvider.createOMProxyIfNeeded should return a new proxy instance for Hadoop < 3.2
Vivek Ratnavel Subramanian created HDDS-4292:
Summary: OMFailoverProxyProvider.createOMProxyIfNeeded should
return a new proxy instance for Hadoop < 3.2
Key: HDDS-4292
URL: https://issues.apache.org/jira/browse/HDDS-4292
Project: Hadoop Distributed Data Store
Issue Type: Bug
Components: Ozone Manager
Affects Versions: 1.0.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Bharat Viswanadham
HDDS-3560 created new ProxyInfo object in case of IllegalAccessError exception.
But, it does not return the new instance and causes NPE in Hadoop versions < 3.2
{code:java}
20/09/29 23:10:22 ERROR client.OzoneClientFactory: Couldn't create RpcClient
protocol exception:20/09/29 23:10:22 ERROR client.OzoneClientFactory: Couldn't
create RpcClient protocol exception:java.lang.NullPointerException at
org.apache.hadoop.io.retry.RetryInvocationHandler.isRpcInvocation(RetryInvocationHandler.java:435)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:354)
at com.sun.proxy.$Proxy10.submitRequest(Unknown Source) at
org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransport.submitRequest(Hadoop3OmTransport.java:89)
at
org.apache.hadoop.ozone.om.protocolPB.OzoneManagerProtocolClientSideTranslatorPB.submitRequest(OzoneManagerProtocolClientSideTranslatorPB.java:213)
at
org.apache.hadoop.ozone.om.protocolPB.OzoneManagerProtocolClientSideTranslatorPB.getServiceInfo(OzoneManagerProtocolClientSideTranslatorPB.java:1030)
at org.apache.hadoop.ozone.client.rpc.RpcClient.(RpcClient.java:175) at
org.apache.hadoop.ozone.client.OzoneClientFactory.getClientProtocol(OzoneClientFactory.java:242)
at
org.apache.hadoop.ozone.client.OzoneClientFactory.getRpcClient(OzoneClientFactory.java:113)
at
org.apache.hadoop.fs.ozone.BasicOzoneClientAdapterImpl.(BasicOzoneClientAdapterImpl.java:149)
at
org.apache.hadoop.fs.ozone.OzoneClientAdapterImpl.(OzoneClientAdapterImpl.java:51)
at
org.apache.hadoop.fs.ozone.OzoneFileSystem.createAdapter(OzoneFileSystem.java:94)
at
org.apache.hadoop.fs.ozone.BasicOzoneFileSystem.initialize(BasicOzoneFileSystem.java:161)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3288) at
org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123) at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3337) at
org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3305) at
org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476) at
org.apache.hadoop.fs.Path.getFileSystem(Path.java:361) at
org.apache.hadoop.fs.shell.PathData.expandAsGlob(PathData.java:352) at
org.apache.hadoop.fs.shell.Command.expandArgument(Command.java:250) at
org.apache.hadoop.fs.shell.Command.expandArguments(Command.java:233) at
org.apache.hadoop.fs.shell.FsCommand.processRawArguments(FsCommand.java:103) at
org.apache.hadoop.fs.shell.Command.run(Command.java:177) at
org.apache.hadoop.fs.FsShell.run(FsShell.java:326) at
org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) at
org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) at
org.apache.hadoop.fs.FsShell.main(FsShell.java:389)ls: Couldn't create
RpcClient protocol
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4261) Recon should display Top N folders for each file size range
Vivek Ratnavel Subramanian created HDDS-4261: Summary: Recon should display Top N folders for each file size range Key: HDDS-4261 URL: https://issues.apache.org/jira/browse/HDDS-4261 Project: Hadoop Distributed Data Store Issue Type: New Feature Components: Ozone Recon Affects Versions: 1.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Recon should have the ability to locate small files in a cluster. Keeping a list of Top N folders within each file size range is one way to achieve this. 4mb - 8mb /vol1/bucket1/p1/p2: 156 keys (40%) /vol1/bucket1/p1/p3: 97 keys (25%) 64mb - 128mb /vol1/bucket2/p11/p0: 450 keys (90%) /vol1/bucket2/p11/p1/p2: 25 keys (5%) 256mb - 512mb /vol2/bucket1/p2: 70 keys (100%) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4196) Add an endpoint in Recon to query Prometheus
[ https://issues.apache.org/jira/browse/HDDS-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-4196. -- Resolution: Fixed > Add an endpoint in Recon to query Prometheus > > > Key: HDDS-4196 > URL: https://issues.apache.org/jira/browse/HDDS-4196 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 1.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Recon should have an endpoint to proxy requests to the configured prometheus > instance. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4150) recon.api.TestEndpoints is flaky
[ https://issues.apache.org/jira/browse/HDDS-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-4150. -- Resolution: Fixed > recon.api.TestEndpoints is flaky > > > Key: HDDS-4150 > URL: https://issues.apache.org/jira/browse/HDDS-4150 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Marton Elek >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Labels: pull-request-available > > Failed on the PR: > https://github.com/apache/hadoop-ozone/pull/1349 > And on the master: > https://github.com/elek/ozone-build-results/blob/master/2020/08/25/2533/unit/hadoop-ozone/recon/org.apache.hadoop.ozone.recon.api.TestEndpoints.txt > and here: > https://github.com/elek/ozone-build-results/blob/master/2020/08/22/2499/unit/hadoop-ozone/recon/org.apache.hadoop.ozone.recon.api.TestEndpoints.txt -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4208) Fix table rendering and logo display in docs
[ https://issues.apache.org/jira/browse/HDDS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-4208. -- Fix Version/s: 1.0.1 Resolution: Fixed > Fix table rendering and logo display in docs > > > Key: HDDS-4208 > URL: https://issues.apache.org/jira/browse/HDDS-4208 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: documentation >Affects Versions: 1.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > Attachments: Screen Shot 2020-09-03 at 2.17.50 PM.png > > > The Docs page does not render the table correctly in OM and SCM architecture > pages. > Also, the ozone logo in the header is not visible. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4208) Fix table rendering and logo display in docs
Vivek Ratnavel Subramanian created HDDS-4208: Summary: Fix table rendering and logo display in docs Key: HDDS-4208 URL: https://issues.apache.org/jira/browse/HDDS-4208 Project: Hadoop Distributed Data Store Issue Type: Bug Components: documentation Affects Versions: 1.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Attachments: Screen Shot 2020-09-03 at 2.17.50 PM.png The Docs page does not render the table correctly in OM and SCM architecture pages. Also, the ozone logo in the header is not visible. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-4205) Fix or disable coverage upload to codecov (pull requests)
[
https://issues.apache.org/jira/browse/HDDS-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190344#comment-17190344
]
Vivek Ratnavel Subramanian commented on HDDS-4205:
--
I agree with you both. We can upload coverage data only from branch builds and
not PR's. Thanks for working on this [~elek]!
> Fix or disable coverage upload to codecov (pull requests)
> -
>
> Key: HDDS-4205
> URL: https://issues.apache.org/jira/browse/HDDS-4205
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
>Reporter: Marton Elek
>Assignee: Marton Elek
>Priority: Major
>
> I would like to start a conversation about disabling the coverage data
> uploading to codecov
> 1. It seems to be unreliable, HTTP 400 is a very common answer. I checked
> and the @v1 is the latest version from the action
> {code}
> -> Pinging Codecov
> https://codecov.io/upload/v4?package=bash-20200825-997b141=secret=HDDS-4193=361ddccd0666a8bd24240cda2652a903d4b69013=237476928_url=http%3A%2F%2Fgithub.com%2Fapache%2Fhadoop-ozone%2Factions%2Fruns%2F237476928=codecov-umbrella==apache%2Fhadoop-ozone=github-actions==1384=_args=f,n,F,Z
> HTTP 400
> {code}
> 2. The reported coverage data is meaningless as there is no good mechanism
> to use the latest stable build as baseline.
> I think we should disable codecov (sonar is still available) until we will
> have a solution for these issue.
> [~adoroszlai], [~vivekratnavel]: What do you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4196) Add an endpoint in Recon to query Prometheus
Vivek Ratnavel Subramanian created HDDS-4196: Summary: Add an endpoint in Recon to query Prometheus Key: HDDS-4196 URL: https://issues.apache.org/jira/browse/HDDS-4196 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 1.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Recon should have an endpoint to proxy requests to the configured prometheus instance. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4051) Remove whitelist/blacklist terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-4051. -- Target Version/s: 0.7.0 Resolution: Fixed > Remove whitelist/blacklist terminology from Ozone > - > > Key: HDDS-4051 > URL: https://issues.apache.org/jira/browse/HDDS-4051 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4091) Report non-inclusive language as part of code contribution pre-commit check
Vivek Ratnavel Subramanian created HDDS-4091: Summary: Report non-inclusive language as part of code contribution pre-commit check Key: HDDS-4091 URL: https://issues.apache.org/jira/browse/HDDS-4091 Project: Hadoop Distributed Data Store Issue Type: Sub-task Affects Versions: 0.6.0 Reporter: Vivek Ratnavel Subramanian Also, as part of this Jira we can include running checkstyle.sh as part of the pre-commit hook to help developers follow Ozone's coding standards. We can also explore if it is possible to add this non-inclusive language check as part of checkstyle.sh -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4009) Recon Overview page: The volume, bucket and key counts are not accurate
[ https://issues.apache.org/jira/browse/HDDS-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4009: - Status: Patch Available (was: Open) > Recon Overview page: The volume, bucket and key counts are not accurate > --- > > Key: HDDS-4009 > URL: https://issues.apache.org/jira/browse/HDDS-4009 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > The counts shown in the overview page are not accurate due to the usage of > "rocksdb.estimate-num-keys" to get the counts. Instead, keep track of > accurate counts by updating the counter in a global table every time an event > is triggered via FileSizeCount Task in Recon. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4052) Remove master/slave terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4052: - Resolution: Fixed Status: Resolved (was: Patch Available) > Remove master/slave terminology from Ozone > -- > > Key: HDDS-4052 > URL: https://issues.apache.org/jira/browse/HDDS-4052 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Attila Doroszlai >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4050) Remove non-inclusive terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4050: - Description: [http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/202007.mbox/%3CCAAaVJWVXhsv4tn1KOQkKYTaQ441Yb8y7s%2BR_GnESwduB1iFxOA%40mail.gmail.com%3E] This JIRA is to remove offensive and non-inclusive terminology from Ozone codebase. The simple ones are whitelist/blacklist and master/slave. However this JIRA can also serve as a place to fix other non-inclusive terminology (e.g., binary gendered examples, "Alice" doing the wrong security thing systematically). As [~curino] posted in his email, the IETF has created a draft for proposed alternatives [https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1] was: http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/202007.mbox/%3CCAAaVJWVXhsv4tn1KOQkKYTaQ441Yb8y7s%2BR_GnESwduB1iFxOA%40mail.gmail.com%3E This JIRA is to remove offensive and non-inclusive terminology from Hadoop. The simple ones are whitelist/blacklist and master/slave. However this JIRA can also serve as a place to fix other non-inclusive terminology (e.g., binary gendered examples, "Alice" doing the wrong security thing systematically). As [~curino] posted in his email, the IETF has created a draft for proposed alternatives https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1 > Remove non-inclusive terminology from Ozone > --- > > Key: HDDS-4050 > URL: https://issues.apache.org/jira/browse/HDDS-4050 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > [http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/202007.mbox/%3CCAAaVJWVXhsv4tn1KOQkKYTaQ441Yb8y7s%2BR_GnESwduB1iFxOA%40mail.gmail.com%3E] > This JIRA is to remove offensive and non-inclusive terminology from Ozone > codebase. The simple ones are whitelist/blacklist and master/slave. However > this JIRA can also serve as a place to fix other non-inclusive terminology > (e.g., binary gendered > examples, "Alice" doing the wrong security thing systematically). > As [~curino] posted in his email, the IETF has created a draft for proposed > alternatives > > [https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4052) Remove master/slave terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4052: - Summary: Remove master/slave terminology from Ozone (was: CLONE - Remove master/slave terminology from Hadoop) > Remove master/slave terminology from Ozone > -- > > Key: HDDS-4052 > URL: https://issues.apache.org/jira/browse/HDDS-4052 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4051) Remove whitelist/blacklist terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-4051: - Summary: Remove whitelist/blacklist terminology from Ozone (was: CLONE - Remove whitelist/blacklist terminology from Hadoop) > Remove whitelist/blacklist terminology from Ozone > - > > Key: HDDS-4051 > URL: https://issues.apache.org/jira/browse/HDDS-4051 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-4052) Remove master/slave terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-4052: Assignee: (was: Vivek Ratnavel Subramanian) > Remove master/slave terminology from Ozone > -- > > Key: HDDS-4052 > URL: https://issues.apache.org/jira/browse/HDDS-4052 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-4050) Remove non-inclusive terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-4050: Assignee: Vivek Ratnavel Subramanian > Remove non-inclusive terminology from Ozone > --- > > Key: HDDS-4050 > URL: https://issues.apache.org/jira/browse/HDDS-4050 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/202007.mbox/%3CCAAaVJWVXhsv4tn1KOQkKYTaQ441Yb8y7s%2BR_GnESwduB1iFxOA%40mail.gmail.com%3E > This JIRA is to remove offensive and non-inclusive terminology from Hadoop. > The simple ones are whitelist/blacklist and master/slave. However this JIRA > can also serve as a place to fix other non-inclusive terminology (e.g., > binary gendered > examples, "Alice" doing the wrong security thing systematically). > As [~curino] posted in his email, the IETF has created a draft for proposed > alternatives > https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-4052) CLONE - Remove master/slave terminology from Hadoop
[ https://issues.apache.org/jira/browse/HDDS-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-4052: Key: HDDS-4052 (was: HADOOP-17174) Workflow: patch-available, re-open possible (was: no-reopen-closed, patch-avail) Assignee: Vivek Ratnavel Subramanian Project: Hadoop Distributed Data Store (was: Hadoop Common) > CLONE - Remove master/slave terminology from Hadoop > --- > > Key: HDDS-4052 > URL: https://issues.apache.org/jira/browse/HDDS-4052 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-4051) CLONE - Remove whitelist/blacklist terminology from Hadoop
[ https://issues.apache.org/jira/browse/HDDS-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-4051: Key: HDDS-4051 (was: HADOOP-17173) Workflow: patch-available, re-open possible (was: no-reopen-closed, patch-avail) Assignee: Vivek Ratnavel Subramanian (was: Eric Badger) Project: Hadoop Distributed Data Store (was: Hadoop Common) > CLONE - Remove whitelist/blacklist terminology from Hadoop > -- > > Key: HDDS-4051 > URL: https://issues.apache.org/jira/browse/HDDS-4051 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Eric Badger >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Moved] (HDDS-4050) Remove non-inclusive terminology from Ozone
[ https://issues.apache.org/jira/browse/HDDS-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian moved HADOOP-17172 to HDDS-4050: --- Key: HDDS-4050 (was: HADOOP-17172) Workflow: patch-available, re-open possible (was: no-reopen-closed, patch-avail) Project: Hadoop Distributed Data Store (was: Hadoop Common) > Remove non-inclusive terminology from Ozone > --- > > Key: HDDS-4050 > URL: https://issues.apache.org/jira/browse/HDDS-4050 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: Eric Badger >Priority: Major > > http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/202007.mbox/%3CCAAaVJWVXhsv4tn1KOQkKYTaQ441Yb8y7s%2BR_GnESwduB1iFxOA%40mail.gmail.com%3E > This JIRA is to remove offensive and non-inclusive terminology from Hadoop. > The simple ones are whitelist/blacklist and master/slave. However this JIRA > can also serve as a place to fix other non-inclusive terminology (e.g., > binary gendered > examples, "Alice" doing the wrong security thing systematically). > As [~curino] posted in his email, the IETF has created a draft for proposed > alternatives > https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-4030) Remember the selected columns and make the X-axis scrollable in recon datanodes UI
[ https://issues.apache.org/jira/browse/HDDS-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-4030. -- Resolution: Fixed > Remember the selected columns and make the X-axis scrollable in recon > datanodes UI > -- > > Key: HDDS-4030 > URL: https://issues.apache.org/jira/browse/HDDS-4030 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Reporter: HuangTao >Assignee: HuangTao >Priority: Minor > Labels: pull-request-available > > Currently, the Datanodes tab can't remember the selected columns, when the > page is auto reloaded, the columns will be reset to the default columns. > Meanwhile, when several columns are selected, we can't see some columns in > the right side. > This issue will fix those. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-3486) Recon cannot track missing containers that were created and went missing while it is down.
[ https://issues.apache.org/jira/browse/HDDS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-3486: Assignee: Prashant Pogde > Recon cannot track missing containers that were created and went missing > while it is down. > -- > > Key: HDDS-3486 > URL: https://issues.apache.org/jira/browse/HDDS-3486 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Recon >Affects Versions: 0.6.0 >Reporter: Aravindan Vijayan >Assignee: Prashant Pogde >Priority: Major > Labels: TriagePending > > Since Recon relies on Container reports from DNs to track replicas, if a new > container was created and went missing when Recon was down, it will not be > able to tag it as a missing container. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-2852) Bootstrap Recon with SCM's container DB.
[ https://issues.apache.org/jira/browse/HDDS-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-2852: Assignee: Prashant Pogde > Bootstrap Recon with SCM's container DB. > > > Key: HDDS-2852 > URL: https://issues.apache.org/jira/browse/HDDS-2852 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Reporter: Aravindan Vijayan >Assignee: Prashant Pogde >Priority: Major > Labels: TriagePending > > Whenever Recon starts up, it needs to get the entire Container DB from SCM > for bootstrap. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4039) Reduce the number of fields in hdds.proto to improve performance
Vivek Ratnavel Subramanian created HDDS-4039: Summary: Reduce the number of fields in hdds.proto to improve performance Key: HDDS-4039 URL: https://issues.apache.org/jira/browse/HDDS-4039 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Datanode Affects Versions: 0.6.0 Reporter: Vivek Ratnavel Subramanian Assignee: HuangTao HDDS-3989 introduced revision and buildDate fields to hdds.proto file. These fields are required only for Recon UI and don't have to be part of hdds.proto. Also, version and setupTime are other two fields which can be removed and added only to the SCM registration type as per [~elek] ([https://github.com/apache/hadoop-ozone/pull/1226|https://github.com/apache/hadoop-ozone/pull/1226#issuecomment-663416483]) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-3804) Recon start fails with SQL exception with MySQL DB.
[
https://issues.apache.org/jira/browse/HDDS-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian reassigned HDDS-3804:
Assignee: Prashant Pogde
> Recon start fails with SQL exception with MySQL DB.
> ---
>
> Key: HDDS-3804
> URL: https://issues.apache.org/jira/browse/HDDS-3804
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
>Affects Versions: 0.6.0
>Reporter: Aravindan Vijayan
>Assignee: Prashant Pogde
>Priority: Major
>
> {code}
> org.jooq.exception.DataAccessException: SQL [create table if not exists
> `CONTAINER_HISTORY`(`container_id` bigint null, `datanode_host` varchar(1024)
> null, `first_report_timestamp` bigint null, `last_report_timestamp` bigint
> null, constraint `pk_container_id_datanode_host` primary key (`container_id`,
> `datanode_host`))]; Specified key was too long; max key length is 3072 bytes
> at org.jooq_3.11.9.MYSQL_5_7.debug(Unknown Source)
> at org.jooq.impl.Tools.translate(Tools.java:2429)
> at
> org.jooq.impl.DefaultExecuteContext.sqlException(DefaultExecuteContext.java:832)
> at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:364)
> at
> org.hadoop.ozone.recon.schema.ContainerSchemaDefinition.createContainerHistoryTable(ContainerSchemaDefinition.java:90)
> at
> org.hadoop.ozone.recon.schema.ContainerSchemaDefinition.initializeSchema(ContainerSchemaDefinition.java:72)
> at
> org.apache.hadoop.ozone.recon.ReconSchemaManager.lambda$createReconSchema$0(ReconSchemaManager.java:50)
> at java.lang.Iterable.forEach(Iterable.java:75)
> at
> org.apache.hadoop.ozone.recon.ReconSchemaManager.createReconSchema(ReconSchemaManager.java:48)
> at
> org.apache.hadoop.ozone.recon.ReconServer.call(ReconServer.java:102)
> at org.apache.hadoop.ozone.recon.ReconServer.call(ReconServer.java:53)
> at picocli.CommandLine.execute(CommandLine.java:1173)
> at picocli.CommandLine.access$800(CommandLine.java:141)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:1367)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:1335)
> at
> picocli.CommandLine$AbstractParseResultHandler.handleParseResult(CommandLine.java:1243)
> at picocli.CommandLine.parseWithHandlers(CommandLine.java:1526)
> at picocli.CommandLine.parseWithHandler(CommandLine.java:1465)
> at org.apache.hadoop.hdds.cli.GenericCli.execute(GenericCli.java:75)
> at org.apache.hadoop.hdds.cli.GenericCli.run(GenericCli.java:66)
> at org.apache.hadoop.ozone.recon.ReconServer.main(ReconServer.java:67)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Specified key was too long; max key length is 3072 bytes
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
> at com.mysql.jdbc.Util.getInstance(Util.java:408)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:943)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2487)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858)
> at
> com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1197)
> at
> com.jolbox.bonecp.PreparedStatementHandle.execute(PreparedStatementHandle.java:140)
> at
> org.jooq.tools.jdbc.DefaultPreparedStatement.execute(DefaultPreparedStatement.java:209)
> at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:432)
> at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:350)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4032) Run author check without docker
[
https://issues.apache.org/jira/browse/HDDS-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-4032:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Run author check without docker
> ---
>
> Key: HDDS-4032
> URL: https://issues.apache.org/jira/browse/HDDS-4032
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
>
> {{author.sh}} can be run in CI without docker container, since it's mostly
> just a recursive grep.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4021) Recon NodeDB should be part of the ReconDBDefinition
Vivek Ratnavel Subramanian created HDDS-4021: Summary: Recon NodeDB should be part of the ReconDBDefinition Key: HDDS-4021 URL: https://issues.apache.org/jira/browse/HDDS-4021 Project: Hadoop Distributed Data Store Issue Type: Bug Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Aravindan Vijayan ReconNodeManager uses node db in an old format which is not part of ReconDBDefinition. Move the definition to ReconDBDefinition. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4020) ACL commands like getacl and setacl should return a response only when Native Authorizer is enabled
Vivek Ratnavel Subramanian created HDDS-4020: Summary: ACL commands like getacl and setacl should return a response only when Native Authorizer is enabled Key: HDDS-4020 URL: https://issues.apache.org/jira/browse/HDDS-4020 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone CLI, Ozone Manager Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Bharat Viswanadham Currently, the getacl and setacl commands return wrong information when an external authorizer such as Ranger is enabled. There should be a check to verify if Native Authorizer is enabled before returning any response for these two commands. If an external authorizer is enabled, it should show a nice message about managing acls in external authorizer. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-4009) Recon Overview page: The volume, bucket and key counts are not accurate
Vivek Ratnavel Subramanian created HDDS-4009: Summary: Recon Overview page: The volume, bucket and key counts are not accurate Key: HDDS-4009 URL: https://issues.apache.org/jira/browse/HDDS-4009 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian The counts shown in the overview page are not accurate due to the usage of "rocksdb.estimate-num-keys" to get the counts. Instead, keep track of accurate counts by updating the counter in a global table every time an event is triggered via FileSizeCount Task in Recon. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3989) Display revision and build date of DN in recon UI
[ https://issues.apache.org/jira/browse/HDDS-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3989. -- Resolution: Fixed > Display revision and build date of DN in recon UI > - > > Key: HDDS-3989 > URL: https://issues.apache.org/jira/browse/HDDS-3989 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Reporter: HuangTao >Assignee: HuangTao >Priority: Minor > Labels: pull-request-available > > Display the revision and build date in the recon UI. > So we can get more detailed version info in UI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3984) Support filter and search the columns in recon UI
[ https://issues.apache.org/jira/browse/HDDS-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3984. -- Fix Version/s: 0.7.0 Resolution: Fixed > Support filter and search the columns in recon UI > - > > Key: HDDS-3984 > URL: https://issues.apache.org/jira/browse/HDDS-3984 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Reporter: HuangTao >Assignee: HuangTao >Priority: Major > Labels: pull-request-available > Fix For: 0.7.0 > > > Add the functions of filter and search in recon UI. People can filter/search > the columns. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3060) /retest github comment does not work
[ https://issues.apache.org/jira/browse/HDDS-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3060: - Fix Version/s: 0.6.0 Resolution: Fixed Status: Resolved (was: Patch Available) > /retest github comment does not work > > > Key: HDDS-3060 > URL: https://issues.apache.org/jira/browse/HDDS-3060 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: CI >Reporter: Marton Elek >Assignee: Attila Doroszlai >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > > Earlier we introduced an additional github workflow to process `/command` > style commands from github comments. But in this case `/retest` didn't create > the new commit to trigger a new build: > Pull request: > https://github.com/apache/hadoop-ozone/pull/393 > Run: > https://github.com/apache/hadoop-ozone/runs/463225330?check_suite_focus=true -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3798) Display version and setupTime of DN in recon web
[ https://issues.apache.org/jira/browse/HDDS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3798. -- Fix Version/s: 0.6.0 Resolution: Fixed > Display version and setupTime of DN in recon web > > > Key: HDDS-3798 > URL: https://issues.apache.org/jira/browse/HDDS-3798 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: HuangTao >Assignee: HuangTao >Priority: Minor > Labels: pull-request-available > Fix For: 0.6.0 > > Attachments: image-2020-06-14-18-53-11-656.png > > > !image-2020-06-14-18-53-11-656.png|width=735,height=191! > Here is the Datanode info currently presented in Recon Web. > If show more info about Datanodes, like the start time and version etc. We > can get the cluster status more conveniently. > For example, we can list how many different DN versions in cluster, and how > long have DN been running, and so on. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3798) Display version and setupTime of DN in recon web
[ https://issues.apache.org/jira/browse/HDDS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3798: - Summary: Display version and setupTime of DN in recon web (was: Collect more info about DN in recon web) > Display version and setupTime of DN in recon web > > > Key: HDDS-3798 > URL: https://issues.apache.org/jira/browse/HDDS-3798 > Project: Hadoop Distributed Data Store > Issue Type: Improvement >Reporter: HuangTao >Assignee: HuangTao >Priority: Minor > Labels: pull-request-available > Attachments: image-2020-06-14-18-53-11-656.png > > > !image-2020-06-14-18-53-11-656.png|width=735,height=191! > Here is the Datanode info currently presented in Recon Web. > If show more info about Datanodes, like the start time and version etc. We > can get the cluster status more conveniently. > For example, we can list how many different DN versions in cluster, and how > long have DN been running, and so on. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3914) Remove LevelDB configuration option for DN Metastore
[ https://issues.apache.org/jira/browse/HDDS-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3914: - Fix Version/s: 0.6.0 > Remove LevelDB configuration option for DN Metastore > > > Key: HDDS-3914 > URL: https://issues.apache.org/jira/browse/HDDS-3914 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Datanode >Reporter: Hanisha Koneru >Assignee: Hanisha Koneru >Priority: Blocker > Labels: pull-request-available > Fix For: 0.6.0 > > > LevelDB support was removed for OM and SCM DBs but DN Metastore can still be > configured to use LevelDB or RocksDB. > This Jira proposes to remove LevelDB configuration option for DN Metastore > (ozone.metastore.impl) and use RocksDB only. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3914) Remove LevelDB configuration option for DN Metastore
[ https://issues.apache.org/jira/browse/HDDS-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3914. -- Resolution: Fixed > Remove LevelDB configuration option for DN Metastore > > > Key: HDDS-3914 > URL: https://issues.apache.org/jira/browse/HDDS-3914 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Datanode >Reporter: Hanisha Koneru >Assignee: Hanisha Koneru >Priority: Blocker > Labels: pull-request-available > > LevelDB support was removed for OM and SCM DBs but DN Metastore can still be > configured to use LevelDB or RocksDB. > This Jira proposes to remove LevelDB configuration option for DN Metastore > (ozone.metastore.impl) and use RocksDB only. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3939) Update proto.lock files
[ https://issues.apache.org/jira/browse/HDDS-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3939. -- Resolution: Fixed > Update proto.lock files > --- > > Key: HDDS-3939 > URL: https://issues.apache.org/jira/browse/HDDS-3939 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone CLI, Ozone Datanode >Affects Versions: 0.6.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > HDDS-426 introduced new additions to proto files but failed to update > proto.lock files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3940) Update angular to v1.7.9
Vivek Ratnavel Subramanian created HDDS-3940: Summary: Update angular to v1.7.9 Key: HDDS-3940 URL: https://issues.apache.org/jira/browse/HDDS-3940 Project: Hadoop Distributed Data Store Issue Type: Task Components: website Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3939) Update proto.lock files
Vivek Ratnavel Subramanian created HDDS-3939: Summary: Update proto.lock files Key: HDDS-3939 URL: https://issues.apache.org/jira/browse/HDDS-3939 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone CLI, Ozone Datanode Affects Versions: 0.6.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian HDDS-426 introduced new additions to proto files but failed to update proto.lock files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3937) Update jquery to v3.5.1
[ https://issues.apache.org/jira/browse/HDDS-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3937: - Labels: (was: pull-request-available) Status: Patch Available (was: In Progress) > Update jquery to v3.5.1 > > > Key: HDDS-3937 > URL: https://issues.apache.org/jira/browse/HDDS-3937 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: website >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3831) Enhance Recon ContainerEndPoint to report on difference unhealty container states
[ https://issues.apache.org/jira/browse/HDDS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3831. -- Fix Version/s: 0.6.0 Resolution: Fixed Merged via [https://github.com/apache/hadoop-ozone/pull/1148] > Enhance Recon ContainerEndPoint to report on difference unhealty container > states > - > > Key: HDDS-3831 > URL: https://issues.apache.org/jira/browse/HDDS-3831 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Affects Versions: 0.6.0 >Reporter: Stephen O'Donnell >Assignee: Stephen O'Donnell >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > > HDDS-3082 changed the unhealthyContainers job to store the counts of under > replicated, over replicated, missing and mis-replicated containers. > We should enhance ContainerEndPoint.java to provide API access to those > states and perhaps a summary status too, eg: > under-replicated-count: 10 > over-replication-count: 0 > mis-replicated-count: 5 > ... -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3928) Fix endpoint display in S3 Gateway webpage
[ https://issues.apache.org/jira/browse/HDDS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3928: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix endpoint display in S3 Gateway webpage > -- > > Key: HDDS-3928 > URL: https://issues.apache.org/jira/browse/HDDS-3928 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: S3 >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Fix the way in which S3g endpoint is being displayed in S3 gateway webpage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3928) Fix endpoint display in S3 Gateway webpage
[ https://issues.apache.org/jira/browse/HDDS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3928: - Status: Patch Available (was: In Progress) > Fix endpoint display in S3 Gateway webpage > -- > > Key: HDDS-3928 > URL: https://issues.apache.org/jira/browse/HDDS-3928 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: S3 >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Fix the way in which S3g endpoint is being displayed in S3 gateway webpage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3928) Fix endpoint display in S3 Gateway webpage
Vivek Ratnavel Subramanian created HDDS-3928: Summary: Fix endpoint display in S3 Gateway webpage Key: HDDS-3928 URL: https://issues.apache.org/jira/browse/HDDS-3928 Project: Hadoop Distributed Data Store Issue Type: Bug Components: S3 Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix the way in which S3g endpoint is being displayed in S3 gateway webpage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3913) Recon build should ignore proxies
[ https://issues.apache.org/jira/browse/HDDS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3913: - Status: Patch Available (was: Open) [https://github.com/apache/hadoop-ozone/pull/1159] > Recon build should ignore proxies > - > > Key: HDDS-3913 > URL: https://issues.apache.org/jira/browse/HDDS-3913 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Recon >Affects Versions: 0.6.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > [https://github.com/eirslett/frontend-maven-plugin] used by Recon to install > pnpm incorrectly passes proxy parameters from maven settings. The frontend > maven plugin should ignore proxy for pnpm to avoid build failures when proxy > is configured. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3913) Recon build should ignore proxies
Vivek Ratnavel Subramanian created HDDS-3913: Summary: Recon build should ignore proxies Key: HDDS-3913 URL: https://issues.apache.org/jira/browse/HDDS-3913 Project: Hadoop Distributed Data Store Issue Type: Bug Components: Ozone Recon Affects Versions: 0.6.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian [https://github.com/eirslett/frontend-maven-plugin] used by Recon to install pnpm incorrectly passes proxy parameters from maven settings. The frontend maven plugin should ignore proxy for pnpm to avoid build failures when proxy is configured. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3908) Duplicate dot in Prometheus endpoint config name
[
https://issues.apache.org/jira/browse/HDDS-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-3908:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Duplicate dot in Prometheus endpoint config name
>
>
> Key: HDDS-3908
> URL: https://issues.apache.org/jira/browse/HDDS-3908
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
>
> {{HddsPrometheusConfig}} includes {{.}} at the end of the prefix, thus
> generated config name has double dot: {{hdds.prometheus..endpoint.token}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3821) Disable Ozone SPNEGO should not fall back to hadoop.http.authentication configuration
[ https://issues.apache.org/jira/browse/HDDS-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3821. -- Resolution: Fixed > Disable Ozone SPNEGO should not fall back to hadoop.http.authentication > configuration > -- > > Key: HDDS-3821 > URL: https://issues.apache.org/jira/browse/HDDS-3821 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Namit Maheshwari >Assignee: Xiaoyu Yao >Priority: Major > Labels: pull-request-available > > HDDS-3282 adds hdds.[compoment].http.auth.[type] for scm/dn and > ozone.[component].http.auth.[type] for om/s3g/recon. The type can be simple > and kerberos. When the type is kerberos, it will setup the spnego > authentication filter for the servlets. > However, when the filter prefix was not setup properly when the type is > simple. As a result, it will fallback to configuration from > hadoop.http.authentication.*. > This ticket is opened to fix the authentication filter prefix so that the > simple configuration can be honored when SPNEGO is disabled. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3821) Disable Ozone SPNEGO should not fall back to hadoop.http.authentication configuration
[ https://issues.apache.org/jira/browse/HDDS-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3821: - Fix Version/s: 0.6.0 > Disable Ozone SPNEGO should not fall back to hadoop.http.authentication > configuration > -- > > Key: HDDS-3821 > URL: https://issues.apache.org/jira/browse/HDDS-3821 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Namit Maheshwari >Assignee: Xiaoyu Yao >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > > HDDS-3282 adds hdds.[compoment].http.auth.[type] for scm/dn and > ozone.[component].http.auth.[type] for om/s3g/recon. The type can be simple > and kerberos. When the type is kerberos, it will setup the spnego > authentication filter for the servlets. > However, when the filter prefix was not setup properly when the type is > simple. As a result, it will fallback to configuration from > hadoop.http.authentication.*. > This ticket is opened to fix the authentication filter prefix so that the > simple configuration can be honored when SPNEGO is disabled. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-3831) Enhance Recon ContainerEndPoint to report on difference unhealty container states
[
https://issues.apache.org/jira/browse/HDDS-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142326#comment-17142326
]
Vivek Ratnavel Subramanian commented on HDDS-3831:
--
[~sodonnell] Thanks for the detailed write-up. I like the
`/containers/unhealthy/\{state}` endpoint. We can give an overall report as the
response for `/containers/unhealthy` endpoint as you suggested and remove the
"missing" endpoint.
> Enhance Recon ContainerEndPoint to report on difference unhealty container
> states
> -
>
> Key: HDDS-3831
> URL: https://issues.apache.org/jira/browse/HDDS-3831
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone Recon
>Affects Versions: 0.6.0
>Reporter: Stephen O'Donnell
>Priority: Major
>
> HDDS-3082 changed the unhealthyContainers job to store the counts of under
> replicated, over replicated, missing and mis-replicated containers.
> We should enhance ContainerEndPoint.java to provide API access to those
> states and perhaps a summary status too, eg:
> under-replicated-count: 10
> over-replication-count: 0
> mis-replicated-count: 5
> ...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3777) Reduce recon UI build time
[
https://issues.apache.org/jira/browse/HDDS-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian resolved HDDS-3777.
--
Resolution: Fixed
> Reduce recon UI build time
> --
>
> Key: HDDS-3777
> URL: https://issues.apache.org/jira/browse/HDDS-3777
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: build
>Affects Versions: 0.6.0
>Reporter: Attila Doroszlai
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Labels: pull-request-available
>
> Hi [~vivekratnavel], [~elek],
> The change in HDDS-3682 increased Recon build time by ~10 minutes, eg.:
> {code:title=before}
> [INFO] Apache Hadoop Ozone Recon .. SUCCESS [04:04
> min]
> {code}
> {code:title=after}
> [INFO] Apache Hadoop Ozone Recon .. SUCCESS [16:34
> min]
> {code}
> Recon UI is built in _compile_, _acceptance_ and _coverage_ checks. Since
> _coverage_ runs after all other checks, the increment affects overall CI
> response time twice. (Effect was 3x before HDDS-3726, thanks for the fix in
> {{integration.sh}}.)
> Is there any way to speed this up, eg. by installing dependencies in the
> ozone-build docker image?
> before: https://github.com/apache/hadoop-ozone/actions/runs/130155633
> pre-HDDS-3726: https://github.com/apache/hadoop-ozone/actions/runs/130301719
> current: https://github.com/apache/hadoop-ozone/actions/runs/131217499
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3784) Use matrix build for integration test
[ https://issues.apache.org/jira/browse/HDDS-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3784: - Resolution: Fixed Status: Resolved (was: Patch Available) > Use matrix build for integration test > - > > Key: HDDS-3784 > URL: https://issues.apache.org/jira/browse/HDDS-3784 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: build >Reporter: Attila Doroszlai >Assignee: Attila Doroszlai >Priority: Major > Labels: pull-request-available > > Integration test profiles can be simplified with matrix builds in GitHub > Actions. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3682) Recon UI: Add interactive visualization for file size counts
[ https://issues.apache.org/jira/browse/HDDS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3682: - Resolution: Fixed Status: Resolved (was: Patch Available) > Recon UI: Add interactive visualization for file size counts > > > Key: HDDS-3682 > URL: https://issues.apache.org/jira/browse/HDDS-3682 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Include a histogram to interactively view file size counts across each > volume/bucket -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3590) Recon UI: Add visualization for file size distribution
[ https://issues.apache.org/jira/browse/HDDS-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3590. -- Resolution: Fixed > Recon UI: Add visualization for file size distribution > --- > > Key: HDDS-3590 > URL: https://issues.apache.org/jira/browse/HDDS-3590 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: TriagePending > Attachments: Recon UI_ Visualizing file size distribution.pdf > > > Recon has an API endpoint to get file size distribution in Ozone. Add > visualization in Recon UI for this using histograms. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3682) Recon UI: Add interactive visualization for file size counts
[ https://issues.apache.org/jira/browse/HDDS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3682: - Status: Patch Available (was: In Progress) > Recon UI: Add interactive visualization for file size counts > > > Key: HDDS-3682 > URL: https://issues.apache.org/jira/browse/HDDS-3682 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Include a histogram to interactively view file size counts across each > volume/bucket -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3726) Upload code coverage to Codecov and enable checks in PR workflow of Github Actions
Vivek Ratnavel Subramanian created HDDS-3726: Summary: Upload code coverage to Codecov and enable checks in PR workflow of Github Actions Key: HDDS-3726 URL: https://issues.apache.org/jira/browse/HDDS-3726 Project: Hadoop Distributed Data Store Issue Type: Bug Components: build Affects Versions: 0.6.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian HDDS-3170 aggregates code coverage across all components. We need to upload the reports to codecov to be able to keep track of coverage and coverage diffs to be able to tell if a PR does not do a good job on writing unit tests. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3681) Recon: Add support to store file size counts in each volume/bucket
[ https://issues.apache.org/jira/browse/HDDS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3681: - Resolution: Fixed Status: Resolved (was: Patch Available) > Recon: Add support to store file size counts in each volume/bucket > -- > > Key: HDDS-3681 > URL: https://issues.apache.org/jira/browse/HDDS-3681 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Update file size count task to keep track of file size counts across each > volume/bucket. Make the necessary changes to the underlying schema. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-281) Recon: Add container size distribution visualization
[ https://issues.apache.org/jira/browse/HDDS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-281: Summary: Recon: Add container size distribution visualization (was: Need container size distribution metric in OzoneManager UI) > Recon: Add container size distribution visualization > > > Key: HDDS-281 > URL: https://issues.apache.org/jira/browse/HDDS-281 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Reporter: Nilotpal Nandi >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Labels: TriagePending > > It would be good if we have some metric/histogram in OzoneManager UI > indicating the different container size range and corresponding percentages > for the same created in the cluster. > For example : > 0-2 GB 10% > 2-4 GB . 20% > 4-5 GB 70% > 5+ GB 0% > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-281) Need container size distribution metric in OzoneManager UI
[ https://issues.apache.org/jira/browse/HDDS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17121324#comment-17121324 ] Vivek Ratnavel Subramanian commented on HDDS-281: - [~arp] Not yet, but this is definitely something that will be part of Recon and not OM UI. I will use this same Jira to track it. Thanks! > Need container size distribution metric in OzoneManager UI > -- > > Key: HDDS-281 > URL: https://issues.apache.org/jira/browse/HDDS-281 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: Ozone Recon >Reporter: Nilotpal Nandi >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Labels: TriagePending > > It would be good if we have some metric/histogram in OzoneManager UI > indicating the different container size range and corresponding percentages > for the same created in the cluster. > For example : > 0-2 GB 10% > 2-4 GB . 20% > 4-5 GB 70% > 5+ GB 0% > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3011) Refreshing Recon UI results in 404
[
https://issues.apache.org/jira/browse/HDDS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian resolved HDDS-3011.
--
Fix Version/s: 0.5.0
Target Version/s: (was: 0.6.0)
Assignee: Vivek Ratnavel Subramanian (was: Aravindan Vijayan)
Resolution: Fixed
This was already fixed by using React Hash router for Recon UI.
> Refreshing Recon UI results in 404
> --
>
> Key: HDDS-3011
> URL: https://issues.apache.org/jira/browse/HDDS-3011
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
>Affects Versions: 0.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Labels: TriagePending
> Fix For: 0.5.0
>
>
> Refreshing any URL of Recon UI (ex:
> [http://localhost:9888/Datanodes|http://vsubramanian-cdh-4.vpc.cloudera.com:9888/Datanodes])
> throws 404 error.
> {code:java}
> HTTP ERROR 404 Not Found
> URI:/Datanodes
> STATUS:404
> MESSAGE:Not Found
> SERVLET:org.eclipse.jetty.servlet.DefaultServlet-4d9d1b69
> {code}
> This 404 should only happen with URLs that match "/api" pattern and not with
> the "/".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3681) Recon: Add support to store file size counts in each volume/bucket
[ https://issues.apache.org/jira/browse/HDDS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3681: - Status: Patch Available (was: Open) > Recon: Add support to store file size counts in each volume/bucket > -- > > Key: HDDS-3681 > URL: https://issues.apache.org/jira/browse/HDDS-3681 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Update file size count task to keep track of file size counts across each > volume/bucket. Make the necessary changes to the underlying schema. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3682) Recon UI: Add interactive visualization for file size counts
Vivek Ratnavel Subramanian created HDDS-3682: Summary: Recon UI: Add interactive visualization for file size counts Key: HDDS-3682 URL: https://issues.apache.org/jira/browse/HDDS-3682 Project: Hadoop Distributed Data Store Issue Type: Sub-task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Include a histogram to interactively view file size counts across each volume/bucket -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3681) Recon: Add support to store file size counts in each volume/bucket
Vivek Ratnavel Subramanian created HDDS-3681: Summary: Recon: Add support to store file size counts in each volume/bucket Key: HDDS-3681 URL: https://issues.apache.org/jira/browse/HDDS-3681 Project: Hadoop Distributed Data Store Issue Type: Sub-task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Update file size count task to keep track of file size counts across each volume/bucket. Make the necessary changes to the underlying schema. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3618) Update OM HA acceptance test to Python3
[
https://issues.apache.org/jira/browse/HDDS-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian resolved HDDS-3618.
--
Resolution: Fixed
> Update OM HA acceptance test to Python3
> ---
>
> Key: HDDS-3618
> URL: https://issues.apache.org/jira/browse/HDDS-3618
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
>
> HDDS-3332 updated acceptance tests to Python 3, but OM HA test (disabled
> currently) fails with:
> {code}
> Step 16/22 : RUN sudo pip install robotframework-sshlibrary
> ---> Running in 15849257580a
> sudo: pip: command not found
> Service 'datanode' failed to build: The command '/bin/sh -c sudo pip install
> robotframework-sshlibrary' returned a non-zero code: 1
> {code}
> Need to update to {{pip3}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-2563) Handle InterruptedException in RunningDatanodeState
[ https://issues.apache.org/jira/browse/HDDS-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-2563. -- Resolution: Fixed > Handle InterruptedException in RunningDatanodeState > --- > > Key: HDDS-2563 > URL: https://issues.apache.org/jira/browse/HDDS-2563 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task >Reporter: Dinesh Chitlangia >Assignee: Dinesh Chitlangia >Priority: Major > Labels: newbie, pull-request-available, sonar > > [https://sonarcloud.io/project/issues?id=hadoop-ozone=AW5md-6pKcVY8lQ4ZsRC=AW5md-6pKcVY8lQ4ZsRC] > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3647) NPE while open datanode page since a pipeline no leader
[ https://issues.apache.org/jira/browse/HDDS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3647. -- Fix Version/s: 0.6.0 Resolution: Fixed > NPE while open datanode page since a pipeline no leader > --- > > Key: HDDS-3647 > URL: https://issues.apache.org/jira/browse/HDDS-3647 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Recon >Affects Versions: 0.6.0 >Reporter: maobaolong >Assignee: maobaolong >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > > If there is a pipeline have no leader on a datanode, it will through NPE. > STAND_ALONE pipeline have no leader, and ratis pipeline have no leader some > time. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Commented] (HDDS-3590) Recon UI: Add visualization for file size distribution
[ https://issues.apache.org/jira/browse/HDDS-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108665#comment-17108665 ] Vivek Ratnavel Subramanian commented on HDDS-3590: -- I have attached the initial version of the design doc for this feature. [^Recon UI_ Visualizing file size distribution.pdf] > Recon UI: Add visualization for file size distribution > --- > > Key: HDDS-3590 > URL: https://issues.apache.org/jira/browse/HDDS-3590 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Attachments: Recon UI_ Visualizing file size distribution.pdf > > > Recon has an API endpoint to get file size distribution in Ozone. Add > visualization in Recon UI for this using histograms. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3590) Recon UI: Add visualization for file size distribution
[ https://issues.apache.org/jira/browse/HDDS-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3590: - Attachment: Recon UI_ Visualizing file size distribution.pdf > Recon UI: Add visualization for file size distribution > --- > > Key: HDDS-3590 > URL: https://issues.apache.org/jira/browse/HDDS-3590 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Attachments: Recon UI_ Visualizing file size distribution.pdf > > > Recon has an API endpoint to get file size distribution in Ozone. Add > visualization in Recon UI for this using histograms. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDDS-3572) Make sure ozone. administrators have access to all keys when acl enabled.
[ https://issues.apache.org/jira/browse/HDDS-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-3572: Assignee: mingchao zhao > Make sure ozone. administrators have access to all keys when acl enabled. > -- > > Key: HDDS-3572 > URL: https://issues.apache.org/jira/browse/HDDS-3572 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: om >Reporter: mingchao zhao >Assignee: mingchao zhao >Priority: Major > Labels: pull-request-available > > After our cluster is acl-enabled, the original user cannot continue to access > his or her key. Because the acl of the old key (created by s3g) has been set > to start the user for s3g. > For access all the keys, we need to increase the user's access to all the > keys. Usually there are a lot of keys in a cluster, so it's very difficult to > add permissions to all keys. > For now, we're trying to use Administrators, but I found that the current > ozone Administrators cannot access all keys. Administrators of ozone are also > checked for permissions. In HDFS, dfs.cluster.administrators can able to > access all files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3571) Recon: Display leader count in Datanodes page
[ https://issues.apache.org/jira/browse/HDDS-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3571. -- Resolution: Fixed > Recon: Display leader count in Datanodes page > - > > Key: HDDS-3571 > URL: https://issues.apache.org/jira/browse/HDDS-3571 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Datanodes page should have "Leader Count" column that displays the leader > count for how many Ratis pipelines the given datanode is elected as a leader. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3571) Recon: Display leader count in Datanodes page
Vivek Ratnavel Subramanian created HDDS-3571: Summary: Recon: Display leader count in Datanodes page Key: HDDS-3571 URL: https://issues.apache.org/jira/browse/HDDS-3571 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Datanodes page should have "Leader Count" column that displays the leader count for how many Ratis pipelines the given datanode is elected as a leader. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3558) Recon UI: Add strict linter rules to improve code quality
[ https://issues.apache.org/jira/browse/HDDS-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3558. -- Fix Version/s: 0.6.0 Resolution: Fixed > Recon UI: Add strict linter rules to improve code quality > - > > Key: HDDS-3558 > URL: https://issues.apache.org/jira/browse/HDDS-3558 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > > Add a linter like ([xojs|https://github.com/xojs/xo]) and fix all linter > errors and warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3570) Add Recon UI lint checks and unit tests to Github Actions CI workflow
Vivek Ratnavel Subramanian created HDDS-3570: Summary: Add Recon UI lint checks and unit tests to Github Actions CI workflow Key: HDDS-3570 URL: https://issues.apache.org/jira/browse/HDDS-3570 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Recon UI unit tests and linter checks should be added to Github actions CI. Optimization: Try to add a workflow in such a way that these checks are run only if there is a change related to Recon UI files. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3558) Recon UI: Add strict linter rules to improve code quality
[ https://issues.apache.org/jira/browse/HDDS-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3558: - Summary: Recon UI: Add strict linter rules to improve code quality (was: Recon UI: Add strict linter to improve code quality) > Recon UI: Add strict linter rules to improve code quality > - > > Key: HDDS-3558 > URL: https://issues.apache.org/jira/browse/HDDS-3558 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Add a linter like ([xojs|https://github.com/xojs/xo]) and fix all linter > errors and warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3558) Recon UI: Add strict linter to improve code quality
[ https://issues.apache.org/jira/browse/HDDS-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3558: - Description: Add a linter like ([xojs|https://github.com/xojs/xo]) and fix all linter errors and warnings. (was: Add a linter like ([xojs|[https://github.com/xojs/xo]]) and fix all linter errors and warnings.) > Recon UI: Add strict linter to improve code quality > --- > > Key: HDDS-3558 > URL: https://issues.apache.org/jira/browse/HDDS-3558 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Add a linter like ([xojs|https://github.com/xojs/xo]) and fix all linter > errors and warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3558) Recon UI: Add strict linter to improve code quality
Vivek Ratnavel Subramanian created HDDS-3558: Summary: Recon UI: Add strict linter to improve code quality Key: HDDS-3558 URL: https://issues.apache.org/jira/browse/HDDS-3558 Project: Hadoop Distributed Data Store Issue Type: Task Components: Ozone Recon Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Add a linter like ([xojs|[https://github.com/xojs/xo]]) and fix all linter errors and warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3333) Recon UI: All the pages should auto reload
[ https://issues.apache.org/jira/browse/HDDS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-: - Resolution: Fixed Status: Resolved (was: Patch Available) > Recon UI: All the pages should auto reload > -- > > Key: HDDS- > URL: https://issues.apache.org/jira/browse/HDDS- > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Overview page should auto refresh to fetch updated data and alerts if any. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3333) Recon UI: All the pages should auto reload
[ https://issues.apache.org/jira/browse/HDDS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-: - Status: Patch Available (was: In Progress) > Recon UI: All the pages should auto reload > -- > > Key: HDDS- > URL: https://issues.apache.org/jira/browse/HDDS- > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > > Overview page should auto refresh to fetch updated data and alerts if any. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3333) Recon UI: All the pages should auto reload
[ https://issues.apache.org/jira/browse/HDDS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-: - Summary: Recon UI: All the pages should auto reload (was: Recon UI: Overview page should auto refresh) > Recon UI: All the pages should auto reload > -- > > Key: HDDS- > URL: https://issues.apache.org/jira/browse/HDDS- > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Overview page should auto refresh to fetch updated data and alerts if any. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3502) Remove dependence on commons-lang
[
https://issues.apache.org/jira/browse/HDDS-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-3502:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove dependence on commons-lang
> -
>
> Key: HDDS-3502
> URL: https://issues.apache.org/jira/browse/HDDS-3502
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Minor
> Labels: pull-request-available
>
> Few parts of Ozone still use {{commons-lang}}, while most are already on
> {{commons-lang3}}. Let's update those remaining usages and remove the
> unnecessary dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-3411) Switch Recon SQL DB to Derby.
[ https://issues.apache.org/jira/browse/HDDS-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3411. -- Resolution: Fixed > Switch Recon SQL DB to Derby. > - > > Key: HDDS-3411 > URL: https://issues.apache.org/jira/browse/HDDS-3411 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.6.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 0.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Recon currently uses Sqlite as its defacto SQL DB with an option to configure > other JDBC compatible databases. However, on some platforms like the IBM > power pc, this causes problems from compile time since it does not have the > sqlite native driver. This task aims to change the default SQL DB used by > Recon to Derby, but retains the out of the box support (no need to supply the > driver) for Sqlite as well. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-2994) API Docs for Recon - Swagger integration.
[ https://issues.apache.org/jira/browse/HDDS-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-2994: - Parent: (was: HDDS-1996) Issue Type: Task (was: Sub-task) > API Docs for Recon - Swagger integration. > - > > Key: HDDS-2994 > URL: https://issues.apache.org/jira/browse/HDDS-2994 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Aravindan Vijayan >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3182) Add unit tests to Recon Frontend
[ https://issues.apache.org/jira/browse/HDDS-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3182: - Parent: (was: HDDS-1996) Issue Type: Bug (was: Sub-task) > Add unit tests to Recon Frontend > > > Key: HDDS-3182 > URL: https://issues.apache.org/jira/browse/HDDS-3182 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Add enzyme and jest libraries as dev dependencies and improve code coverage > with unit tests in Recon UI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3182) Add unit tests to Recon Frontend
[ https://issues.apache.org/jira/browse/HDDS-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3182: - Target Version/s: 0.6.0 (was: 0.5.0) > Add unit tests to Recon Frontend > > > Key: HDDS-3182 > URL: https://issues.apache.org/jira/browse/HDDS-3182 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Add enzyme and jest libraries as dev dependencies and improve code coverage > with unit tests in Recon UI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3182) Add unit tests to Recon Frontend
[ https://issues.apache.org/jira/browse/HDDS-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3182: - Issue Type: Task (was: Bug) > Add unit tests to Recon Frontend > > > Key: HDDS-3182 > URL: https://issues.apache.org/jira/browse/HDDS-3182 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: Ozone Recon >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Add enzyme and jest libraries as dev dependencies and improve code coverage > with unit tests in Recon UI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3393) Recon throws NPE in clusterState endpoint
[
https://issues.apache.org/jira/browse/HDDS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-3393:
-
Status: Patch Available (was: Open)
> Recon throws NPE in clusterState endpoint
> -
>
> Key: HDDS-3393
> URL: https://issues.apache.org/jira/browse/HDDS-3393
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
>Affects Versions: 0.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Major
> Labels: pull-request-available
>
> Recon throws NPE while trying to get number of volumes from omMetadataManager
> instance (omMetadataManager.getVolumeTable().getEstimatedKeyCount()).
> This happens before Recon gets its first snapshot db from OM, because only
> after first snapshot db, omMetadataManager initializes its tables.
> {code:java}
> Unable to get Volumes count in ClusterStateResponse.
> java.lang.NullPointerException
> at
> org.apache.hadoop.ozone.recon.api.ClusterStateEndpoint.getClusterState(ClusterStateEndpoint.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:76)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:148)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:191)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:200)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:103)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:493)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:415)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:104)
> at
> org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:277)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:272)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:268)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:268)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:289)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:256)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:416)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:370)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:389)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:342)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:229)
> at
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
> at
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
> at
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
> at
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
> at
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
> at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
> at
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
> at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596)
> at
>
[jira] [Resolved] (HDDS-3357) Add check for import from shaded package
[ https://issues.apache.org/jira/browse/HDDS-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved HDDS-3357. -- Resolution: Fixed > Add check for import from shaded package > > > Key: HDDS-3357 > URL: https://issues.apache.org/jira/browse/HDDS-3357 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: build >Reporter: Attila Doroszlai >Assignee: Attila Doroszlai >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add a checkstyle rule to reject import from shaded packages. This would help > avoid accidentally using shaded transitive dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3393) Recon throws NPE in clusterState endpoint
Vivek Ratnavel Subramanian created HDDS-3393:
Summary: Recon throws NPE in clusterState endpoint
Key: HDDS-3393
URL: https://issues.apache.org/jira/browse/HDDS-3393
Project: Hadoop Distributed Data Store
Issue Type: Bug
Components: Ozone Recon
Affects Versions: 0.5.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
Recon throws NPE while trying to get number of volumes from omMetadataManager
instance (omMetadataManager.getVolumeTable().getEstimatedKeyCount()).
This happens before Recon gets its first snapshot db from OM, because only
after first snapshot db, omMetadataManager initializes its tables.
{code:java}
Unable to get Volumes count in ClusterStateResponse.
java.lang.NullPointerException
at
org.apache.hadoop.ozone.recon.api.ClusterStateEndpoint.getClusterState(ClusterStateEndpoint.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:76)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:148)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:191)
at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:200)
at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:103)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:493)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:415)
at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:104)
at
org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:277)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:272)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:268)
at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
at org.glassfish.jersey.internal.Errors.process(Errors.java:268)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:289)
at
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:256)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:416)
at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:370)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:389)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:342)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:229)
at
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
at
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
at
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
at
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
at
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596)
at
org.apache.hadoop.hdds.server.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1615)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
at
org.apache.hadoop.hdds.server.http.NoCacheFilter.doFilter(NoCacheFilter.java:48)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
[jira] [Created] (HDDS-3376) Exclude unwanted jars from Ozone Filesystem jar
Vivek Ratnavel Subramanian created HDDS-3376: Summary: Exclude unwanted jars from Ozone Filesystem jar Key: HDDS-3376 URL: https://issues.apache.org/jira/browse/HDDS-3376 Project: Hadoop Distributed Data Store Issue Type: Bug Components: Ozone Filesystem Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian This is a followup Jira to HDDS-3368 to clean up unwanted jars like jackson being packaged with Ozone Filesystem jar. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3368) Ozone filesystem jar should not include webapps folder
[ https://issues.apache.org/jira/browse/HDDS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3368: - Status: Patch Available (was: In Progress) > Ozone filesystem jar should not include webapps folder > -- > > Key: HDDS-3368 > URL: https://issues.apache.org/jira/browse/HDDS-3368 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Filesystem >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > hadoop-ozone-filesystem-lib-current jar includes webapps folder of hdds > datanode. > This should not be included in the filesystem jar. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3368) Ozone filesystem jar should not include webapps folder
Vivek Ratnavel Subramanian created HDDS-3368: Summary: Ozone filesystem jar should not include webapps folder Key: HDDS-3368 URL: https://issues.apache.org/jira/browse/HDDS-3368 Project: Hadoop Distributed Data Store Issue Type: Bug Components: Ozone Filesystem Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian hadoop-ozone-filesystem-lib-current jar includes webapps folder of hdds datanode. This should not be included in the filesystem jar. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Created] (HDDS-3342) Ozone admin shell commands do not print or log exceptions on failures
Vivek Ratnavel Subramanian created HDDS-3342: Summary: Ozone admin shell commands do not print or log exceptions on failures Key: HDDS-3342 URL: https://issues.apache.org/jira/browse/HDDS-3342 Project: Hadoop Distributed Data Store Issue Type: Bug Components: Ozone CLI Affects Versions: 0.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Ozone shell commands such as `ozone admin container create` does not print any information on failure which makes it very difficult to debug the underlying issue. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-3280) Ozone BaseHTTPServer should honor ozone.security.enabled config
[ https://issues.apache.org/jira/browse/HDDS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated HDDS-3280: - Status: Patch Available (was: Open) > Ozone BaseHTTPServer should honor ozone.security.enabled config > --- > > Key: HDDS-3280 > URL: https://issues.apache.org/jira/browse/HDDS-3280 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Security >Affects Versions: 0.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > > Ozone BaseHTTPServer tries to start HTTP server with Spnego Principal and > Keytab even if ozone.security.enabled flag is set to false. It should honor > ozone.security.enabled flag and start the server accordingly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
