Hi We are facing performance problem at Nifi UI. Sometime it takes around 6-14 sec. when moving a processor at the UI. Questions: 1) How to debug the UI which is slow? 2) Is overflow of cancelled tasks normal when setting to DEBUG? SLOW 2018-10-15 11:16:14,645 INFO [NiFi Web Server-729217] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for () PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 1.1.1.1) 2018-10-15 11:16:14,681 INFO [NiFi Web Server-728820] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) 2018-10-15 11:16:20,811 INFO [NiFi Web Server-729013] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) FAST 2018-10-15 11:17:11,931 INFO [NiFi Web Server-728355] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for () PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 1.1.1.1) 2018-10-15 11:17:11,966 INFO [NiFi Web Server-729217] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) 2018-10-15 11:17:11,985 INFO [NiFi Web Server-729215] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) When change org.apache.nifi to log level="DEBUG", the nifi-app.log get overflow by.. Not sure if that is a issue.. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-1] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7501e256' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-43] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@706658f2' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-33] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2272bf22' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-43] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@21fdf62a' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-64] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@28592572' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-11] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@af48695' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-45] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@fe17bc0' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-7] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@18db7949' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-44] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@f91f797' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-3] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5a9bbd7f' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-54] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5ed37c9a' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-44] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@43972b17' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-51] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3300301' has been cancelled. ... View more

Hi We are facing performance problem at Nifi UI. Sometime it takes around 6-14 sec. when moving a processor at the UI. Questions: 1) How to debug the UI which is slow? 2) Is overflow of cancelled tasks normal when setting to DEBUG? SLOW 2018-10-15 11:16:14,645 INFO [NiFi Web Server-729217] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<JWT token>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 10.129.40.59) 2018-10-15 11:16:14,681 INFO [NiFi Web Server-728820] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_><NIFI_URL_01><CN=NIFI_URL_02, OU=Internal PKI, O=COMPANY, C=DK>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) 2018-10-15 11:16:20,811 INFO [NiFi Web Server-729013] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_><NIFI_URL_01><CN=NIFI_URL_02, OU=Internal PKI, O=COMPANY, C=DK>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) FAST 2018-10-15 11:17:11,931 INFO [NiFi Web Server-728355] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<JWT token>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 10.129.40.59) 2018-10-15 11:17:11,966 INFO [NiFi Web Server-729217] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_><NIFI_URL_01><CN=NIFI_URL_02, OU=Internal PKI, O=COMPANY, C=DK>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) 2018-10-15 11:17:11,985 INFO [NiFi Web Server-729215] o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (<_USER_><NIFI_URL_01><CN=NIFI_URL_02, OU=Internal PKI, O=COMPANY, C=DK>) PUT https://NIFI_URL_01:9091/nifi-api/processors/be6b3028-e778-1f93-ae64-9a6552036e77 (source ip: 0.0.0.0) When change org.apache.nifi to log level="DEBUG", the nifi-app.log get overflow by.. Not sure if that is a issue.. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-1] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7501e256' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-43] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@706658f2' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-33] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2272bf22' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-43] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@21fdf62a' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-64] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@28592572' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-11] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@af48695' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-45] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@fe17bc0' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-7] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@18db7949' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-44] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@f91f797' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-3] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5a9bbd7f' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-54] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@5ed37c9a' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-44] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@43972b17' has been cancelled. 2018-10-15 14:04:56,165 DEBUG [Timer-Driven Process Thread-51] org.apache.nifi.engine.FlowEngine A flow controller execution task 'java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3300301' has been cancelled. ... View more

Hi, We have created a connection with a ODBC from Informatica to Hive, but special chars as привет is convert to □ . The Hive table data is showed fine in Beeline, Ambari Hive View, JDBC 64bit but not ODBC 64bit. The documentation link page 18, tell that is is possible to add server-side property to the ODBC and that these options can be showed by type set -v. I can figure out to run the command to see the properties. What we are looking for is if any encoding/code-page can be set to solve the encoding problem. Questions: 1) Have any other had problem with UTF-8 chars like привет, to be showed correctly with Hortonworks ODBC 54bit? 2) Any guidance to how the server-site options kan be displyed. From documentation: 1. To create a server-side property, click Add, then type appropriate values in the Key and Value fields, and then click OK Note: For a list of all Hadoop and Hive server-side properties that your implementation supports, type set -v at the Hive CLI command line or Beeline. You can also execute the set -v query after connecting using the driver. ... View more

Scenario: User X run a %livy.pyspark job in notebook AnalysisX 5 seconds after user Y run a %livy.pyspark job in notebook AnalysisY Y have to wait for X's spark job to finish, which is not effective. How is it possible in HDP2.5 through Livy impersonated, to run multiple spark jobs from Zeppeline at the same time? ... View more

Hi I am having problem understand what to change to make another user run a workflow. User A submit a workflow in Oozie. A is able to run and it work fine. Now user B want to run the same workflow. But is not authorized. oozie-error-message: E0508: User [XXXX] not authorized for WF job [0000012-161010094223089-oozie-oozi-W] What we want is a developer to create a workflow and what this workflow can be access through the Oozie API by a external service. Question 1) Where is this authorized being controlled in Oozie? 2) How can auth being change for other users/service account to run workflows? Error: HTTP/1.1 401 Unauthorized Server: Apache-Coyote/1.1 WWW-Authenticate: Negotiate Set-Cookie: hadoop.auth=; Path=/; HttpOnly Content-Type: text/html;charset=utf-8 Content-Length: 997 Date: Wed, 26 Oct 2016 13:03:51 GMT HTTP/1.1 401 Unauthorized Server: Apache-Coyote/1.1 WWW-Authenticate: Negotiate YGYGCSqGSIb3EgECAgIAb1cwVaADAgEFoQMCAQ+iSTBHoAMCAReiQAQ+Ar4Y2B5Cx+YJTHB3R7olNUPQNMZTqZfdTAoO0RRLuA20m9LgfB3LpyRaGwuPRF3tio3FREDxUJ7TQoZPdm8= Set-Cookie: hadoop.auth="u=XXXX&p=XXXX@XX.XX&t=kerberos&e=1477523031321&s=OKOKcrY3HZXdjhNQKpEr4FXiLSQ="; Path=/; HttpOnly oozie-error-code: E0508 oozie-error-message: E0508: User [XXXX] not authorized for WF job [0000012-161010094223089-oozie-oozi-W] Content-Type: text/html;charset=utf-8 Content-Length: 951 Date: Wed, 26 Oct 2016 13:03:51 GMT ... View more