RE: 答复: A failed Trafodion installation can lead to the hbase:meta table staying in the FAILED_OPEN state.

Hi, Yes Ming that’s an excellent point. Though I didn’t mention it, my first attempt at recovery centered on trying to verify the hbase:meta table was okay using the HBase OfflineMetaRepair utility. Even after that tool said the table was fine, I still tried another restart because the

Re: 答复: A failed Trafodion installation can lead to the hbase:meta table staying in the FAILED_OPEN state.

HI there All- I have made a jira for the installer, based on this issue. https://issues.apache.org/jira/browse/TRAFODION-1884 Thanks! On Wed, Mar 9, 2016 at 8:41 AM, Liu, Ming (Ming) wrote: > Thanks Denies to share this. We saw this issue during an expansion of > Trafodion

Re: perl-DBD-SQLite*

Okay perfect. This is exactly what I wanted to know. Thanks to Eason and Dennis for actually digging into the code!! Appreciate it! On Wed, Mar 9, 2016 at 5:36 AM, Zhang, Yi (Eason) wrote: > Hi, > > In my VM environment there’s only perl-DBD-SQLite installed, both ‘sqgen’ >

答复: how to tell the most time-consuming part for a given Trafodion query plan?

Thank you Selva, Gunnar pointed me to the sql manual guide before. I should read it more carefully. There are a lot of information in your reply, I need some time to understand all of them. But for my major question mark ‘how to tell running time in different part for a given query’ is

Re: Request for information about the installer's new management nodes prompt.

Hi, Amanda can correct me if I'm wrong but I think that this refers to configurations where the distribution manager (Ambari or Cloudera) runs on separate nodes in the cluster. That is, the nodes are part of the cluster but is not used as edge nodes or storage nodes and, therefore, should not

RE: perl-DBD-SQLite*

Hi, I’m not a yum expert, but could the ‘*’ actually be part of a glob expression? For example on a CentOS 6.5 node I did: yum list installed "perl-DBD-SQLite*" … perl-DBD-SQLite.x86_64 1.27-3.el6