From the command line as the hdfs user: # Create the directory $ hdfs dfs -mkdir /user/<username> # Set permissions and ownership $ hdfs dfs -chown <username> /user/<username> $ hdfs dfs -chmod 700 /user/<username> ##Optionally set $ hdfs dfsadmin -setSpaceQuota <bytes_allocated> /user/<username> ## Where bytes_allocated is bytes allowed for this directory (counting replication). This is allocating space for the directory, not by username. So if the user created files in other HDFS directories, this doesn't control that. ... View more

@Wing Lo - The solution may depend on what is actually wrong. It may be that the node is just out of memory. If that's the case, a restart may resolve the issue (but it could occur again). If the index data is actually corrupt, you can take the bad node offline and the errors will stop. However, if the index is actually corrupt, you will need to fix/replace the bad data. I have not used this technique, but you might look at this https://support.lucidworks.com/hc/en-us/articles/202091128-How-to-deal-with-Index-Corruption ... View more

@Prem Kripalani That is weird. I'm looking at code for nifi 1.0.0 and line 82 does not have JAVAHOME anywhere near it. In fact, I don't see JAVAHOME anywhere. Typically that variable has an underscore "_" like JAVA_HOME. The error message "syntax error near unexpected token `newline'" is associated with an invalid redirect ">" with a newline after it. Can you find the file nifi.sh and look around line 82 to see if you see anything about JAVAHOME or if you see a redirect with no filename after it? This could be an empty variable after the ">" as well. In any case, it may be easier to reinstall Nifi than to track it down. ... View more