Hi James, Thanks for your reply, in my case I don't have a cluster. It is just one machine and hence launching the drill in embedded mode. Probably this will be the same in the production environment as the client feels maintaining the cluster will be an additional effort. So trying to see if everything works fine in standalone/embedded mode. thx
Regards Prabhakar On Tue, Jul 19, 2022 at 10:58 AM James Turton <[email protected]> wrote: > Well if we're playing with hacks... :-) > > nohup drill-embedded -f <(sleep infinity) > /dev/null > > That needs a shell smart enough to do process substitution and avoids > what I guess was busy wait loop in sqlline's input reader that you ran > into. > > Back to being boring and responsible: are you sure you want to run Drill > this way? It would be a lot more natural to launch a standalone Drillbit > with drillbit.sh, having started a ZooKeeper somewhere beforehand. > > On 2022/07/19 05:30, Prabhakar Bhosale wrote: > > Hi Luoc, > > When I run the drill in embedded mode as foreground process, the %CPU > does > > not go beyond 1%. for java process. Please let me know if you need any > > additional information. thx > > > > Regards > > Prabhakar > > > > On Tue, Jul 19, 2022 at 6:57 AM luoc <[email protected]> wrote: > > > >> Hi, > >> > >> What is the cost of the CPU if you are running in a front process? > >> > >>> On Jul 18, 2022, at 14:51, Prabhakar Bhosale <[email protected]> > >> wrote: > >>> Hi Team, > >>> I am trying to run drill in embedded mode as background process with > >> below > >>> command > >>> nohup sh drill-embedded >/dev/null 2>&1 & > >>> > >>> My observation is that it takes too much CPU. After starting drill by > >> above > >>> command the output of top command against java process shows %CPU > >> anything > >>> between 150 to 175%. > >>> > >>> So any recommended way to run drill in embedded mode in background? > >> thanks > >>> REgards > >>> Prabhakar > >> > >
