Hadoop yana buƙatar duka ma'aunin SOCKS da masana'antar soket na abokin ciniki da ke karanta shi. Ƙara duka biyu cikin core-site.xml da aka loda don aikin:

<property>
  <name>hadoop.socks.server</name>
  <value>proxy.example.net:1080</value>
</property>
<property>
  <name>hadoop.rpc.socket.factory.class.default</name>
  <value>org.apache.hadoop.net.SocksSocketFactory</value>
</property>

A cikin Hadoop 3.4.2, SocksSocketFactory yana karanta ma'aunin host:port daga Configuration ɗinsa kuma yana ƙirƙirar soket ɗin Java da wannan hanyar. Don gwajin TCP na jama'a da aka yarda ba tare da tabbatar da wakili ba, shigar da ta dace daga jerin wakilan SOCKS na iya samar da hadoop.socks.server; tabbatar da isa ga duk wuraren yarjejeniya da tashoshin da ake buƙata.

Kafin ka ɗauka an zaɓi tsoho, duba maɓallin na musamman na yarjejeniya: NetUtils yana duba hadoop.rpc.socket.factory.class. da farko sannan sunan ajin yarjejeniya. Yana amfani da tsohon ne kawai lokacin da wannan binciken bai zaɓi masana'anta ba.

Don haka ƙima daga wani fayil da aka loda na iya barin tsohuwar masana'antar aiki. Duba Configuration mai tasiri na abokin ciniki maimakon fayil ɗin XML ɗaya a kan uwar garke.

Wannan yana aiki inda Hadoop ke amfani da wannan masana'antar TCP. Yana kiyaye halin adireshin manufa da DNS na ɓangaren; zaɓin wakili ba umarni ba ne na ƙirƙirar sakamakon DNS na maye gurbin.

Labarai masu alaƙa