[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1453:
-
Attachment: TS-1453_v2.patch
this patch base on TS-1405_v12.patch
> remove InactivityCop and enable define INACTIVI
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917710#comment-13917710
]
Bin Chen commented on TS-1405:
--
the origin event schedule policy will schedule the event(event->
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1405:
-
Attachment: patch12_test.pdf
test between original version and patch p12.
> apply time-wheel scheduler about event
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1405:
-
Attachment: linux_time_wheel_v12.patch
base master 5.0.0
> apply time-wheel scheduler about event system
> --
[
https://issues.apache.org/jira/browse/TS-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769166#comment-13769166
]
Bin Chen commented on TS-2201:
--
for supporting large cluster.
> split drainInco
[
https://issues.apache.org/jira/browse/TS-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-2201.
Resolution: Fixed
Fix Version/s: 4.1.0
> split drainIncomingChannel two thread, one handle Broadcast messag
[
https://issues.apache.org/jira/browse/TS-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2201:
-
Attachment: TS-2201.patch
> split drainIncomingChannel two thread, one handle Broadcast message and other
> han
[
https://issues.apache.org/jira/browse/TS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1637.
Resolution: Fixed
Fix Version/s: (was: 4.2.0)
4.1.0
> nodes as idle/dead if we have
[
https://issues.apache.org/jira/browse/TS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-2185.
Resolution: Fixed
Fix Version/s: 4.1.0
> support to control ClusterCom::sendSharedData frequency
>
[
https://issues.apache.org/jira/browse/TS-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2201:
Assignee: Bin Chen
> split drainIncomingChannel two thread, one handle Broadcast message and other
> hand
Bin Chen created TS-2201:
Summary: split drainIncomingChannel two thread, one handle
Broadcast message and other handle Reliable(TCP) request
Key: TS-2201
URL: https://issues.apache.org/jira/browse/TS-2201
Pr
[
https://issues.apache.org/jira/browse/TS-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2184:
Assignee: Bin Chen
> Fetch from cluster with proxy.config.http.cache.cluster_cache_local enabled
> ---
[
https://issues.apache.org/jira/browse/TS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2185:
-
Attachment: TS-2185.patch
> support to control ClusterCom::sendSharedData frequency
> --
[
https://issues.apache.org/jira/browse/TS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2185:
Assignee: Bin Chen
> support to control ClusterCom::sendSharedData frequency
> ---
Bin Chen created TS-2185:
Summary: support to control ClusterCom::sendSharedData frequency
Key: TS-2185
URL: https://issues.apache.org/jira/browse/TS-2185
Project: Traffic Server
Issue Type: Improvem
[
https://issues.apache.org/jira/browse/TS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TS-1637 started by Bin Chen.
> nodes as idle/dead if we have not heard from them in awhile
> ---
>
>
[
https://issues.apache.org/jira/browse/TS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758768#comment-13758768
]
Bin Chen commented on TS-1637:
--
mgmt_select() broadcast fd will be timeout. So checkPeers will b
[
https://issues.apache.org/jira/browse/TS-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1637:
-
Attachment: TS-1637_v2.patch
> nodes as idle/dead if we have not heard from them in awhile
> ---
[
https://issues.apache.org/jira/browse/TS-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2149:
-
Attachment: Screenshot.png
> loop in dir_clean_bucket()
> --
>
> Key: TS
Bin Chen created TS-2149:
Summary: loop in dir_clean_bucket()
Key: TS-2149
URL: https://issues.apache.org/jira/browse/TS-2149
Project: Traffic Server
Issue Type: Bug
Components: Cache
[
https://issues.apache.org/jira/browse/TS-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-2107.
Resolution: Fixed
Fix Version/s: 4.1.0
> add absolute proxy.config.http.transaction_active_timeout_in abou
[
https://issues.apache.org/jira/browse/TS-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2107:
-
Attachment: TS-2107.patch
> add absolute proxy.config.http.transaction_active_timeout_in about request
> --
[
https://issues.apache.org/jira/browse/TS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-287.
---
Resolution: Fixed
> transaction_active_timeout_in does not trigger on the first request of a
> Keep-Alive connection
[
https://issues.apache.org/jira/browse/TS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744784#comment-13744784
]
Bin Chen commented on TS-287:
-
This bug is fixed by Que Han (Li Gang).
> transact
[
https://issues.apache.org/jira/browse/TS-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1595:
Assignee: Yu Qing (was: Bin Chen)
> different domain have different origin_max_connections?
> ---
[
https://issues.apache.org/jira/browse/TS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-287:
Attachment: TS-287.patch
does not trigger becasue of set_active_timeout() success only
UnixNetVConnection.read(write)
[
https://issues.apache.org/jira/browse/TS-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-2136.
Resolution: Fixed
Fix Version/s: 3.5.0
> the first proxy.config.http.accept_no_activity_timeout is invalid
[
https://issues.apache.org/jira/browse/TS-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2136:
-
Attachment: TS-2136.patch
> the first proxy.config.http.accept_no_activity_timeout is invalid
>
Bin Chen created TS-2136:
Summary: the first proxy.config.http.accept_no_activity_timeout is
invalid
Key: TS-2136
URL: https://issues.apache.org/jira/browse/TS-2136
Project: Traffic Server
Issue Typ
[
https://issues.apache.org/jira/browse/TS-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2136:
Assignee: Bin Chen
> the first proxy.config.http.accept_no_activity_timeout is invalid
> -
[
https://issues.apache.org/jira/browse/TS-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2133:
Assignee: Bin Chen
> proxy.config.http.transaction_active_timeout_in is invalid
>
Bin Chen created TS-2133:
Summary: proxy.config.http.transaction_active_timeout_in is invalid
Key: TS-2133
URL: https://issues.apache.org/jira/browse/TS-2133
Project: Traffic Server
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TS-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2107:
-
Priority: Blocker (was: Major)
Affects Version/s: 3.3.5
Fix Version/s: 3.3.5
Assig
Bin Chen created TS-2107:
Summary: add absolute
proxy.config.http.transaction_active_timeout_in about request
Key: TS-2107
URL: https://issues.apache.org/jira/browse/TS-2107
Project: Traffic Server
[
https://issues.apache.org/jira/browse/TS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-2085:
Assignee: Bin Chen
> Can't put url in ram
>
>
> Key: TS-2085
>
Bin Chen created TS-2085:
Summary: Can't put url in ram
Key: TS-2085
URL: https://issues.apache.org/jira/browse/TS-2085
Project: Traffic Server
Issue Type: Bug
Components: Cache, HTTP
[
https://issues.apache.org/jira/browse/TS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2084:
-
Description: 1. should ts support forcing to put some very hot url in ram
by cache.config? (was: 1. should ts suppo
Bin Chen created TS-2084:
Summary: support some very hot url force to put in ram?
Key: TS-2084
URL: https://issues.apache.org/jira/browse/TS-2084
Project: Traffic Server
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/TS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717929#comment-13717929
]
Bin Chen commented on TS-1375:
--
should we disable throttling? If connection is exceed, then ts c
[
https://issues.apache.org/jira/browse/TS-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717927#comment-13717927
]
Bin Chen commented on TS-1595:
--
this issue will a part of new remap format
> di
[
https://issues.apache.org/jira/browse/TS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1280.
Resolution: Fixed
> add url match token about cache control rule
>
>
[
https://issues.apache.org/jira/browse/TS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1280:
-
Attachment: TS-1280.patch
rebase master
> add url match token about cache control rule
> -
[
https://issues.apache.org/jira/browse/TS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1280:
-
Summary: add url match token about cache control rule (was: cache control
rule matching performance tweak(add url t
[
https://issues.apache.org/jira/browse/TS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1280:
-
Summary: cache control rule matching performance tweak(add url token)
(was: cache control rule matching performance
[
https://issues.apache.org/jira/browse/TS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2053:
-
Affects Version/s: (was: 3.3.4)
Fix Version/s: (was: 3.3.5)
3.2.4
> When
[
https://issues.apache.org/jira/browse/TS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2053:
-
Priority: Major (was: Blocker)
> When Consumer(User agent)->write_vio.nbytes = INT64_MAX &
> Producer(Cache)->
[
https://issues.apache.org/jira/browse/TS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2053:
-
Attachment: TS-2053.patch
> When Consumer(User agent)->write_vio.nbytes = INT64_MAX &
> Producer(Cache)->alive
Bin Chen created TS-2053:
Summary: When Consumer(User agent)->write_vio.nbytes = INT64_MAX &
Producer(Cache)->alive = false HttpSM will hung
Key: TS-2053
URL: https://issues.apache.org/jira/browse/TS-2053
Pr
[
https://issues.apache.org/jira/browse/TS-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-2053:
-
Affects Version/s: 3.3.4
3.2.4
Fix Version/s: 3.3.6
Assignee: Bin Chen
[
https://issues.apache.org/jira/browse/TS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1898.
Resolution: Fixed
> improve cluster read/write performance
> --
>
>
[
https://issues.apache.org/jira/browse/TS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1898:
-
Attachment: TS-1898_v2.patch
rebase on master
> improve cluster read/write performance
> --
[
https://issues.apache.org/jira/browse/TS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1520.
Resolution: Fixed
> CacheContinuation->timeout->m_ptr is null, then core
> ---
[
https://issues.apache.org/jira/browse/TS-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1482.
Resolution: Fixed
> enable define INACTIVITY_TIMEOUT, Action::cancel_action will assert
>
[
https://issues.apache.org/jira/browse/TS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1898:
-
Attachment: TS-1898.patch
1.add atomiclist to notify vc is ready
2.remove clustervc schedule handle
[
https://issues.apache.org/jira/browse/TS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1957.
Resolution: Fixed
> if CacheContinuation timeout, timeout Event will be loop
> --
[
https://issues.apache.org/jira/browse/TS-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1006:
Assignee: Yunkai Zhang (was: Bin Chen)
> memory management, cut down memory waste ?
> ---
[
https://issues.apache.org/jira/browse/TS-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1967:
-
Attachment: TS-1967.patch
add max accept & max client transactions limit. when exceed then drop request.
[
https://issues.apache.org/jira/browse/TS-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1967:
-
Assignee: Bin Chen
Issue Type: Improvement (was: Bug)
Affects Version/s: 3.2.4
> create
Bin Chen created TS-1967:
Summary: create max accept handler function
Key: TS-1967
URL: https://issues.apache.org/jira/browse/TS-1967
Project: Traffic Server
Issue Type: Bug
Components: Ne
[
https://issues.apache.org/jira/browse/TS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1957:
-
Attachment: TS-1957_v2.patch
> if CacheContinuation timeout, timeout Event will be loop
> -
[
https://issues.apache.org/jira/browse/TS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1957:
-
Attachment: TS-1957.patch
> if CacheContinuation timeout, timeout Event will be loop
>
[
https://issues.apache.org/jira/browse/TS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683463#comment-13683463
]
Bin Chen commented on TS-1957:
--
In cluster mode, if CacheContinuation timeout, the
"proxy.proc
[
https://issues.apache.org/jira/browse/TS-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1957:
Assignee: Bin Chen
> if CacheContinuation timeout, timeout Event will be loop
> -
Bin Chen created TS-1957:
Summary: if CacheContinuation timeout, timeout Event will be loop
Key: TS-1957
URL: https://issues.apache.org/jira/browse/TS-1957
Project: Traffic Server
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1757:
Assignee: Yunkai Zhang (was: taorui)
> core at LogUtils::escapify_url()
> ---
Bin Chen created TS-1906:
Summary: crash at BaseStatPagesHandler::resp_add
Key: TS-1906
URL: https://issues.apache.org/jira/browse/TS-1906
Project: Traffic Server
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635969#comment-13635969
]
Bin Chen commented on TS-1453:
--
this patch can be not depending on TS-1405. In our env, ts shoul
[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1453:
-
Attachment: (was: TS-1453.patch)
> remove InactivityCop and enable define INACTIVITY_TIMEOUT
> -
[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1453:
-
Attachment: TS-1453.patch
base git master + TS-1405(linux_time_wheel_v11jp.patch)
> remove Inactivi
[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634992#comment-13634992
]
Bin Chen commented on TS-1453:
--
John & Leif, please help to review this patch(replace InActivCop
[
https://issues.apache.org/jira/browse/TS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1453:
-
Attachment: TS-1453.patch
> remove InactivityCop and enable define INACTIVITY_TIMEOUT
>
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631560#comment-13631560
]
Bin Chen edited comment on TS-1405 at 4/15/13 7:44 AM:
---
http_load test:
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631560#comment-13631560
]
Bin Chen commented on TS-1405:
--
http_load test:
Very important:
* disabe ram cache (If not, tes
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1405:
-
Comment: was deleted
(was: url.txt:
total 50 urls.
the last number is the size of object.
{code}
http://ts.cn:8080/t
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631562#comment-13631562
]
Bin Chen commented on TS-1405:
--
url.txt:
total 50 urls.
the last number is the size of object.
{
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628638#comment-13628638
]
Bin Chen commented on TS-1405:
--
http_load -parallel 100 -seconds 60 -keep_alive 100 /tmp/URL
al
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626171#comment-13626171
]
Bin Chen commented on TS-1405:
--
linux_time_wheel_v11jp.patch
> apply time-wheel
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626145#comment-13626145
]
Bin Chen commented on TS-1405:
--
test box: Cluster(cluster_type == 1) 10*Cache Server:
CPU:Intel(
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625411#comment-13625411
]
Bin Chen commented on TS-1405:
--
Last patch have been running on our ten boxes five days. These b
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620798#comment-13620798
]
Bin Chen commented on TS-1405:
--
it's good idea freeing CANCEL_QUEUED event in
EThread::process_
[
https://issues.apache.org/jira/browse/TS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1757:
Assignee: taorui
> core at LogUtils::escapify_url()
>
>
>
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1797.
Resolution: Fixed
> when ts start, maybe some clusterHandlers is null. So we can scan all
> clusterHandlers in Cl
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1797:
-
Attachment: TS-1797.patch
> when ts start, maybe some clusterHandlers is null. So we can scan all
> clusterHand
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1797:
-
Summary: when ts start, maybe some clusterHandlers is null. So we can scan
all clusterHandlers in ClusterHandler *Cl
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1797:
-
Summary: when ts start, maybe some clusterHandlers is null. So we can scan
all clusterHandlers in ClusterHandler *Cl
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1797:
-
Summary: when ts start, maybe some clusterHandlers is null. So we can scan
all clusterHandlers. (was: when ts start
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619794#comment-13619794
]
Bin Chen commented on TS-1797:
--
in ClusterHandler *ClusterMachine::pop_ClusterHandler.
Bin Chen created TS-1797:
Summary: when ts start, maybe some clusterHandlers is null. So we
can scan allclusterHandlers.
Key: TS-1797
URL: https://issues.apache.org/jira/browse/TS-1797
Project: Traffic Server
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1797:
-
Fix Version/s: 3.3.2
> when ts start, maybe some clusterHandlers is null. So we can scan
> allclusterHandlers.
[
https://issues.apache.org/jira/browse/TS-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1797:
Assignee: Bin Chen
> when ts start, maybe some clusterHandlers is null. So we can scan
> allclusterHandle
[
https://issues.apache.org/jira/browse/TS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1751.
Resolution: Fixed
> when ts have high cpu usage, cluster thread isn't balance
> --
[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619536#comment-13619536
]
Bin Chen commented on TS-1405:
--
yeah, i should read more carefully. But i can test this patch fi
[
https://issues.apache.org/jira/browse/TS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1751:
-
Attachment: TS-1751_v3.patch
when cluster connection assigned ok(origin assign by connection handle), don't
bind cl
[
https://issues.apache.org/jira/browse/TS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1751:
-
Fix Version/s: (was: 3.5.0)
3.3.2
> when ts have high cpu usage, cluster thread isn't bal
[
https://issues.apache.org/jira/browse/TS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1796.
Resolution: Fixed
> remove cluster connection number change handler because of cluster connection
> number = (bas
[
https://issues.apache.org/jira/browse/TS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1796:
-
Attachment: TS-1796.patch
> remove cluster connection number change handler because of cluster connection
> num
[
https://issues.apache.org/jira/browse/TS-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen reassigned TS-1796:
Assignee: Bin Chen
> remove cluster connection number change handler because of cluster connection
> numb
Bin Chen created TS-1796:
Summary: remove cluster connection number change handler because
of cluster connection number = (base on) cluster thread number
Key: TS-1796
URL: https://issues.apache.org/jira/browse/TS-1796
[
https://issues.apache.org/jira/browse/TS-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen closed TS-1793.
Resolution: Fixed
> force cluster connection = cluster number for cluster thread balance
> --
[
https://issues.apache.org/jira/browse/TS-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin Chen updated TS-1793:
-
Attachment: TS-1793.patch
> force cluster connection = cluster number for cluster thread balance
>
1 - 100 of 179 matches
Mail list logo
