We ran into a problem today that looks like it might be related to this: https://issues.apache.org/jira/browse/KUDU-1891 We had a client app crash with this same kind of error: "not enough mutation buffer space remaining for operation". Currently the client app was queuing up a number of writes and doing manual flushing at the end of the set of transactions. We're using the kudu-python api and would like to better understand the behavior of the different flushing modes... (assuming SessionConfiguration.FlushMode is the thing we should be looking at). Are there any global settings to tweak to allow a larger buffer? What would be the pro's and con's of this? Would explicitly using KuduSession.setFlushMode(AUTO_FLUSH_SYNC) make any difference?
Shawn Terry Analytics Systems Architect Komatsu Mining Corp. Group 15802 - 116 Avenue Edmonton Alberta T5M 3S5 Canada Office: (1) 780-239-8179 [cid:[email protected]]<http://mining.komatsu/> This electronic mail transmission contains information from Joy Global Inc. which is confidential, and is intended only for the use of the proper Addressee. If you are not the intended recipient, please notify us immediately at the return address on this transmission, and delete this message and any attachments from your system. Unauthorized use, copying, disclosing, distributing, or taking any action in reliance on the contents of this transmission is strictly prohibited and may be unlawful. Privacy-JGI
