[jira] [Updated] (TS-1963) upgrade the version number for cache between 3.2.0 and 3.4.0
[
https://issues.apache.org/jira/browse/TS-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-1963:
---
Affects Version/s: 3.3.4
> upgrade the version number for cache between 3.2.0 and 3.4.0
>
>
> Key: TS-1963
> URL: https://issues.apache.org/jira/browse/TS-1963
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
>Affects Versions: 3.3.4
>Reporter: Bryan Call
>
> If you don't remove the cache between versions I have seen weird behavior on
> trying to get locks for reading from cache:
> perf top output:
> {code}
> Samples: 379K of event 'cycles', Event count (approx.): 159277054084
> 20.54% libpthread-2.12.so[.] pthread_mutex_trylock
> 10.59% traffic_server[.] CacheVC::openReadStartHead(int, Event*)
> 5.49% traffic_server[.]
> MutexTryLock::MutexTryLock(ProxyMutex*, EThread*)
> 3.39% libtsutil.so.3[.] ink_freelist_new
> 3.17% traffic_server[.] EThread::process_event(Event*, int)
> 3.06% [kernel] [k] _spin_lock_bh
> 2.56% libtsutil.so.3[.] ink_freelist_free
> 1.48% [kernel] [k] _spin_lock
> 1.46% traffic_server[.] EThread::execute()
> 1.44% libpthread-2.12.so[.] pthread_mutex_unlock
> 1.33% [kernel] [k] copy_user_generic_string
> 1.22% traffic_server[.] Ptr::operator=(ProxyMutex*)
> {code}
--
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
[jira] [Updated] (TS-1963) upgrade the version number for cache between 3.2.0 and 3.4.0
[
https://issues.apache.org/jira/browse/TS-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-1963:
---
Fix Version/s: 3.3.5
> upgrade the version number for cache between 3.2.0 and 3.4.0
>
>
> Key: TS-1963
> URL: https://issues.apache.org/jira/browse/TS-1963
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
>Affects Versions: 3.3.4
>Reporter: Bryan Call
> Fix For: 3.3.5
>
>
> If you don't remove the cache between versions I have seen weird behavior on
> trying to get locks for reading from cache:
> perf top output:
> {code}
> Samples: 379K of event 'cycles', Event count (approx.): 159277054084
> 20.54% libpthread-2.12.so[.] pthread_mutex_trylock
> 10.59% traffic_server[.] CacheVC::openReadStartHead(int, Event*)
> 5.49% traffic_server[.]
> MutexTryLock::MutexTryLock(ProxyMutex*, EThread*)
> 3.39% libtsutil.so.3[.] ink_freelist_new
> 3.17% traffic_server[.] EThread::process_event(Event*, int)
> 3.06% [kernel] [k] _spin_lock_bh
> 2.56% libtsutil.so.3[.] ink_freelist_free
> 1.48% [kernel] [k] _spin_lock
> 1.46% traffic_server[.] EThread::execute()
> 1.44% libpthread-2.12.so[.] pthread_mutex_unlock
> 1.33% [kernel] [k] copy_user_generic_string
> 1.22% traffic_server[.] Ptr::operator=(ProxyMutex*)
> {code}
--
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
