Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2438 | 04-27-2020 03:48 AM | |
4867 | 04-26-2020 06:18 PM | |
3972 | 04-26-2020 06:05 PM | |
3210 | 04-13-2020 08:53 PM | |
4904 | 03-31-2020 02:10 AM |
02-10-2020
06:57 AM
I have found a solution. I have forgot to mention that before service is in Maintenance Mode. To perform action with service in Maintenance Mode, it is needed to use one more parameter in rest API call. This article helped me describes all extra parameters.
... View more
02-06-2020
12:27 AM
Thanks for the response @jsensharma I do not want point to a python script file and invoke the interpreter. I have scenario where python code is present in flowfile attribute or a variable and want to run it in ExecuteStreamCommand processor. I can not use ExecuteScript processor because it invokes Jython based interpreter. Am using ExecuteStreamCommand processor as I want to explicitly invoke Python 3.5 interpreter. If there is no workaround, What is standard way for having script location. Placing the script file in NiFi server might be risk because other users might accidentally modify/delete it. How to avoid it?
... View more
02-05-2020
10:33 PM
@gvbnn Those are just warnings you can ignore them ... it should not be causing Job failure. As we also see that the application_id "application_1580968178673_0001" is also generated ... So you should be able to check the status of your Yarn application in ResourceManagr UI. http://$RM_ADDRESS:8088/cluster/apps If your cluster has enough resources then you should see the progress as well for your application_id ...
... View more
02-04-2020
11:25 PM
@Quang_Vu_Blog As per kafka-connect docs the default port "rest.port" is 8083 rest.port - the port the REST interface listens on for HTTP requests So are you getting conflict on port 8003 (or there is a typo ? is it 8083) Can you try changing the "rest.port" in your worker config to something else and then try again. Also please try to run the below commands before starting kafka-connect to verify if there is any port conflict? Or if there are any bind address issue # netstat -tnlpa | grep 8083
# netstat -tnlpa | grep 8003 .
... View more
02-04-2020
11:53 AM
@johnwook Sorry, You can not change password for local user from CDSW directly. Though forgot password method is a workaround for this. Please enter this URL in browser http://cdsw.company.com/forgot-password and then follow the Wizard, you will be able to put new password here. Cheers, Spent sometime to mark this as solution if this resolves your issue.
... View more
02-04-2020
04:06 AM
Thanks You
... View more
02-03-2020
11:42 PM
Set the value of the dfs.webhdfs.enabled property in hdfs-site.xml to true. <property>
<name>dfs.webhdfs.enabled</name>
<value>true</value>
</property> Create an HTTP service user principal. kadmin: addprinc -randkey HTTP/$<Fully_Qualified_Domain_Name>@$<Realm_Name>.COM where: Fully_Qualified_Domain_Name: Host where the NameNode is deployed. Realm_Name: Name of your Kerberos realm. Create a keytab file for the HTTP principal. kadmin: xst -norandkey -k /etc/security/spnego.service.keytab HTTP/$<Fully_Qualified_Domain_Name> Verify that the keytab file and the principal are associated with the correct service. klist –k -t /etc/security/spnego.service.keytab Add the dfs.web.authentication.kerberos.principal and dfs.web.authentication.kerberos.keytab properties to hdfs-site.xml. <property>
<name>dfs.web.authentication.kerberos.principal</name>
<value>HTTP/$<Fully_Qualified_Domain_Name>@$<Realm_Name>.COM</value>
</property>
<property>
<name>dfs.web.authentication.kerberos.keytab</name>
<value>/etc/security/spnego.service.keytab</value>
</property> Restart the NameNode and the DataNodes.
... View more
02-03-2020
01:28 PM
1 Kudo
Dear Jay what to say excellent answer , you are really one of the best here
... View more