[jira] [Closed] (TRAFODION-2061) SQL Error 1583 "Sequence metadata could not be updated"

[Jarek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek closed TRAFODION-2061.

Resolution: Duplicate

> SQL Error 1583 "Sequence metadata could not be updated"
> ---
>
> Key: TRAFODION-2061
> URL: https://issues.apache.org/jira/browse/TRAFODION-2061
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-general
>Affects Versions: 2.1-incubating
> Environment: OS Type and Version: Centos  release 6.7
> Trafodion SW Version: 2.1
> CDH Version: 5.5.4
> JDK Version: 1.7.0_67
>Reporter: Jarek
> Attachments: 
> coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log, 
> coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log
>
>
> Issue Description:
> When insert data using multi threads program, some insertion data is missing 
> because of SQL error 1583 "Sequence metadata could not be updated" occurred.
> Test Steps:
> Step 0. Hive Metastore Server Instance is running.
> Step 1. Start multi threads program.
> Step 2. Stop Hive Metastore Server Instance.
> Step 3. Back to multi threads program, it still running, waiting it completed.
> Step 4. Check multi threads program output and the log file.
> 1) output is,
> DEBUG: plan to delete total rows is  291488
> DEBUG: remaining rows to delete is  291400
> DEBUG: Remaining rows 310909
> DEBUG: Total rows 311000
> DEBUG: Deleted rows 88
> DEBUG: Missing insertion rows 3# please note that here 3 is 
> not fixed, if you run several times, it will be changed other number.
> Total Tests=1  Failed=1
> 2) log file attached, 
> "coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"
> 13:46:52  ***ERROR: SQLExecDirect: Expected: SQL_SUCCESS Actual: SQL_ERROR
>File: ../../../../src/coast/coast_unified/src/jmtload.c   Line: 187
>   # please note that here 187 line is used to insert a row 
> into table
>State: X01G7
>Native Error: 4294965713
>Error: [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** 
> ERROR[1583] Sequence metadata could not be updated. [2016-06-07 13:46:52]
> By the way, if skip step 3, no this kind error occurred, the output and log 
> file below,
> 1) output is,
> DEBUG: plan to delete total rows is  145895
> DEBUG: remaining rows to delete is  145809
> DEBUG: Remaining rows 310914
> DEBUG: Total rows 311000
> DEBUG: Deleted rows 86
> DEBUG: Missing insertion rows 0
> Total Tests=1  Failed=0
> 2) log file attached, 
> "coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TRAFODION-2061) SQL Error 1583 "Sequence metadata could not be updated"

[Jarek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek updated TRAFODION-2061:
-
Attachment: 
coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log

coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log

> SQL Error 1583 "Sequence metadata could not be updated"
> ---
>
> Key: TRAFODION-2061
> URL: https://issues.apache.org/jira/browse/TRAFODION-2061
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-general
>Affects Versions: 2.1-incubating
> Environment: OS Type and Version: Centos  release 6.7
> Trafodion SW Version: 2.1
> CDH Version: 5.5.4
> JDK Version: 1.7.0_67
>Reporter: Jarek
> Attachments: 
> coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log, 
> coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log
>
>
> Issue Description:
> When insert data using multi threads program, some insertion data is missing 
> because of SQL error 1583 "Sequence metadata could not be updated" occurred.
> Test Steps:
> Step 0. Hive Metastore Server Instance is running.
> Step 1. Start multi threads program.
> Step 2. Stop Hive Metastore Server Instance.
> Step 3. Back to multi threads program, it still running, waiting it completed.
> Step 4. Check multi threads program output and the log file.
> 1) output is,
> DEBUG: plan to delete total rows is  291488
> DEBUG: remaining rows to delete is  291400
> DEBUG: Remaining rows 310909
> DEBUG: Total rows 311000
> DEBUG: Deleted rows 88
> DEBUG: Missing insertion rows 3# please note that here 3 is 
> not fixed, if you run several times, it will be changed other number.
> Total Tests=1  Failed=1
> 2) log file attached, 
> "coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"
> 13:46:52  ***ERROR: SQLExecDirect: Expected: SQL_SUCCESS Actual: SQL_ERROR
>File: ../../../../src/coast/coast_unified/src/jmtload.c   Line: 187
>   # please note that here 187 line is used to insert a row 
> into table
>State: X01G7
>Native Error: 4294965713
>Error: [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** 
> ERROR[1583] Sequence metadata could not be updated. [2016-06-07 13:46:52]
> By the way, if skip step 3, no this kind error occurred, the output and log 
> file below,
> 1) output is,
> DEBUG: plan to delete total rows is  145895
> DEBUG: remaining rows to delete is  145809
> DEBUG: Remaining rows 310914
> DEBUG: Total rows 311000
> DEBUG: Deleted rows 86
> DEBUG: Missing insertion rows 0
> Total Tests=1  Failed=0
> 2) log file attached, 
> "coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2061) SQL Error 1583 "Sequence metadata could not be updated"

[Jarek (JIRA)]

Jarek created TRAFODION-2061:


 Summary: SQL Error 1583 "Sequence metadata could not be updated"
 Key: TRAFODION-2061
 URL: https://issues.apache.org/jira/browse/TRAFODION-2061
 Project: Apache Trafodion
  Issue Type: Bug
  Components: sql-general
Affects Versions: 2.1-incubating
 Environment: OS Type and Version: Centos  release 6.7
Trafodion SW Version: 2.1
CDH Version: 5.5.4
JDK Version: 1.7.0_67
Reporter: Jarek


Issue Description:
When insert data using multi threads program, some insertion data is missing 
because of SQL error 1583 "Sequence metadata could not be updated" occurred.

Test Steps:
Step 0. Hive Metastore Server Instance is running.
Step 1. Start multi threads program.
Step 2. Stop Hive Metastore Server Instance.
Step 3. Back to multi threads program, it still running, waiting it completed.
Step 4. Check multi threads program output and the log file.
1) output is,
DEBUG: plan to delete total rows is  291488
DEBUG: remaining rows to delete is  291400
DEBUG: Remaining rows 310909
DEBUG: Total rows 311000
DEBUG: Deleted rows 88
DEBUG: Missing insertion rows 3# please note that here 3 is not 
fixed, if you run several times, it will be changed other number.
Total Tests=1  Failed=1
2) log file attached, 
"coast_2016-06-07_13.43.58.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"
13:46:52  ***ERROR: SQLExecDirect: Expected: SQL_SUCCESS Actual: SQL_ERROR
   File: ../../../../src/coast/coast_unified/src/jmtload.c   Line: 187  
# please note that here 187 line is used to insert a row into 
table
   State: X01G7
   Native Error: 4294965713
   Error: [Trafodion ODBC Driver][Trafodion Database] SQL ERROR:*** ERROR[1583] 
Sequence metadata could not be updated. [2016-06-07 13:46:52]
By the way, if skip step 3, no this kind error occurred, the output and log 
file below,
1) output is,
DEBUG: plan to delete total rows is  145895
DEBUG: remaining rows to delete is  145809
DEBUG: Remaining rows 310914
DEBUG: Total rows 311000
DEBUG: Deleted rows 86
DEBUG: Missing insertion rows 0
Total Tests=1  Failed=0
2) log file attached, 
"coast_2016-06-07_13.53.49.ANSI.GBK.MultiThread.linux64.TRAF_GBK.log"






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (TRAFODION-2047) add SQL syntax support to INTERSECT

[liu ming (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on TRAFODION-2047 started by liu ming.
---
> add SQL syntax support to INTERSECT
> ---
>
> Key: TRAFODION-2047
> URL: https://issues.apache.org/jira/browse/TRAFODION-2047
> Project: Apache Trafodion
>  Issue Type: New Feature
>Reporter: liu ming
>Assignee: liu ming
>
> INTERSECT is a common SQL syntax. 
> Trafodion should support it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2060) Add support for native tinyint datatype

[Anoop Sharma (JIRA)]

Anoop Sharma created TRAFODION-2060:
---

 Summary: Add support for native tinyint datatype
 Key: TRAFODION-2060
 URL: https://issues.apache.org/jira/browse/TRAFODION-2060
 Project: Apache Trafodion
  Issue Type: Improvement
Reporter: Anoop Sharma
Assignee: Anoop Sharma
Priority: Minor


Currently, tinyint datatype(1 byte integer) in trafodion is automatically 
converted to smallint (2 byte integer) and treated like smallint.
It causes values that are beyond the tinyint range to be inserted
and selected.
Same issue happens with hive tinyint datatypes which are also
treated as smallint. That causes inconsistent behavior when that
datatype is accessed or inserted from hive vs. trafodion.

This jira is to add support for true tinyint datatype in table definitions,
cast stmts, param typing and handling of hive tables.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (TRAFODION-2060) Add support for native tinyint datatype

[Anoop Sharma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on TRAFODION-2060 started by Anoop Sharma.
---
> Add support for native tinyint datatype
> ---
>
> Key: TRAFODION-2060
> URL: https://issues.apache.org/jira/browse/TRAFODION-2060
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Anoop Sharma
>Assignee: Anoop Sharma
>Priority: Minor
>
> Currently, tinyint datatype(1 byte integer) in trafodion is automatically 
> converted to smallint (2 byte integer) and treated like smallint.
> It causes values that are beyond the tinyint range to be inserted
> and selected.
> Same issue happens with hive tinyint datatypes which are also
> treated as smallint. That causes inconsistent behavior when that
> datatype is accessed or inserted from hive vs. trafodion.
> This jira is to add support for true tinyint datatype in table definitions,
> cast stmts, param typing and handling of hive tables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-2046) change DTM's memoryUsageChore default settings to enable memory threthold

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325779#comment-15325779
 ] 

ASF GitHub Bot commented on TRAFODION-2046:
---

GitHub user traflm opened a pull request:

https://github.com/apache/incubator-trafodion/pull/542

[TRAFODION-2046]change DTM's memoryUsageChore default settings to ena…

…ble memory threthold

Change the default behavior of DTM to restrict the memory usage in Region 
Server to 90%, if above that threshold, stop all new transaction operations 
until memory released under the threshold.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/traflm/incubator-trafodion TRAFODION-2046-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafodion/pull/542.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 #542


commit 31d0bea37b7b0f09ba84495f28a6f9044e7368d6
Author: Liu Ming 
Date:   2016-06-11T08:47:41Z

[TRAFODION-2046]change DTM's memoryUsageChore default settings to enable 
memory threthold




> change DTM's memoryUsageChore default settings to enable memory threthold
> -
>
> Key: TRAFODION-2046
> URL: https://issues.apache.org/jira/browse/TRAFODION-2046
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: liu ming
>Assignee: liu ming
>
> DTM provide MemoryUsageChore to monitor the memory pressure in a 
> RegionServer, when memory is beyond a defined threshold, it will give a 
> warning or prevent new operations based on a flag.
> By default, the threshold is now 100%, and the flag is just warning. So that 
> means DTM coprocessor can use all RS memory and when it find memory pressure 
> , just print warning, instead of control new transaction.
> This will lead to un-predictable behavior for certain fat transaction.
> It is better to change the default setting to enable protection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (TRAFODION-1784) [MTDCS]statement shoud be removed from HashMap when it's closed.

[Weiqing Xu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiqing Xu resolved TRAFODION-1784.
---
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> [MTDCS]statement shoud be removed from HashMap when it's closed.
> 
>
> Key: TRAFODION-1784
> URL: https://issues.apache.org/jira/browse/TRAFODION-1784
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: connectivity-dcs
>Affects Versions: 1.3-incubating
>Reporter: Weiqing Xu
>Assignee: Weiqing Xu
> Fix For: 2.0-incubating
>
>
> TrafConnection uses a HashMap to store the statements in MTDCS code. When a 
> statement is closed, it should be removed from the HashMap, otherwise the JVM 
> garbage collection couldn't delete the unused objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TRAFODION-2046) change DTM's memoryUsageChore default settings to enable memory threthold

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325760#comment-15325760
 ] 

ASF GitHub Bot commented on TRAFODION-2046:
---

Github user traflm closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/537


> change DTM's memoryUsageChore default settings to enable memory threthold
> -
>
> Key: TRAFODION-2046
> URL: https://issues.apache.org/jira/browse/TRAFODION-2046
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: liu ming
>Assignee: liu ming
>
> DTM provide MemoryUsageChore to monitor the memory pressure in a 
> RegionServer, when memory is beyond a defined threshold, it will give a 
> warning or prevent new operations based on a flag.
> By default, the threshold is now 100%, and the flag is just warning. So that 
> means DTM coprocessor can use all RS memory and when it find memory pressure 
> , just print warning, instead of control new transaction.
> This will lead to un-predictable behavior for certain fat transaction.
> It is better to change the default setting to enable protection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)