[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3786:
---------------------------------------
master and 8.12 docs have been updated to include the property on the vdb definition page as well.
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: TEIID-3786
> URL: https://issues.…
[View More]jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-3786:
----------------------------------------
Customer just tried the vdb property lazy-invalidate=true and it worked in 6.1.3 so I guess it was backported. I don't see that property listed in the docs for vdb props though so will log a DV doc bug for that as well. Thanks for you help
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ---------…
[View More]-------------------------------------------------------------
>
> Key: TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3786:
---------------------------------------
It's definitely in 6.2. It was logged off of 7.7 case though. There doesn't appear to be any back ports.
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: TEIID-3786
> URL: https://…
[View More]issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Debbie Steigner closed TEIID-3786.
----------------------------------
Resolution: Rejected
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type:…
[View More] Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3786:
------------------------------------------------
dsteigne(a)redhat.com changed the Status of [bug 1274862|https://bugzilla.redhat.com/show_bug.cgi?id=1274862] from NEW to CLOSED
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: …
[View More]TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3786:
------------------------------------------------
dsteigne(a)redhat.com changed the Status of [bug 1274860|https://bugzilla.redhat.com/show_bug.cgi?id=1274860] from NEW to CLOSED
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: …
[View More]TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-3786:
----------------------------------------
ok looking at https://issues.jboss.org/browse/TEIID-2840 it was changed, would that have been in DV 6.1? If so, it's the DV docs that are wrong - https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Virtuali...
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ---------------------------…
[View More]-------------------------------------------
>
> Key: TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3786:
---------------------------------------
See also https://docs.jboss.org/author/display/teiid811final/Internal+Materialization and https://issues.jboss.org/browse/TEIID-2840
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: TEIID-3786
> …
[View More] URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3786:
---------------------------------------
I'm not sure I follow this issue.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1]
The first line indicates that the is an invalidating refresh. Lines 2-5 are an expected progression to loading.
Then there is an error, which presumably aborts the refresh.
Is this expected to not be …
[View More]invaliding? Or is there something unexpected happening after the failed refresh?
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ----------------------------------------------------------------------
>
> Key: TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months
[JBoss JIRA] (TEIID-3786) Cache hint TTL invalidates cache before the reload/refresh is complete
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3786?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3786:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1274860, https://bugzilla.redhat.com/show_bug.cgi?id=1274862 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1274860)
> Cache hint TTL invalidates cache before the reload/refresh is complete
> ---------------------------------------------------------…
[View More]-------------
>
> Key: TEIID-3786
> URL: https://issues.jboss.org/browse/TEIID-3786
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Cache hint TTL invalidates cache before the reload/refresh is complete, if the reload fails so do the user queries because the cache is invalid.
> According to the Caching documentation when using Cache Hint:
> Important
> In this example, the user query started a new refresh/load job, however it did not invalidate the current results. So, in the mean time while the load/refresh job is running, the user queries continue to return the expired results. When the refresh/reload job completes, then the old results will be flushed and new results will be used for any future user requests.
> The main idea here is not to block user queries while the refresh job is running. This is mainly due to the fact that you can not predict how long a refresh job going to run.
> From the customer logs, you can see that the Matview is invalidated before it reloads[1], so if the reload fails for some reason then the user queries fail. I assume this is a bug not a documentation error
> [1]
> 11:16:08,073 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to NEEDS_LOADING null 1445613368074 old values LOADED false
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 invalidating
> 11:16:08,074 DEBUG [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) org.teiid.query.tempdata.GlobalTableStoreImpl$MatTableInfo@3be0afa0 setting matState to LOADING null 1445613368074 old values NEEDS_LOADING false
> 11:16:08,074 INFO [org.teiid.PROCESSOR.MATVIEWS] (Worker2_QueryProcessorQueue8) TEIID30013 Loading materialized view table #MAT_MBDVCONF.CLIENT
> 11:16:08,076 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue9) /RMoMwxJGpmf.1.12.3 Processing NEW request: SELECT g_0.ID, g_0.NAME, g_0.CREATE_DT FROM mbdvconf_sm.CLIENT AS g_0
> 11:16:26,027 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (Worker3_QueryProcessorQueue9) Destroying connection that is not valid, due to the following exception: oracle.jdbc.driver.T4CConnection@6d07b3ed: java.sql.SQLException: pingDatabase failed status=-1
> at org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker.isValidConnection(OracleValidConnectionChecker.java:68)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1100)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 5 months