Dru Jensen wrote:
I am upgrading to 0.19.0. Do I still need these settings in
hadoop-site.xml?
<property>
<name>dfs.datanode.max.xcievers</name>
<value>1024</value>
</property>
You could remove it and see if you start getting the complaint about
xcievers in your datanode logs (I've not been following the issue
closely to say for sure if this config. has changed in 0.19.0 hadoop).
<property>
<name>dfs.datanode.socket.write.timeout</name>
<value>0</value>
</property>
Was this hadoop-site.xml in your hbase/conf dir? Reason I ask is
because the above is a 'client' config; for the DFSClient that hbase
hosts. This config. becomes the socket timeout. Again, I've not been
following close enough to determine whether this config. is still
needed. You could try without and if you start getting the missing
block exceptions, then you know you'll need to add it back again.
<property>
<name>mapred.child.java.opts</name>
<value>-Xmx1024m</value>
</property>
Why did you up the child heap? The hbase client was OOMEing loading
hbase? There have been no changes in hbase client memory usage so I'd
keep this one.
St.Ack
