[ 
https://issues.apache.org/jira/browse/NIFI-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mahieddine Cherif updated NIFI-7979:
------------------------------------
    Description: 
For some reason we are no longer able to update a parameter on our nifi 
cluster. That's not related to some processor/controller that can't be stopped 
because : 

1 - It happens on all of our parameters contexts

2 - As shown in this screen record https://www.screencast.com/t/N5ard5eW2AQP 
Even with an empty  freshly created parameter context we can't add a new 
parameter. 

In both cases we get this error 


!sc_error1.png!

!sc_error2.png!

 When we restart our cluster it works then after few hours it happens again

  was:
For some reason we are no longer able to update a parameter on our nifi 
cluster. That's not related to some processor/controller that can't be stopped 
because : 

1 - It happens on all of our parameters contexts

2 - Even with empty a freshly created parameter context we can't add a new 
parameter

In both cases we get this error 

 

!sc_error1.png!

!sc_error2.png!

 


> Can't update parameter
> ----------------------
>
>                 Key: NIFI-7979
>                 URL: https://issues.apache.org/jira/browse/NIFI-7979
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.11.4
>            Reporter: Mahieddine Cherif
>            Priority: Major
>         Attachments: sc_error1.png, sc_error2.png
>
>
> For some reason we are no longer able to update a parameter on our nifi 
> cluster. That's not related to some processor/controller that can't be 
> stopped because : 
> 1 - It happens on all of our parameters contexts
> 2 - As shown in this screen record https://www.screencast.com/t/N5ard5eW2AQP 
> Even with an empty  freshly created parameter context we can't add a new 
> parameter. 
> In both cases we get this error 
> !sc_error1.png!
> !sc_error2.png!
>  When we restart our cluster it works then after few hours it happens again



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to