[jira] [Resolved] (HBASE-26472) Adhere to semantic conventions regarding table data operations

[Nick Dimiduk (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-26472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-26472.
--
Resolution: Fixed

Pushed addendum.

> Adhere to semantic conventions regarding table data operations
> --
>
> Key: HBASE-26472
> URL: https://issues.apache.org/jira/browse/HBASE-26472
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-2
>
>
> Follow the guidance outlined in 
> https://github.com/open-telemetry/opentelemetry-specification/blob/3e380e2/specification/trace/semantic_conventions/database.dm



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (HBASE-24936) review Jenkins build artifacts

[Sean Busbey (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-24936.
-
  Assignee: Duo Zhang  (was: Sean Busbey)
Resolution: Fixed

> review Jenkins build artifacts
> --
>
> Key: HBASE-24936
> URL: https://issues.apache.org/jira/browse/HBASE-24936
> Project: HBase
>  Issue Type: Task
>Reporter: Sean Busbey
>Assignee: Duo Zhang
>Priority: Critical
> Attachments: usage-hbase-find-flaky.zip, usage-hbase-full.zip
>
>
> Post move to the ci-hadoop build servers we are now the biggest user of 
> space. That is not a problem in and of itself, but the master node has run 
> out of disk space twice now. As of this snapshot we are using 125GB of 
> storage and the next largest project is only using 20GB.
> https://paste.apache.org/kyrds
> We should review our builds for any issues and come up with expectations for 
> what our steady-state disk usage should look like
> * we are supposed to compress any test logs (usually this gets us 90-99% 
> space savings)
> * we are supposed to clean up workspaces when jobs are done
> * we are supposed to keep a fixed window of prior builds (either by days or 
> number of runs)
> If all of our jobs are currently following these guidelines, another 
> possibility is to push the artifacts we need over to 
> [nightlies.a.o|https://nightlies.apache.org/authoring.html]. Barring that, we 
> should formally request asf infra set up [a plugin for storing artifact on 
> s3|https://plugins.jenkins.io/artifact-manager-s3/].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)