[
https://issues.apache.org/jira/browse/KNOX-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634281#comment-17634281
]
ASF subversion and git services commented on KNOX-2835:
-------------------------------------------------------
Commit 6d3f960b54fee520b2311f614a073cc8c2592403 in knox's branch
refs/heads/master from Attila Magyar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=6d3f960b5 ]
KNOX-2835 - SQL DB based topology monitor
> 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: 0.5h
> 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)
