Why is a stateful remote procedure problematical

Question

In the context of distributed applications, why is a stateful remote procedure problematical? How could such a problem be overcome?

Answer 1

A stateful remote procedure problematical because If the server crashes and restarts, then the state information it was holding might be lost and the client may produce inconsistent results. When the client process crashes and restarts, the server will contain inconsistent information about the client.

To avoid such a problem we may go for the Log File to keep the status of running processes and keep it on a separate disk.