[jira] [Commented] (KUDU-3007) ARM/aarch64 platform support

[ https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090034#comment-17090034 ] Adar Dembo commented on KUDU-3007: -- [~seanlau], I'm no longer all that involved in Kudu's day-to-day

[jira] [Commented] (KUDU-3007) ARM/aarch64 platform support

[ https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077559#comment-17077559 ] Adar Dembo commented on KUDU-3007: -- Thanks for doing this amazing work. Looks like we're almost there!

[jira] [Assigned] (KUDU-3101) ASAN and dynamic linking are incompatible on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-3101: Affects Version/s: 1.12.0 Assignee: RuiChen Summary: ASAN and dynamic

[jira] [Reopened] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reopened KUDU-3072: -- [~huangtianhua], could you take a look at [~shuna]'s question? > minidump-test failed on aarch64 server >

[jira] [Commented] (KUDU-3102) tabletserver coredump in jsonwriter

[ https://issues.apache.org/jira/browse/KUDU-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073129#comment-17073129 ] Adar Dembo commented on KUDU-3102: -- The upper half of the stack trace suggests an issue in allocation

[jira] [Commented] (KUDU-3101) There is no checking for incompatibility of ASAN and dynamic linking in CMakeLists.txt

[ https://issues.apache.org/jira/browse/KUDU-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073128#comment-17073128 ] Adar Dembo commented on KUDU-3101: -- That note in the Kudu README is actually stale: in 2015 we [removed

[jira] [Assigned] (KUDU-423) Implement scalable and performant on-disk storage

[ https://issues.apache.org/jira/browse/KUDU-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-423: --- Assignee: (was: Adar Dembo) This Jira originally yielded the log block manager, but there's still

[jira] [Assigned] (KUDU-829) Support online GC of orphaned data blocks

[ https://issues.apache.org/jira/browse/KUDU-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-829: --- Assignee: (was: Adar Dembo) I never got around to this and am not actively working on it, so

[jira] [Assigned] (KUDU-605) Implement block placement hints

[ https://issues.apache.org/jira/browse/KUDU-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-605: --- Assignee: (was: Adar Dembo) I never got around to doing this and am not actively working on it,

[jira] [Assigned] (KUDU-1967) Umbrella JIRA for node density improvements

[ https://issues.apache.org/jira/browse/KUDU-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-1967: Assignee: (was: Adar Dembo) I did a fair amount of work for this in past Kudu releases; the

[jira] [Assigned] (KUDU-478) Prototype additional allocation strategies

[ https://issues.apache.org/jira/browse/KUDU-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-478: --- Assignee: (was: Adar Dembo) I never got around to this and am not actively working on it. >

[jira] [Assigned] (KUDU-1358) Following a master leader election, create table may fail

[ https://issues.apache.org/jira/browse/KUDU-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-1358: Assignee: (was: Adar Dembo) I never got around to doing this and am not actively working on

[jira] [Assigned] (KUDU-477) Implement block storage microbenchmark

[ https://issues.apache.org/jira/browse/KUDU-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-477: --- Assignee: (was: Adar Dembo) I never got around to doing this and am not actively working on it,

[jira] [Commented] (KUDU-3096) debug-util-test failed sometimes on aarch64: Segmentation fault

[ https://issues.apache.org/jira/browse/KUDU-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071181#comment-17071181 ] Adar Dembo commented on KUDU-3096: -- [~tlipcon] any ideas here? I remember the stacktrace collection code

[jira] [Commented] (KUDU-3093) DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069305#comment-17069305 ] Adar Dembo commented on KUDU-3093: -- Can you open a new JIRA with the log output of the test? >

[jira] [Resolved] (KUDU-3093) DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3093. -- Fix Version/s: 1.12.0 Resolution: Fixed > DebugUtilTest.TestSignalStackTrace of debug-util-test

[jira] [Commented] (KUDU-3093) DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069250#comment-17069250 ] Adar Dembo commented on KUDU-3093: -- bq. So in RELEASE mode, we don't call the function SleeperThread()?

[jira] [Assigned] (KUDU-3093) DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-3093: Assignee: Adar Dembo > DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64 >

[jira] [Commented] (KUDU-3093) DebugUtilTest.TestSignalStackTrace of debug-util-test failed on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069027#comment-17069027 ] Adar Dembo commented on KUDU-3093: -- I actually don't think this is an aarch64-specific issue; I can repro

[jira] [Updated] (KUDU-3087) Python tests failed on arm64

[ https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3087: - Fix Version/s: 1.12.0 Resolution: Fixed Status: Resolved (was: In Review) > Python

[jira] [Resolved] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3072. -- Fix Version/s: 1.12.0 Assignee: huangtianhua Resolution: Fixed > minidump-test failed

[jira] [Created] (KUDU-3092) MultiMasterIdleConnectionsITest.ClientReacquiresAuthnToken is flaky

Adar Dembo created KUDU-3092: Summary: MultiMasterIdleConnectionsITest.ClientReacquiresAuthnToken is flaky Key: KUDU-3092 URL: https://issues.apache.org/jira/browse/KUDU-3092 Project: Kudu

[jira] [Commented] (KUDU-3089) ERROR when running tests on ARM64 server with TSAN or ASAN enabled

[ https://issues.apache.org/jira/browse/KUDU-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065356#comment-17065356 ] Adar Dembo commented on KUDU-3089: -- Yeah that looks like a reasonable way to invoke the tests (using

[jira] [Commented] (KUDU-3089) ERROR when running tests on ARM64 server with TSAN or ASAN enabled

[ https://issues.apache.org/jira/browse/KUDU-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065100#comment-17065100 ] Adar Dembo commented on KUDU-3089: -- For ASAN, check out

[jira] [Assigned] (KUDU-3087) Python tests failed on arm64

[ https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-3087: Assignee: Alexey Serbin Alexey authored that commit. Alexey, when you have a moment, could you

[jira] [Commented] (KUDU-3068) MemTracker CHECK failed on aarch64 when run cache-bench test

[ https://issues.apache.org/jira/browse/KUDU-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060418#comment-17060418 ] Adar Dembo commented on KUDU-3068: -- bq. Should I propose an patch for this? Sure. For what it's worth,

[jira] [Updated] (KUDU-2836) Maybe wrong memory size used to detect pressure

[ https://issues.apache.org/jira/browse/KUDU-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2836: - Affects Version/s: 1.10.0 > Maybe wrong memory size used to detect pressure >

[jira] [Resolved] (KUDU-3064) client_symbol-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3064. -- Fix Version/s: 1.12.0 Assignee: huangtianhua Resolution: Fixed > client_symbol-test

[jira] [Commented] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058280#comment-17058280 ] Adar Dembo commented on KUDU-3072: -- Yeah I think that's a reasonable place to start. We can always

[jira] [Commented] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057156#comment-17057156 ] Adar Dembo commented on KUDU-3072: -- Well, you could certainly patch glog to avoid libunwind on aarch64,

[jira] [Resolved] (KUDU-3070) allow skip open block manager in cli cmeta rewrite_raft_config operation

[ https://issues.apache.org/jira/browse/KUDU-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3070. -- Fix Version/s: 1.12.0 Assignee: wangningito Resolution: Fixed > allow skip open block

[jira] [Commented] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056138#comment-17056138 ] Adar Dembo commented on KUDU-3072: -- The documentation for libunwind suggests that it supports aarch64,

[jira] [Commented] (KUDU-3064) client_symbol-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056135#comment-17056135 ] Adar Dembo commented on KUDU-3064: -- bq. Do I need to propose this simple modification first? Consider it

[jira] [Commented] (KUDU-3072) minidump-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055630#comment-17055630 ] Adar Dembo commented on KUDU-3072: -- I can't comment on the glog fix (I'm not super familiar with glog),

[jira] [Resolved] (KUDU-3069) Support to alter the number of hash buckets for newly added range partitions

[ https://issues.apache.org/jira/browse/KUDU-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3069. -- Fix Version/s: n/a Resolution: Duplicate To add to what Vlad said, [~zhangyifan27] if you've got

[jira] [Commented] (KUDU-3067) Inexplict cloud detection for AWS and OpenStack based cloud by querying metadata

[ https://issues.apache.org/jira/browse/KUDU-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051750#comment-17051750 ] Adar Dembo commented on KUDU-3067: -- [~aserbin] wrote the cloud detector and is aware of this bug. I think

[jira] [Commented] (KUDU-3068) MemTracker CHECK failed on aarch64 when run cache-bench test

[ https://issues.apache.org/jira/browse/KUDU-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051697#comment-17051697 ] Adar Dembo commented on KUDU-3068: -- Hmm, perhaps the behavior of std::atomic is slightly different on

[jira] [Commented] (KUDU-3064) client_symbol-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049882#comment-17049882 ] Adar Dembo commented on KUDU-3064: -- bq. so I think we should match _U* to make all plats works? Yeah I

[jira] [Commented] (KUDU-3066) Possible data race in kudu::security::InitKerberosForServer

[ https://issues.apache.org/jira/browse/KUDU-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049878#comment-17049878 ] Adar Dembo commented on KUDU-3066: -- That's pretty weird though: the renewal thread is only started by the

[jira] [Commented] (KUDU-3064) client_symbol-test failed on aarch64 server

[ https://issues.apache.org/jira/browse/KUDU-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049736#comment-17049736 ] Adar Dembo commented on KUDU-3064: -- You'll need to update [this

[jira] [Commented] (KUDU-3054) Init kudu.write_duration accumulator lazily

[ https://issues.apache.org/jira/browse/KUDU-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036702#comment-17036702 ] Adar Dembo commented on KUDU-3054: -- [~liupengcheng] thanks for filing this. I can't load the images

[jira] [Resolved] (KUDU-2155) Disarm failure detector during an election

[ https://issues.apache.org/jira/browse/KUDU-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2155. -- Fix Version/s: 1.12.0 Resolution: Fixed > Disarm failure detector during an election >

[jira] [Resolved] (KUDU-2987) Intra location rebalance will crash in special case

[ https://issues.apache.org/jira/browse/KUDU-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2987. -- Fix Version/s: 1.11.1 1.12.0 Resolution: Fixed > Intra location rebalance

[jira] [Updated] (KUDU-2987) Intra location rebalance will crash in special case

[ https://issues.apache.org/jira/browse/KUDU-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2987: - Affects Version/s: 1.11.0 > Intra location rebalance will crash in special case >

[jira] [Updated] (KUDU-2987) Intra location rebalance will crash in special case

[ https://issues.apache.org/jira/browse/KUDU-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2987: - Component/s: CLI > Intra location rebalance will crash in special case >

[jira] [Resolved] (KUDU-3035) createRequestPB() in Batch.java doesn't set the last propagated timestamp on the builder

[ https://issues.apache.org/jira/browse/KUDU-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3035. -- Fix Version/s: 1.12.0 Resolution: Fixed > createRequestPB() in Batch.java doesn't set the last

[jira] [Assigned] (KUDU-3035) createRequestPB() in Batch.java doesn't set the last propagated timestamp on the builder

[ https://issues.apache.org/jira/browse/KUDU-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-3035: Assignee: Andy > createRequestPB() in Batch.java doesn't set the last propagated timestamp on >

[jira] [Created] (KUDU-3038) ClientFailoverTServerTimeoutITest.FailoverOnLeaderTimeout is flaky in TSAN mode

Adar Dembo created KUDU-3038: Summary: ClientFailoverTServerTimeoutITest.FailoverOnLeaderTimeout is flaky in TSAN mode Key: KUDU-3038 URL: https://issues.apache.org/jira/browse/KUDU-3038 Project: Kudu

[jira] [Created] (KUDU-3037) HMS notification log listener runs in follower masters

Adar Dembo created KUDU-3037: Summary: HMS notification log listener runs in follower masters Key: KUDU-3037 URL: https://issues.apache.org/jira/browse/KUDU-3037 Project: Kudu Issue Type:

[jira] [Resolved] (KUDU-3032) key columns unnecessarily selected when predicate is converted to range

[ https://issues.apache.org/jira/browse/KUDU-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3032. -- Fix Version/s: 1.12.0 Resolution: Fixed > key columns unnecessarily selected when predicate is

[jira] [Commented] (KUDU-3035) createRequestPB() in Batch.java doesn't set the last propagated timestamp on the builder

[ https://issues.apache.org/jira/browse/KUDU-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008545#comment-17008545 ] Adar Dembo commented on KUDU-3035: -- Thanks for finding this. Looks like it's been around since the very

[jira] [Updated] (KUDU-3035) createRequestPB() in Batch.java doesn't set the last propagated timestamp on the builder

[ https://issues.apache.org/jira/browse/KUDU-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3035: - Component/s: java > createRequestPB() in Batch.java doesn't set the last propagated timestamp on > the

[jira] [Updated] (KUDU-3035) createRequestPB() in Batch.java doesn't set the last propagated timestamp on the builder

[ https://issues.apache.org/jira/browse/KUDU-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3035: - Affects Version/s: 1.11.1 > createRequestPB() in Batch.java doesn't set the last propagated timestamp on

[jira] [Commented] (KUDU-3021) Add metric gauges for the size of transactions applied to tablets and number of rejected transactions due to their size

[ https://issues.apache.org/jira/browse/KUDU-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17004871#comment-17004871 ] Adar Dembo commented on KUDU-3021: -- Keeping this open for the histogram Alexey suggested. > Add metric

[jira] [Resolved] (KUDU-3029) error raised on aarch64: #error You need to define CycleTimer for your O/S and CPU

[ https://issues.apache.org/jira/browse/KUDU-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3029. -- Fix Version/s: 1.12.0 Resolution: Fixed > error raised on aarch64: #error You need to define

[jira] [Updated] (KUDU-2839) RebalanceParamTest.Rebalance in attemp to get location for non-participant in a tablet's Raft configuration

[ https://issues.apache.org/jira/browse/KUDU-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2839: - Fix Version/s: 1.12.0 Resolution: Fixed Status: Resolved (was: In Review) >

[jira] [Updated] (KUDU-3029) error raised on aarch64: #error You need to define CycleTimer for your O/S and CPU

[ https://issues.apache.org/jira/browse/KUDU-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3029: - Affects Version/s: 1.11.1 > error raised on aarch64: #error You need to define CycleTimer for your O/S >

[jira] [Assigned] (KUDU-3029) error raised on aarch64: #error You need to define CycleTimer for your O/S and CPU

[ https://issues.apache.org/jira/browse/KUDU-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-3029: Assignee: huangtianhua > error raised on aarch64: #error You need to define CycleTimer for your

[jira] [Commented] (KUDU-282) Test when errors occur on the Apply() phase of transactions

[ https://issues.apache.org/jira/browse/KUDU-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17004867#comment-17004867 ] Adar Dembo commented on KUDU-282: - bq. who can tell me, what`s the reason of this bug? any fix other than

[jira] [Resolved] (KUDU-3027) gcc error: unrecognized command line option '-msse4.2' on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3027. -- Fix Version/s: 1.12.0 Resolution: Fixed > gcc error: unrecognized command line option '-msse4.2'

[jira] [Updated] (KUDU-3027) gcc error: unrecognized command line option '-msse4.2' on aarch64

[ https://issues.apache.org/jira/browse/KUDU-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3027: - Affects Version/s: 1.11.1 > gcc error: unrecognized command line option '-msse4.2' on aarch64 >

[jira] [Updated] (KUDU-2992) Limit concurrent alter request of a table

[ https://issues.apache.org/jira/browse/KUDU-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2992: - Affects Version/s: 1.11.0 > Limit concurrent alter request of a table >

[jira] [Resolved] (KUDU-2992) Limit concurrent alter request of a table

[ https://issues.apache.org/jira/browse/KUDU-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2992. -- Fix Version/s: 1.12.0 Resolution: Fixed > Limit concurrent alter request of a table >

[jira] [Commented] (KUDU-3022) C++ Client does not retry CreateTable on "new table name is already reserved" error

[ https://issues.apache.org/jira/browse/KUDU-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997642#comment-16997642 ] Adar Dembo commented on KUDU-3022: -- This is also an issue for altering a table. LookupRpc::SendRpcCb has

[jira] [Commented] (KUDU-3007) ARM/aarch64 platform support

[ https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994912#comment-16994912 ] Adar Dembo commented on KUDU-3007: -- bq. I cannot open the kudu-upstream-infra repo(maybe it is a private

[jira] [Commented] (KUDU-3007) ARM/aarch64 platform support

[ https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993254#comment-16993254 ] Adar Dembo commented on KUDU-3007: -- Sorry for not responding earlier; been thinking about the proposal

[jira] [Commented] (KUDU-3016) Catalog manager: don't lump together all updates from one tablet report

[ https://issues.apache.org/jira/browse/KUDU-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992189#comment-16992189 ] Adar Dembo commented on KUDU-3016: -- As proposed, this would revert the perf improvement from KUDU-1125.

[jira] [Resolved] (KUDU-3001) Multi-thread to load containers in a data directory

[ https://issues.apache.org/jira/browse/KUDU-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-3001. -- Fix Version/s: 1.12.0 Resolution: Fixed > Multi-thread to load containers in a data directory >

[jira] [Resolved] (KUDU-2703) ITClientStress.testMultipleSessions timeout

[ https://issues.apache.org/jira/browse/KUDU-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2703. -- Fix Version/s: 1.12.0 Resolution: Fixed > ITClientStress.testMultipleSessions timeout >

[jira] [Assigned] (KUDU-2703) ITClientStress.testMultipleSessions timeout

[ https://issues.apache.org/jira/browse/KUDU-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-2703: Assignee: Adar Dembo > ITClientStress.testMultipleSessions timeout >

[jira] [Commented] (KUDU-3013) Race in StopTabletITest.TestStoppedTabletsDontWrite

[ https://issues.apache.org/jira/browse/KUDU-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986277#comment-16986277 ] Adar Dembo commented on KUDU-3013: -- Thanks for the detailed analysis; this test has been flaky for some

[jira] [Commented] (KUDU-3010) unsafe_change_config can lead to a crash

[ https://issues.apache.org/jira/browse/KUDU-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984037#comment-16984037 ] Adar Dembo commented on KUDU-3010: -- The quoted logs have quite a bit of info elided from them, not least

[jira] [Updated] (KUDU-3012) Throttle "Applying an operation in a closed session" warning log

[ https://issues.apache.org/jira/browse/KUDU-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3012: - Labels: newbie (was: beginner) > Throttle "Applying an operation in a closed session" warning log >

[jira] [Updated] (KUDU-3010) unsafe_change_config can lead to a crash

[ https://issues.apache.org/jira/browse/KUDU-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-3010: - Description: I've seen a case of running the {{unsafe_change_config}} tool, per the steps laid out in

[jira] [Commented] (KUDU-3007) ARM/aarch64 platform support

[ https://issues.apache.org/jira/browse/KUDU-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979872#comment-16979872 ] Adar Dembo commented on KUDU-3007: -- This is very exciting! I presume you and/or your organization already

[jira] [Resolved] (KUDU-2162) Expose stats about scan filters

[ https://issues.apache.org/jira/browse/KUDU-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2162. -- Fix Version/s: 1.12.0 Resolution: Fixed Some more stats are now exposed. If there's a need for

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978987#comment-16978987 ] Adar Dembo commented on KUDU-2990: -- The 1.10.1 and 1.11.1 releases are now available on [the downloads

[jira] [Commented] (KUDU-38) bootstrap should not replay logs that are known to be fully flushed

[ https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978859#comment-16978859 ] Adar Dembo commented on KUDU-38: I spoke to Todd offline and he helped me see what I had been missing. The

[jira] [Commented] (KUDU-38) bootstrap should not replay logs that are known to be fully flushed

[ https://issues.apache.org/jira/browse/KUDU-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976392#comment-16976392 ] Adar Dembo commented on KUDU-38: [~tlipcon] I've been looking into this (with [~awong]'s help) and I have a

[jira] [Resolved] (KUDU-2777) Upgrade LZ4 to 1.9.0+

[ https://issues.apache.org/jira/browse/KUDU-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2777. -- Resolution: Fixed > Upgrade LZ4 to 1.9.0+ > - > > Key: KUDU-2777 >

[jira] [Updated] (KUDU-2777) Upgrade LZ4 to 1.9.0+

[ https://issues.apache.org/jira/browse/KUDU-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2777: - Fix Version/s: (was: 1.11.0) > Upgrade LZ4 to 1.9.0+ > - > > Key:

[jira] [Updated] (KUDU-2777) Upgrade LZ4 to 1.9.0+

[ https://issues.apache.org/jira/browse/KUDU-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2777: - Fix Version/s: 1.11.0 > Upgrade LZ4 to 1.9.0+ > - > > Key: KUDU-2777

[jira] [Resolved] (KUDU-2977) Sharding block map of LogBlockManager

[ https://issues.apache.org/jira/browse/KUDU-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2977. -- Fix Version/s: 1.12.0 Resolution: Fixed > Sharding block map of LogBlockManager >

[jira] [Resolved] (KUDU-2995) Tuning kudu write performance

[ https://issues.apache.org/jira/browse/KUDU-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2995. -- Fix Version/s: n/a Resolution: Information Provided For problems like these, please e-mail [the

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968169#comment-16968169 ] Adar Dembo commented on KUDU-2990: -- [~pbalcer] thanks for the feedback. Agreed that, given your

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967335#comment-16967335 ] Adar Dembo commented on KUDU-2990: -- [~Michal Biesek] thanks for chiming in. Do you have any concerns

[jira] [Updated] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2990: - Status: In Review (was: In Progress) > Kudu can't distribute libnuma (dependency of memkind) >

[jira] [Updated] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2990: - Code Review: https://gerrit.cloudera.org/c/14620/ > Kudu can't distribute libnuma (dependency of memkind)

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964676#comment-16964676 ] Adar Dembo commented on KUDU-2990: -- To put a finer point on option #3, perhaps it'd be sufficient to: #

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964658#comment-16964658 ] Adar Dembo commented on KUDU-2990: -- There's a clause in the ASF 3rd party license policy that talks about

[jira] [Commented] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

[ https://issues.apache.org/jira/browse/KUDU-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964654#comment-16964654 ] Adar Dembo commented on KUDU-2990: -- To be a little more pedantic, we currently provide Kudu in one source

[jira] [Created] (KUDU-2990) Kudu can't distribute libnuma (dependency of memkind)

Adar Dembo created KUDU-2990: Summary: Kudu can't distribute libnuma (dependency of memkind) Key: KUDU-2990 URL: https://issues.apache.org/jira/browse/KUDU-2990 Project: Kudu Issue Type: Bug

[jira] [Created] (KUDU-2988) built-in NTP client: sometimes minichronyd fails to start with address already in use

Adar Dembo created KUDU-2988: Summary: built-in NTP client: sometimes minichronyd fails to start with address already in use Key: KUDU-2988 URL: https://issues.apache.org/jira/browse/KUDU-2988 Project:

[jira] [Resolved] (KUDU-2949) Thread collision in consensus current_term

[ https://issues.apache.org/jira/browse/KUDU-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo resolved KUDU-2949. -- Fix Version/s: 1.12.0 Resolution: Fixed Fixed in commit 87d90b2. > Thread collision in

[jira] [Commented] (KUDU-2975) Spread WAL across multiple data directories

[ https://issues.apache.org/jira/browse/KUDU-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964460#comment-16964460 ] Adar Dembo commented on KUDU-2975: -- Andrew, thanks for the detailed summary. I agree with pretty much

[jira] [Commented] (KUDU-2904) Master shouldn't allow master tablet operations after a disk failure

[ https://issues.apache.org/jira/browse/KUDU-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964440#comment-16964440 ] Adar Dembo commented on KUDU-2904: -- bq. Should/can we persist this disk failure state on the master

[jira] [Updated] (KUDU-2949) Thread collision in consensus current_term

[ https://issues.apache.org/jira/browse/KUDU-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo updated KUDU-2949: - Code Review: https://gerrit.cloudera.org/c/14580/ > Thread collision in consensus current_term >

[jira] [Assigned] (KUDU-2949) Thread collision in consensus current_term

[ https://issues.apache.org/jira/browse/KUDU-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adar Dembo reassigned KUDU-2949: Assignee: Adar Dembo > Thread collision in consensus current_term >

[jira] [Commented] (KUDU-2963) Catalog manager never gives up on CreateTablet RPCs

[ https://issues.apache.org/jira/browse/KUDU-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963431#comment-16963431 ] Adar Dembo commented on KUDU-2963: -- Thanks for finding that 30s deadline; I didn't notice that and

[jira] [Commented] (KUDU-2979) Add wrap up function of krb5_parse_name, so it can be called from Impala

[ https://issues.apache.org/jira/browse/KUDU-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16961451#comment-16961451 ] Adar Dembo commented on KUDU-2979: -- Fixed in commit 6ca5991. > Add wrap up function of krb5_parse_name,

  1   2   3   4   5   6   7   8   >