All work
- When running many concurrent SQOOP processes, some SQOOP logs are missing.BAD-1927Resolved issue: BAD-1927Vasco Marques
- CDH61/62 : Cannot execute Hbase steps on AEL SparkBAD-1914
- When running multiple SQOOP Import process on PDI Server or Carte, SQOOP logs are mixing in all the concurrent processes.BAD-1912Resolved issue: BAD-1912Li Deng
- [DEV] Fix NoClassDefFound Error on 8.3 with pigBAD-1776Resolved issue: BAD-1776Tim Kafalas
- [DEV] - Run dev-validation against the 8.3 using EMR 5.21 shim on EE.BAD-1753Resolved issue: BAD-1753Ihar Kuntsevich
- [DEV] - Include EMR 5.21 into the Pentaho 8.3 nightly build process.BAD-1752Resolved issue: BAD-1752Jacob Gminder
- [DEV] - Develop the EMR 5.21 CE shim for Pentaho 8.3BAD-1751Resolved issue: BAD-1751Jacob Gminder
- [DEV] - Develop the EMR 5.21 EE shim for Pentaho 8.3BAD-1750Resolved issue: BAD-1750Jacob Gminder
- [DEV] - Develop the EMR 5.21 Shim for Pentaho 8.3/MasterBAD-1749Resolved issue: BAD-1749
- Process Component Requests for the Submit Component Requests for the EMR 5.21 shimBAD-1718Resolved issue: BAD-1718Luc Boudreau
- Send a notification to the Component Process Reviewers.BAD-1717Resolved issue: BAD-1717
- Submit Component Requests for the EMR 5.21 shimBAD-1716Resolved issue: BAD-1716Luc Boudreau
- [DEV] - Submit the component requests for the EMR 5.21 shimBAD-1715Resolved issue: BAD-1715
- [QA] - Perform initial EMR 5.21 cluster validationBAD-1712Resolved issue: BAD-1712Viktoryia Shalkova
- [QA] - Load test data onto the EMR 5.21 clusterBAD-1711Resolved issue: BAD-1711Viktoryia Shalkova
- Perform initial cluster validation of EMR 5.21 clustersBAD-1708Resolved issue: BAD-1708
- [DEV] - Run the developer test plan using Pentaho 8.3 with the emr521 shim on EE.BAD-1705Resolved issue: BAD-1705Tim Kafalas
- [DEV] - Run the developer test plan using Pentaho 8.2 with the emr521 shim on EE.BAD-1704Resolved issue: BAD-1704Tim Kafalas
- [DEV] - Include EMR 5.21 into the Pentaho 8.2 nightly build processBAD-1703Resolved issue: BAD-1703Tim Kafalas
- [DEV] - Develop the EMR 5.21 EE shim for Pentaho 8.2BAD-1702Resolved issue: BAD-1702Tim Kafalas
- [DEV] - Develop the EMR 5.21 CE shim for Pentaho 8.2BAD-1701Resolved issue: BAD-1701Tim Kafalas
- [DEV] - Develop the EMR 5.21 Shim for Pentaho 8.2BAD-1700Resolved issue: BAD-1700
- [QA] - Perform initial HDP 3.1 cluster validationBAD-1696Resolved issue: BAD-1696Nick Belli
- [QA] - Load test data onto the HDP 3.1 clusterBAD-1695Resolved issue: BAD-1695Nick Belli
- Perform initial cluster validation of HDP 3.1 clusters.BAD-1692Resolved issue: BAD-1692
- [DEV] - Run the developer test plan using Pentaho 8.3 with the cdh610 shim on EE.BAD-1691Resolved issue: BAD-1691
- [DEV] - Run the developer test plan using Pentaho 8.2 with the HDP 3.0 on HDP 3.1 vendor versionBAD-1659Resolved issue: BAD-1659
- [DEV] - Run the developer test plan against the 8.3 cdh6.1 shim on EE.BAD-1690Resolved issue: BAD-1690Tim Kafalas
- [DEV] - Include CDH 6.1 into the Pentaho 8.3 nightly build process.BAD-1689Resolved issue: BAD-1689Tim Kafalas
- [DEV] - Develop the CDH 6.1 CE shim for Pentaho 8.3BAD-1688Resolved issue: BAD-1688Tim Kafalas
- [DEV] - Develop the CDH 6.1 EE shim for Pentaho 8.3BAD-1687Resolved issue: BAD-1687Tim Kafalas
- [DEV] - Develop the CDH 6.1 Shim for Pentaho 8.3/MasterBAD-1686Resolved issue: BAD-1686
- [QA] - Perform initial CDH 6.1 cluster validationBAD-1683Resolved issue: BAD-1683Viktoryia Shalkova
- [QA] - Load test data onto the CDH 6.1 clusterBAD-1682Resolved issue: BAD-1682Viktoryia Shalkova
- Perform initial cluster validation of CDH 6.1 clusters.BAD-1679Resolved issue: BAD-1679Viktoryia Shalkova
- Process Component Requests for the CDH 6.1.0 shim.BAD-1616Resolved issue: BAD-1616Luc Boudreau
- Send a notification to the Component Process Reviewers.BAD-1615Resolved issue: BAD-1615
- Submit Component Requests for the CDH 6.1.0 shim.BAD-1614Resolved issue: BAD-1614
- [DEV] - Submit the component requests for the CDH 6.1.0 shim.BAD-1613Resolved issue: BAD-1613
- [DEV] - Run the developer test plan using Pentaho 8.2 with the cdh610 shim on EE.BAD-1612Resolved issue: BAD-1612Tim Kafalas
- [DEV] - Include CDH 6.1.0 into the Pentaho 8.2 nightly build process.BAD-1611Resolved issue: BAD-1611Jacob Gminder
- [DEV] - Develop the CDH 6.1.0 EE shim for Pentaho 8.2BAD-1610Resolved issue: BAD-1610Jacob Gminder
- [DEV] - Develop the CDH 6.1.0 CE shim for Pentaho 8.2BAD-1609Resolved issue: BAD-1609Jacob Gminder
- [DEV] - Develop the CDH 6.1.0 Shim for Pentaho 8.2BAD-1608Resolved issue: BAD-1608
- [DEV] - Run the developer test plan against the 8.2 using cdh601 shim on EE.BAD-1573Resolved issue: BAD-1573Jacob Gminder
- [DEV] - Include CDH 601 into the Pentaho 8.2 nightly build process.BAD-1572Resolved issue: BAD-1572Jacob Gminder
- [DEV] - Develop the CDH 601 CE shim for Pentaho 8.2BAD-1571Resolved issue: BAD-1571Jacob Gminder
- [DEV] - Develop the CDH 601 EE shim for Pentaho 8.2BAD-1570Resolved issue: BAD-1570Jacob Gminder
- [DEV] - Develop the CDH 601 Shim for released Pentaho 8.2BAD-1569Resolved issue: BAD-1569Jacob Gminder
- The MapReduce step creates a metastore folder every time it is executedBAD-1439Resolved issue: BAD-1439Ricardo Rosinha
When running many concurrent SQOOP processes, some SQOOP logs are missing.
Description
Steps to Reproduce
It is necessary to run around 40-50 concurrent SQOOP processes to replicate the scenario.
Customer currently runs about 100 SQOOP processes and this issue happens 4-5 times on every cycle.
Workaround
Attachments
has Pentaho private
Details
Details
Assignee
Reporter
Labels
Edit Screen Preamble
<div class="notify info" style="margin-bottom: 10px;">
If you are a Pentaho customer, please use the <a href="http://support.pentaho.com">Customer Support portal</a> to log issues.
<p />
This system is used for logging bugs and enhancement requests only. Please use our <a href="https://community.pentaho.com">community at https://community.pentaho.com</a> if you have questions, configuration issues, or have an issue with a marketplace plugin as Pentaho does not support marketplace plugins unless written by Pentaho.
<p />
Lastly, when creating a bug, please provide as much detail as possible. To prevent unnecessary delays in reviewing your issue, please attach complete server logs, SQL/MDX logs where applicable, schemas, etc. Also, screen-shots and screen-cams are especially helpful in demonstrating the issue.
<p />
Thank-you so much,<br />
The Pentaho Team
</div>
Notice
<div class="notify info" style="margin-bottom: 10px;">
When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
</div>
Sprint Team
Story Points
Affects versions
Priority
Activity
ATRCM Official September 20, 2024 at 5:51 AM
Back in case we fixed the mixed logs, but now from time to time the SQOOP logs are missing.
We identified that the issue is linked to the fact that the ChannelId is not unique on concurrent processes that run very close to each other.
ChannelId
Thread
_time
Count of ChannelId
5c3272a7-3781-44c9-9575-3f5888542b1c
2
Thread[Thread-10676,5,main]
1
2022-02-12T19:55:37.586+0100
1
Thread[Thread-11134,5,main]
1
2022-02-12T19:56:00.091+0100
1
9d55190a-8d9a-43b6-b1f8-a6dd7cd9166b
2
Thread[Thread-11080,5,main]
1
2022-02-12T19:55:56.495+0100
1
Thread[Thread-9568,5,main])
1
2022-02-12T19:55:32.681+0100
1
093bc01c-3dc8-4197-b4b5-f8ca38ef33cc
2
Thread[Thread-19035,5,main]
1
2022-02-12T19:57:06.677+0100
1
Thread[Thread-21674,5,main]
1
2022-02-12T19:57:28.688+0100
1