[jira] [Commented] (ZOOKEEPER-4425) 4lw Command: On demand snapshot

["Patrick D. Hunt (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470945#comment-17470945 ] 

Patrick D. Hunt commented on ZOOKEEPER-4425:
--------------------------------------------

I have a concern about this change - tbh whether the feature should be supported at all. If you notice none of the existing 4lw allow changes to the "persistent" state of the service. This is on purpose. 4lw have no security - eg no authz. 4lw have been a source of security issues in the. past - in particular DOS attacks. eg https://issues.apache.org/jira/browse/ZOOKEEPER-2693
see also
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ZOOKEEPER%20AND%20text%20~%20%224lw%20dos%22
Please reconsider this feature, at least in the current form. Thx.

> 4lw Command: On demand snapshot
> -------------------------------
>
>                 Key: ZOOKEEPER-4425
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4425
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Pablo Francisco Pérez Hidalgo
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Working with disaster recovery scenarios at work, we found that having the capacity of telling a ZooKeeper instance to take a snapshot, thus dumping into files the contents of its view of the internal database, could be a last resource hatch out of potential data loss.
> As an example, imagine that all the voting members of the ensemble are wiped out due a wrong deployment configuration change. A single surviving observer could hold on its memory the last copy of most recently updated the ensemble data. Sending it a _*snap*_ *four letter words command* that forced it to save a snapshot of that information into disk could be a very convenient way of recovering the database.
>  
> This issue aims to discuss the addition of this feature and serve as the gate for a an already available patch providing this feature.



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