Modify the yarn kbn reset script to delete the /data directory
#187914
Assignees
Labels
Team:Operations
Team label for Operations Team
Comments
|
Pinging @elastic/kibana-operations (Team:Operations) |
delanni
added a commit
that referenced
this issue
Jul 15, 2024
## Summary In some cases, the `data/` folder sticking around is causing developers' environments to be corrupted. None of the current reset/clean methods clean that folder. This PR adds this small adjustment. Closes: #187914
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Jul 15, 2024
…ic#188298) ## Summary In some cases, the `data/` folder sticking around is causing developers' environments to be corrupted. None of the current reset/clean methods clean that folder. This PR adds this small adjustment. Closes: elastic#187914 (cherry picked from commit f1fa221)
kibanamachine
referenced
this issue
Jul 15, 2024
…tale state (#188298) (#188316) # Backport This will backport the following commits from `main` to `8.15`: - [`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)](#188298) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-07-15T14:38:57Z","message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.16.0"],"title":"`yarn kbn reset` will clean data/ as well to avoid stale state","number":188298,"url":"https://github.com/elastic/kibana/pull/188298","mergeCommit":{"message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/188298","number":188298,"mergeCommit":{"message":"`yarn kbn reset` will clean data/ as well to avoid stale state (#188298)\n\n## Summary\r\nIn some cases, the `data/` folder sticking around is causing developers'\r\nenvironments to be corrupted. None of the current reset/clean methods\r\nclean that folder. This PR adds this small adjustment.\r\n\r\nCloses: https://github.com/elastic/kibana/issues/187914","sha":"f1fa22125115c13638e3470891f62fbbe02c71bb"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature:
Modify the
yarn kbn resetscript to delete the/datadirectoryDescribe a specific use case for the feature:
Over the past 6 months multiple folks have encountered errors running Kibana related to lmdb. The solution to which was to delete the
/datadirectory under the root of the Kibana project.It could be useful to delete this directory as part of the
yarn kbn resetscript, as it is meant to be a hard reset for Kibana when all else fails, so this seems to fit in concept. My hope would be that it is a simple change that could save some folks in the future a few hours of debugging.(cc @delanni in case of labeled this issue incorrectly)
The text was updated successfully, but these errors were encountered: