[jira] [Commented] (TRAFODION-1819) UPDATE STATS should not be allowed in a user transaction
[ https://issues.apache.org/jira/browse/TRAFODION-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15139826#comment-15139826 ] ASF GitHub Bot commented on TRAFODION-1819: --- GitHub user DaveBirdsall opened a pull request: https://github.com/apache/incubator-trafodion/pull/313 [TRAFODION-1819] Disallow UPDATE STATS in a user transaction UPDATE STATS sometimes does DDL and DML under the covers, and likes to start its own transactions for this purpose. Trafodion doesn't support mixed DDL and DML in the same transaction. Therefore, it makes sense for UPDATE STATS to check for a user transaction up front, and raise an error if there is one running. You can merge this pull request into a Git repository by running: $ git pull https://github.com/DaveBirdsall/incubator-trafodion Trafodion1819 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/313.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #313 commit 6073986a03d19be327619976559e59772b43c9e7 Author: Dave BirdsallDate: 2016-02-09T21:15:40Z Disallow UPDATE STATS in a user transaction > UPDATE STATS should not be allowed in a user transaction > > > Key: TRAFODION-1819 > URL: https://issues.apache.org/jira/browse/TRAFODION-1819 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-cmp >Affects Versions: 2.0-incubating, 1.3-incubating > Environment: Any >Reporter: David Wayne Birdsall >Assignee: David Wayne Birdsall > > UPDATE STATISTICS sometimes will do a mix of DDL and DML statements. These > cannot be mixed in one transaction. Therefore, UPDATE STATISTICS should not > be allowed in a user transaction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1820) HBase error after a failed bulk load in Trafodion
Hans Zeller created TRAFODION-1820: -- Summary: HBase error after a failed bulk load in Trafodion Key: TRAFODION-1820 URL: https://issues.apache.org/jira/browse/TRAFODION-1820 Project: Apache Trafodion Issue Type: Bug Components: sql-general Affects Versions: 1.1 (pre-incubation) Environment: Any Reporter: Hans Zeller When using the Trafodion bulk loader (LOAD statement), if the load fails in the middle, it may leave HBase in a state where the HMaster produces security-related errors. In the case I saw, the HMaster failed to start, due to these errors. Here is an example: Unhandled exception. Starting shutdown. java.io.IOException: Received error when attempting to archive files ([class org.apache.hadoop.hbase.backup.HFileArchiver$FileablePath, file:hdfs://ip-10-0-0-132.ec2.internal:8020/hbase/.tmp/data/default/TRAFODION.SEABASE.LSTATS1/03a60516389fcc3e02e5de07f936cbb1/#1, class org.apache.hadoop.hbase.backup.HFileArchiver$FileablePath, file:hdfs://ip-10-0-0-132.ec2.internal:8020/hbase/.tmp/data/default/TRAFODION.SEABASE.LSTATS1/03a60516389fcc3e02e5de07f936cbb1/mt_, class org.apache.hadoop.hbase.backup.HFileArchiver$FileablePath, file:hdfs://ip-10-0-0-132.ec2.internal:8020/hbase/.tmp/data/default/TRAFODION.SEABASE.LSTATS1/03a60516389fcc3e02e5de07f936cbb1/recovered.edits]), cannot delete region directory. at org.apache.hadoop.hbase.backup.HFileArchiver.archiveRegion(HFileArchiver.java:148) at org.apache.hadoop.hbase.master.MasterFileSystem.checkTempDir(MasterFileSystem.java:508) at org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:149) at org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:126) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:611) at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:169) at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1484) at java.lang.Thread.run(Thread.java:745) The solution is to do a "chown hbase:hbase" command in HDFS, to give the files to the hbase user. A fix for this problem might do this chown operation earlier in the Trafodion code path, or use some other method to avoid the security error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1821) installer ldap config fails to find lapconfigcheck
Steve Varnau created TRAFODION-1821: --- Summary: installer ldap config fails to find lapconfigcheck Key: TRAFODION-1821 URL: https://issues.apache.org/jira/browse/TRAFODION-1821 Project: Apache Trafodion Issue Type: Bug Components: installer Affects Versions: 2.0-incubating Reporter: Steve Varnau This failure is visible in daily test jobs. Example: http://traf-testlogs.esgyn.com/PullReq/313/419/jdbc_test-cdh/Install_Start.log ***INFO: Checking LDAP Configuration file for errors. /usr/lib/trafodion/installer/traf_sqgen: line 76: ldapconfigcheck: command not found ***ERROR: traf_authentication_config not configured correctly. ***ERROR: Install will continue WITHOUT simple security turned on. ***ERROR: Please review wiki for manual steps to setup simple security. ***INFO: starting Trafodion instance -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1818) Initial build gives maven error
[ https://issues.apache.org/jira/browse/TRAFODION-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1513#comment-1513 ] ASF GitHub Bot commented on TRAFODION-1818: --- GitHub user svarnau opened a pull request: https://github.com/apache/incubator-trafodion/pull/314 [TRAFODION-1818] Parallel build with maven caused error Add dependencies in sqf/Makefile to prevent collision of maven builds downloading dependencies. Replace spaces in hbasetmlib2/Makefile with tabs. Makefile syntax requires initial tab for shell commands. You can merge this pull request into a Git repository by running: $ git pull https://github.com/svarnau/incubator-trafodion maven_dep Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/314.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #314 commit 5d4a72cac0e53d59a0e4ce85acfb1a60711ca203 Author: Steve VarnauDate: 2016-02-09T23:25:26Z [TRAFODION-1818] Parallel build with maven caused error Add dependencies in sqf/Makefile to prevent collision of maven builds downloading dependencies. Replace spaces in hbasetmlib2/Makefile with tabs. Makefile syntax requires initial tab for shell commands. > Initial build gives maven error > --- > > Key: TRAFODION-1818 > URL: https://issues.apache.org/jira/browse/TRAFODION-1818 > Project: Apache Trafodion > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 2.0-incubating >Reporter: Steve Varnau >Assignee: Steve Varnau > > Subsequent trafodion builds work, but initial one gets an error. This can be > replicated by removing or re-naming your maven repository (~/.m2/repository). > Sample errors: > [ERROR] Failed to execute goal on project trafodion-utility: Could not > resolve dependencies for project > org.trafodion.utility:trafodion-utility:jar:2.0.0: Failed to collect > dependencies for [org.apache.hbase:hbase-server:jar:0.98.6-cdh5.3.0 > (compile), org.apache.hbase:hbase-client:jar:0.98.6-cdh5.3.0 (compile)]: > Failed to read artifact descriptor for org.mortbay.jetty:jsp-2.1:jar:6.1.14: > Could not find artifact org.mortbay.jetty:project:pom:6.1.14 in cloudera > (https://repository.cloudera.com/artifactory/cloudera-repos/) -> [Help 1] > ##(HBASE_UTIL) > in another build of same version of source code: > [ERROR] Failed to execute goal on project trafodion-utility: Could not > resolve dependencies for project > org.trafodion.utility:trafodion-utility:jar:2.0.0: The following artifacts > could not be resolved: com.yammer.metrics:metrics-core:jar:2.2.0, > com.google.guava:guava:jar:12.0.1, > com.github.stephenc.high-scale-lib:high-scale-lib:jar:1.1.1, > org.apache.commons:commons-math:jar:2.1, > org.mortbay.jetty:jsp-2.1:jar:6.1.14, > org.mortbay.jetty:jsp-api-2.1:jar:6.1.14, > org.mortbay.jetty:servlet-api-2.5:jar:6.1.14, > org.jamon:jamon-runtime:jar:2.3.1, org.codehaus.jackson:jackson-xc:jar:1.7.1, > org.cloudera.htrace:htrace-core:jar:2.04, > com.github.stephenc.findbugs:findbugs-annotations:jar:1.3.9-1, > commons-codec:commons-codec:jar:1.7, io.netty:netty:jar:3.6.6.Final: Could > not find artifact com.yammer.metrics:metrics-core:jar:2.2.0 in cloudera > (https://repository.cloudera.com/artifactory/cloudera-repos/) -> [Help 1] > ##(HBASE_UTIL) > In both cases, the same goal got an error, but complained about different > dependency. Subsequent build works, until repository removed to start fresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1822) Update website to use new Apache logos
Gunnar Tapper created TRAFODION-1822: Summary: Update website to use new Apache logos Key: TRAFODION-1822 URL: https://issues.apache.org/jira/browse/TRAFODION-1822 Project: Apache Trafodion Issue Type: Bug Components: documentation Affects Versions: 2.0-incubating Environment: All Reporter: Gunnar Tapper Fix For: 2.0-incubating Apache has created new logos. The Trafodion website must be updated to use said logos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1822) Update website to use new Apache logos
[ https://issues.apache.org/jira/browse/TRAFODION-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140321#comment-15140321 ] Gunnar Tapper commented on TRAFODION-1822: -- Checked in. Pull request 316. > Update website to use new Apache logos > -- > > Key: TRAFODION-1822 > URL: https://issues.apache.org/jira/browse/TRAFODION-1822 > Project: Apache Trafodion > Issue Type: Bug > Components: documentation >Affects Versions: 2.0-incubating > Environment: All >Reporter: Gunnar Tapper >Assignee: Gunnar Tapper > Fix For: 2.0-incubating > > > Apache has created new logos. The Trafodion website must be updated to use > said logos. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1648) Synchronization issues in TrxRegion* coprocessor code for Region split/balance
[ https://issues.apache.org/jira/browse/TRAFODION-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trina Krug resolved TRAFODION-1648. --- Resolution: Fixed > Synchronization issues in TrxRegion* coprocessor code for Region > split/balance > --- > > Key: TRAFODION-1648 > URL: https://issues.apache.org/jira/browse/TRAFODION-1648 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm >Reporter: Trina Krug >Assignee: Trina Krug > > --New transactions become disabled in preClose/preSplit, but other requests > such as commitRequest are allowed to get through after this point. This > poses an issue when gathering/writing transaction state at flush time. A > slight design modification is required. > --In addition, detailed review and possible modification of shared lists > should be done in this region split/balance area, including those affected > above. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1814) REST Servers' pstack API does not return pstack information of process
[ https://issues.apache.org/jira/browse/TRAFODION-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15139269#comment-15139269 ] ASF GitHub Bot commented on TRAFODION-1814: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/311 > REST Servers' pstack API does not return pstack information of process > -- > > Key: TRAFODION-1814 > URL: https://issues.apache.org/jira/browse/TRAFODION-1814 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Venkat Muthuswamy >Assignee: Venkat Muthuswamy > > The REST servers pstack api does not work as expected. The REST API uses the > sqpstack script under the covers. While the sqpstack works as expected, the > REST APIs do not return the complete results. > The API to get pstack of all processes does not return information for all > processes. For example if sqpstack returns pstack for 2 processes, only the > first pstack information is returned. > http://:4200/v1/servers/pstack > The API to get pstack for a user specified process returns an exception > instead of the pstack info, even though the underlying sqpstack command works > fine. > http://:4200/v1/servers/pstack/program/ > The response is an exception string > { > "RemoteException": { > "javaClassName": "org.trafodion.rest.NotFoundException", > "exception": "NotFoundException", > "message": "No pstack resources found" > } > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1814) REST Servers' pstack API does not return pstack information of process
[ https://issues.apache.org/jira/browse/TRAFODION-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Muthuswamy resolved TRAFODION-1814. -- Resolution: Fixed code delivered > REST Servers' pstack API does not return pstack information of process > -- > > Key: TRAFODION-1814 > URL: https://issues.apache.org/jira/browse/TRAFODION-1814 > Project: Apache Trafodion > Issue Type: Bug >Reporter: Venkat Muthuswamy >Assignee: Venkat Muthuswamy > > The REST servers pstack api does not work as expected. The REST API uses the > sqpstack script under the covers. While the sqpstack works as expected, the > REST APIs do not return the complete results. > The API to get pstack of all processes does not return information for all > processes. For example if sqpstack returns pstack for 2 processes, only the > first pstack information is returned. > http://:4200/v1/servers/pstack > The API to get pstack for a user specified process returns an exception > instead of the pstack info, even though the underlying sqpstack command works > fine. > http://:4200/v1/servers/pstack/program/ > The response is an exception string > { > "RemoteException": { > "javaClassName": "org.trafodion.rest.NotFoundException", > "exception": "NotFoundException", > "message": "No pstack resources found" > } > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)