[
https://issues.apache.org/jira/browse/KNOX-2835?focusedWorklogId=829626&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-829626
]
ASF GitHub Bot logged work on KNOX-2835:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Nov/22 10:21
Start Date: 29/Nov/22 10:21
Worklog Time Spent: 10m
Work Description: zeroflag opened a new pull request, #686:
URL: https://github.com/apache/knox/pull/686
## What changes were proposed in this pull request?
Originally was named incorretly
## How was this patch tested?
Issue Time Tracking
-------------------
Worklog Id: (was: 829626)
Time Spent: 40m (was: 0.5h)
> SQL DB based topology monitor
> -----------------------------
>
> Key: KNOX-2835
> URL: https://issues.apache.org/jira/browse/KNOX-2835
> Project: Apache Knox
> Issue Type: New Feature
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This is similar to KNOX-1012 but the providers/descriptors are stored in the
> database instead of zookeeper.
> * If a provider/descriptor is deleted from the db but exists on the file
> system the monitor is going to delete it from the file system
> * If a provider/descriptor exists in the DB but missing from the file system
> the monitor is going to download it from the DB to the FS.
> * If a provider/descriptor in the DB has a different content than the
> corresponding local file, then the monitor is going to update the local file
> with the content from he DB. However to avoid too frequent and unnecessary IO
> operations we only change the local files if the remote change happened after
> the last synchronization time (if it happened in the past, we assume the
> changes were already synced to the disk). So one can change the local files
> on the disk manually without worrying about losing their local changes, until
> someone updates the DB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
