On 11/29/2017 10:29 AM, S G wrote: > Shouldn't the slow logger print the document also which took so long? > The /select query and /get query handlers do a good job of helping in such > cases as the entire URL is present there (I know its GET vs POST thing). > But we should probably print the POST request's payload for /update > requests to debug more?
In addition to what Erick said: The specific log message you provided is from an update request in javabin format. This means that the POST content is binary -- very likely consisting of unprintable bytes, which could cause problems if the content is logged. Thanks, Shawn
