I use the following configuration to avoid this problem. However, I after doing this, I encounter an another problem which makes my job stuck. The issue is described in another message:
MapReduce Job stuck when using ignite hadoop accelerator <http://apache-ignite-users.70518.x6.nabble.com/MapReduce-Job-stuck-when-using-ignite-hadoop-accelerator-tc9216.html> <property name="communicationSpi"> <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> <property name="socketWriteTimeout" value="600000"/> </bean> </property> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-perform-request-when-running-MR-job-with-ignite-hadoop-accelerator-tp9193p9250.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
