kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amit Adhau <amit.ad...@globant.com>
Subject Re: Setting flags flush_threshold_mb and cfile_do_on_finish
Date Tue, 24 May 2016 17:55:55 GMT
Thanks Adar, I have installed Kudu 0.8 using cloudera parcel. Can you
please suggest the better way to set these gflags.

Thank you,
Amit
On May 24, 2016 10:29 PM, "Adar Dembo" <adar@cloudera.com> wrote:

> It's best to set these gflags the same way you've set any other Kudu
> gflags. Have you installed Kudu from Cloudera's RPM packages? Using a
> Cloudera parcel? Or are you just running your own binaries directly?
>
> Let me know how your setup looks and I can give you better advice.
>
> On Tue, May 24, 2016 at 5:34 AM, Amit Adhau <amit.adhau@globant.com>
> wrote:
>
>> Hi,
>>
>> We were working on performance improvement part for kudu insert and
>> currently inserting 3M records in 50 seconds and while doing so, we have
>> gone through the recent ycsb benchmark article and would like to set the
>> flags flush_threshold_mb and cfile_do_on_finish, however when we set it
>> using kudu-tserver command, the flags remains their temporarily and after
>> kudu re-start they also, gets changed to default value.
>>
>> Can you please suggest, how can we set these flags properly and if there
>> could be any other factor(e.g. buffer,batch_size,partition) which we should
>> consider for insert into kudu.
>>
>> --
>> Thanks & Regards,
>>
>> *Amit Adhau* | Data Architect
>>
>> *GLOBANT* | IND:+91 9821518132
>>
>> [image: Facebook] <https://www.facebook.com/Globant>
>>
>> [image: Twitter] <http://www.twitter.com/globant>
>>
>> [image: Youtube] <http://www.youtube.com/Globant>
>>
>> [image: Linkedin] <http://www.linkedin.com/company/globant>
>>
>> [image: Pinterest] <http://pinterest.com/globant/>
>>
>> [image: Globant] <http://www.globant.com/>
>>
>> The information contained in this e-mail may be confidential. It has been
>> sent for the sole use of the intended recipient(s). If the reader of this
>> message is not an intended recipient, you are hereby notified that any
>> unauthorized review, use, disclosure, dissemination, distribution or
>> copying of this communication, or any of its contents,
>> is strictly prohibited. If you have received it by mistake please let us
>> know by e-mail immediately and delete it from your system. Many thanks.
>>
>>
>>
>> La información contenida en este mensaje puede ser confidencial. Ha sido
>> enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de
>> este mensaje no fuera el destinatario previsto, por el presente queda Ud.
>> notificado que cualquier lectura, uso, publicación, diseminación,
>> distribución o copiado de esta comunicación o su contenido está
>> estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje
>> por error le agradeceremos notificarnos por e-mail inmediatamente y
>> eliminarlo de su sistema. Muchas gracias.
>>
>>
>

-- 


The information contained in this e-mail may be confidential. It has been 
sent for the sole use of the intended recipient(s). If the reader of this 
message is not an intended recipient, you are hereby notified that any 
unauthorized review, use, disclosure, dissemination, distribution or 
copying of this communication, or any of its contents, 
is strictly prohibited. If you have received it by mistake please let us 
know by e-mail immediately and delete it from your system. Many thanks.

 

La información contenida en este mensaje puede ser confidencial. Ha sido 
enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de 
este mensaje no fuera el destinatario previsto, por el presente queda Ud. 
notificado que cualquier lectura, uso, publicación, diseminación, 
distribución o copiado de esta comunicación o su contenido está 
estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje 
por error le agradeceremos notificarnos por e-mail inmediatamente y 
eliminarlo de su sistema. Muchas gracias.


Mime
View raw message