I-Hadoop idinga i-SOCKS endpoint kanye nefekthri yesokhethi yeklayenti eyifundayo. Faka kokubili ku-core-site.xml elayishwe kulo msebenzi:

<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>

Ku-Hadoop 3.4.2, SocksSocketFactory ifunda i-host:port endpoint kusuka ku-Configuration yayo futhi yakha amasokhethi e-Java ngalowo mzila. Ukuhlolwa kwe-TCP okusemthethweni okugunyaziwe ngaphandle kokuqinisekiswa kweproxy, umbhalo ofanele ovela ohlaweni lwamaproxy e-SOCKS ungahlinzeka nge-hadoop.socks.server; qinisekisa ukufinyelela kuzo zonke izindawo nezingosi zeprotocol ezidingekayo.

Ngaphambi kokucabanga ukuthi kukhethwe okuzenzakalelayo, hlola ukhiye oqondene neprotocol: i-NetUtils ihlola kuqala hadoop.rpc.socket.factory.class. bese igama elilula lekilasi leprotocol. Isebenzisa okuzenzakalelayo kuphela lapho lokho kusesha kungakhethi fekthri.

Ngakho-ke inani elivela kwelinye ifayela elayishiwe lingagcina ifekthri endala isebenza. Hlola i-Configuration yeklayenti esebenzayo hhayi ifayela elilodwa le-XML kuseva.

Lokhu kusebenza lapho i-Hadoop isebenzisa leyofekthri ye-TCP. Igcina ukuziphatha kwekomponenti ngekheli lendawo kanye ne-DNS; ukukhetha iproxy akusona isiyalo sokwakha imiphumela ye-DNS yokushintsha.

Izihloko ezihlobene