[JBoss JIRA] (TEIID-2404) Expose buffermanager monitoring properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2404?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2404.
---------------------------------
> Expose buffermanager monitoring properties
> ------------------------------------------
>
> Key: TEIID-2404
> URL: https://issues.jboss.org/browse/TEIID-2404
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.3
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> We should expose:
> BufferServiceImpl.getUserBufferSpace - the number of megs currently used by the buffermanager disk storage.
> A rough total of the memory buffer space used can be added, which would be from the BufferFrontedCacheStore concurrent bits set X block size.
> Also the BufferManagerImpl could report the total estimate of objects held in memory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIID-2322) ReusableExecution issue with large dependent joins
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2322?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2322.
---------------------------------
> ReusableExecution issue with large dependent joins
> --------------------------------------------------
>
> Key: TEIID-2322
> URL: https://issues.jboss.org/browse/TEIID-2322
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> Large dependent joins can be split among multiple queries that can be issued in parallel with the same node id (but different execution ids). The reusable execution is reusing based upon node id, so the logic either needs to create multiple executions for the parallel case or we need to be explicit about this possibility and have the translator developer check the execution id in the translator and respond appropriately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIID-196) Support creation of temp tables on physical sources.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ]
Steven Hawkins closed TEIID-196.
--------------------------------
> Support creation of temp tables on physical sources.
> ----------------------------------------------------
>
> Key: TEIID-196
> URL: https://issues.jboss.org/browse/TEIID-196
> Project: Teiid
> Issue Type: Feature Request
> Components: Connector API, Query Engine
> Affects Versions: 6.0.0
> Reporter: Ken Johnson
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> This is a multi-part request.
> First, the system should support creation of temporary tables using a physical backing store rather than buffer manger. Given multi-pass SQL's heavy use of temp tables, buffer manager can easily be overloaded with large interim results stored in temp tables.
> Second, this should be a user-configurable behavior. For example, user might be able to choose a system-level or session-level default from among:
> -- memory/cache
> -- a source represented by a connector binding
> -- a distinct temp source defined with it's own connection parameters (possibly another schema in the repository DB instance)
> Ideally default selectoin should be override-able at temp table creation time through a DDL extension
> In the case where multiple temp tables have been created on a source via connector, the query planner should recognize this and leverage pushdown to the temp store when later query passes access multiple temp tables.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (TEIID-2364) Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2364?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2364.
---------------------------------
> Binding host interface with 0.0.0.0 fails to start JBOSS AS 7.1.1 successfully with Teiid 8.2 in domain mode
> ------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2364
> URL: https://issues.jboss.org/browse/TEIID-2364
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2
> Environment: Ubuntu 10.04 Linux running on a VirtualCenter VM
> Reporter: Jose Chavez
> Assignee: Ramesh Reddy
> Labels: 0.0.0.0, 8.2, Binding, JBOSS, Ports, Teiid, already, conflict, in, use
> Fix For: 8.3
>
>
> After installing/extracting JBOSS AS 7.1.1 and overlaying Teiid 8.2 final on top, fix a couple of issues in the JBOSS_HOME/bin/scripts/teiid-domain-mode-install.cli, it looks like Teiid 8.3 Beta 1 has fixed these syntax issues. Anyway, once Teiid is down, start JBOSS AS using domain.sh -b=0.0.0.0 -bmanagement=0.0.0.0, this will start JBOSS like a champ, no problems. Now run the teiid-domain-mode-install.cli file, "./jboss-cli.sh --file=scripts/teiid-domain-mode-install.cli" from the JBOSS_HOME/bin directory, if there are no errors with the cli file you will see all the changes succeed, but if you scroll up you will see stack traces indicating "address already in use". You can stop JBOSS and then restart again binding to 0.0.0.0 to get a better view of all the errors as well. Based on my testing and analysis of ports I think the issue is with:
>
> tcp 0 0 hostname:54200 *:* LISTEN 14115/java
> It looks like when JBOSS start successfully by binding to an external address I see these two ports are opened:
>
> tcp 0 0 hostname:54201 *:* LISTEN 14115/java
> tcp 0 0 hostname:54202 *:*
>
> but when binding to 0.0.0.0 those do not get opened so my hunch is that the problem lies somewhere in this area. Also JDBC and ODBC teiid ports do not get opened in this case where as they do when binding to an external ip.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months