3 Commits

Author	SHA1	Message	Date
Harshavardhana	70d2cb5f4d	rpc: Remove time check for each RPC calls. (#3804) ... This removal comes to avoid some redundant requirements which are adding more problems on a production setup. Here are the list of checks for time as they happen - Fresh connect (during server startup) - CORRECT - A reconnect after network disconnect - CORRECT - For each RPC call - INCORRECT. Verifying time for each RPC aggravates a situation where a RPC call is rejected in a sequence of events due to enough load on a production setup. 3 second might not be enough time window for the call to be initiated and received by the server.	2017-02-24 18:26:56 -08:00
Harshavardhana	e1142e99f2	rpc/lock: Make sure to capitalize for proper marshalling. (#3544) ... Distributed setup stopped working for certain types of operations `6d10f4c19af6861e4de1b22ac20a3e5136f69d67` This is a regression. Fixes #3543	2017-01-08 20:37:53 -08:00
Bala.FA	6d10f4c19a	Adopt dsync interface changes and major cleanup on RPC server/client. ... * Rename GenericArgs to AuthRPCArgs * Rename GenericReply to AuthRPCReply * Remove authConfig.loginMethod and add authConfig.ServiceName * Rename loginServer to AuthRPCServer * Rename RPCLoginArgs to LoginRPCArgs * Rename RPCLoginReply to LoginRPCReply * Version and RequestTime are added to LoginRPCArgs and verified by server side, not client side. * Fix data race in lockMaintainence loop.	2017-01-02 20:57:42 +05:30