Hello Artem, many thanks for your answer. 🙂 Klaus ... View more

Which clients are affected is not the case. As you described this was documented in Ambari very well. The problem was starting the Accumulo shell in /usr/hdp/2.4.0.0-169/accumulo/bin on the namenode (hosting Master, Monitor, Trace and CG): root@NameNode:/usr/hdp/2.4.0.0-169/accumulo/bin# accumulo JAVA_HOME is not set or is not a directory. Please make sure it's set globally or in conf/accumulo-env.sh Starting it on the datanode hosting the TServer, I was able to start the shell (both nodes have no JAVA_HOME entry in the environment) and to set the values to 0 meaning use the replica value from hdfs. root@hdp-accumulo-instance> config -t accumulo.metadata -f table.file.replication SCOPE | NAME | VALUE default | table.file.replication .. | 0 root@hdp-accumulo-instance> config -t accumulo.metadata -f table.file.replication SCOPE | NAME | VALUE default | table.file.replication .. | 0 Finishing with: hdfs dfs -setrep -w 3 / and the problem was solved. Many thanks for you Support. 🙂 Klaus ... View more

Hello Billie sounds good but Ambari has installed Accumulo and has not set any environment variables needed by the Accumolo shell script (/usr/hdp/2.4.0.0-169/accumulo/bin/accumulo). Could I set the parameters with Ambari e.g. in "custom accumulo-site"? ... View more

Hello Sagar! I reviewed this already. This blog concerns to mapred. As I wrote the setrep command reduce the replicas but not any new incomming ones. 🙂 Klaus ... View more