Yes. The bit and server are idle, with no jobs of any sort running on them.
I just did started sqlline and it happened again. I had to cancel the show databases command after 30s. sqlline version 1.1.6 0: jdbc:drill:zk=theServer:5181> show databases; +-------------+ | SCHEMA_NAME | +-------------+ | INFORMATION_SCHEMA | | cp.default | | dfs.default | | dfs.root | | dfs.tmp | | test.default | | test.schema1 | | sys | +-------------+ 8 rows selected (29.264 seconds) On Mon, May 11, 2015 at 6:57 PM, Hanifi Gunes <[email protected]> wrote: > Can you confirm if this happens even when the particular 0.9 bit is idle? > > -Hanifi > > On Mon, May 11, 2015 at 3:53 PM, Minnow Noir <[email protected]> wrote: > > > Experiencing some slowness after upgrading one of our servers from 0.8 to > > 0.9. In particular, despite restarting the Drillbit, and even the > server, > > several times, the Drill web UI and sqlline are both so slow as to be > > unusable. > > > > For example, doing a show databases hangs indefinitely, until I CTRL-C > the > > command (e.g., after a minute). > > > > show databases; > > +-------------+ > > | SCHEMA_NAME | > > +-------------+ > > | INFORMATION_SCHEMA | > > | cp.default | > > | dfs.default | > > | dfs.root | > > | dfs.tmp | > > | test.default | > > | test.schema1 | > > | sys | > > +-------------+ > > 8 rows selected (59.044 seconds) > > > > I tried changing schemas, but had to cancel after waiting several > minutes. > > > > use test.schema1; > > +------------+------------+ > > | ok | summary | > > +------------+------------+ > > | true | Default schema changed to 'test.schema1' | > > +------------+------------+ > > 1 row selected (208.089 seconds) > > > > There are no errors or obvious issues in the logs. The server has plenty > of > > disk, CPU, and RAM free. It's running a recent version of MAPR Hadoop on > > CentOS 6.5 on EC2. It feels like something is hanging > > > > Note: This is just after starting sqlline; no actual work, which might > have > > slowed things down, has happened yet. > > > > This is what's running from a Drill perspective: > > > > ps aux | grep drill > > ec2-user 24662 0.0 0.0 106100 1328 pts/0 S 12:29 0:00 bash > > bin/drillbit.sh internal_start drillbit > > ec2-user 24697 0.3 2.3 6486240 730568 pts/0 Sl 12:29 0:36 > > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.79.x86_64/bin/java > > -Dlog.path=/opt/mapr/drill/drill-0.9.0/logs/drillbit.log -Xms1G -Xmx4G > > -XX:MaxDirectMemorySize=8G -XX:MaxPermSize=512M > > -XX:ReservedCodeCacheSize=1G -ea > > -Djava.security.auth.login.config=/opt/mapr/conf/mapr.login.conf > > -Dzookeeper.sasl.client=false -XX:+CMSClassUnloadingEnabled > > -XX:+UseConcMarkSweepGC -cp > > > > > /opt/mapr/drill/drill-0.9.0/conf:/opt/mapr/drill/drill-0.9.0/jars/*:/opt/mapr/drill/drill-0.9.0/jars/ext/*:/opt/mapr/drill/drill-0.9.0/jars/3rdparty/*:/opt/mapr/drill/drill-0.9.0/jars/classb/* > > org.apache.drill.exec.server.Drillbit > > > > Drill has been started thusly: > > > > bin/sqlline -u jdbc:drill:zk=theServer:5181 > > > > Any idea how I could troubleshoot this? > > > > Anyone else experiencing slowness after upgrading? > > > > Thank you > > >
