-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volumes not save flows #10
Comments
Docker containers should be stateless. Thus all container-related parameters (configuration, processors etc.) should be managed on docker image build stage. Flow management is a pain-point for NiFi. Here you have 2 options:
Easiest way to work with flow which is stored outside of container:
|
Regarding cluster the best way is to store all node-related information (flow, settings etc.) on separate places. |
@xemuliam I am following your approach. I started with copying only flow.xml.gz and nifi.properties, then starting up a new container mapping just these 2 files. The container will not start however. It has these messages in the log:
and
|
Also .. if the flow data is in flow.xml.gz then whats the point of the flowfile_repository folder? |
Processors are not saved after to and restart the containers, whenever I see the volume database_repository it is modified. I need to create the flows and they stay on the volume. And I have a question regarding clusters volumes, how should I implement them? Should I make a volume for each instance or can I just create a shared volume for all instances?
The text was updated successfully, but these errors were encountered: